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
Copy file name to clipboardExpand all lines: README.md
+17-17Lines changed: 17 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -65,23 +65,6 @@ and [Emacs](https://fortls.fortran-lang.org/editor_integration.html#emacs).
65
65
66
66
- Signature help and hover does not handle elegantly overloaded functions i.e. interfaces
67
67
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). -->
80
-
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.
84
-
85
68
## Installation
86
69
87
70
### PyPi
@@ -162,6 +145,23 @@ An example for a Configuration file is given below
162
145
|`textDocument/didChange`| Document synchronisation upon changes to the document |
`fortls` has reached a point where it is feature complete and stable enough to be used in many modern Fortran projects without any issues.
151
+
It does however still have fundamental limitations,
152
+
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!**
153
+
154
+
We are excited to announce that we are working on creating a new Fortran Language Server
155
+
based on the actively developed [LFortran](https://lfortran.org/) compiler 🎉.
156
+
The new Language Server will be able to understand all Fortran syntax, be faster,
157
+
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.
158
+
159
+
<!-- Have a look at our roadmap (link) and consider contributing to our efforts (donations and contribution tasks link). -->
160
+
161
+
### What about `fortls`?
162
+
163
+
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.
164
+
165
165
## `fortls` vs `fortran-language-server`
166
166
167
167
This project was originally based on `fortran-language-server` LSP implementation, but the two projects have since diverged.
0 commit comments