You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -65,22 +66,10 @@ and [Emacs](https://fortls.fortran-lang.org/editor_integration.html#emacs).
65
66
66
67
- Signature help and hover does not handle elegantly overloaded functions i.e. interfaces
67
68
68
-
## Future plans
69
-
70
-
`fortls` has reached a point where it is feature complete and stable enough to be used in many modern Fortran projects without any issues.
71
-
It does however still have fundamental limitations,
72
-
namely its ability to understand all Fortran syntax and semantics that has been used throughout the 65+ years of the language. **The good news is that we have a plan to address this issue!**
73
-
74
-
We are excited to announce that we are working on creating a new Fortran Language Server
75
-
based on the actively developed [LFortran](https://lfortran.org/) compiler 🎉.
76
-
The new Language Server will be able to understand all Fortran syntax, be faster,
77
-
and give more accurate autocompletion, hover and diagnostic information. That means we plan on investing any future funding on creating our new language server and ultimately creating a better user experience for everyone.
78
-
79
-
<!-- Have a look at our roadmap (link) and consider contributing to our efforts (donations and contribution tasks link). -->
69
+
## Documentation
80
70
81
-
### What about `fortls`?
82
-
83
-
Not to worry, `fortls` will continue to be here. We will keep `fortls` in maintenance mode with bug fixes and new features from volunteer contributors, but otherwise we will be focusing our efforts into making the new LFortran language server a reality.
71
+
The full documentation for `fortls` can be found at
`fortls` has reached a point where it is feature complete and stable enough to be used in many modern Fortran projects without any issues.
157
+
It does however still have fundamental limitations,
158
+
namely its ability to understand all Fortran syntax and semantics that has been used throughout the 65+ years of the language. **The good news is that we have a plan to address this issue!**
159
+
160
+
We are excited to announce that we are working on creating a new Fortran Language Server
161
+
based on the actively developed [LFortran](https://lfortran.org/) compiler 🎉.
162
+
The new Language Server will be able to understand all Fortran syntax, be faster,
163
+
and give more accurate autocompletion, hover and diagnostic information. That means we plan on investing any future funding on creating our new language server and ultimately creating a better user experience for everyone.
164
+
165
+
<!-- Have a look at our roadmap (link) and consider contributing to our efforts (donations and contribution tasks link). -->
166
+
167
+
### What about `fortls`?
168
+
169
+
Not to worry, `fortls` will continue to be here. We will keep `fortls` in active maintenance mode with bug fixes and new features from volunteer contributors, but otherwise we will be focusing our efforts into making the new language server using LFortran's parser a reality.
170
+
165
171
## `fortls` vs `fortran-language-server`
166
172
167
173
This project was originally based on `fortran-language-server` LSP implementation, but the two projects have since diverged.
@@ -181,12 +187,10 @@ change in the future.
181
187
This project would not have been possible without the original work of [@hansec](https://github.com/hansec/)
182
188
in [`fortran-language-server`](https://github.com/hansec/fortran-language-server)
183
189
184
-
<!-- ## Support
185
-
186
-
If you want to support this project you can do it through
0 commit comments