Skip to content

Commit 845b490

Browse files
committed
chore: moved future plans after installation and setup instructions
1 parent 8b2960c commit 845b490

File tree

1 file changed

+17
-17
lines changed

1 file changed

+17
-17
lines changed

README.md

Lines changed: 17 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -65,23 +65,6 @@ and [Emacs](https://fortls.fortran-lang.org/editor_integration.html#emacs).
6565

6666
- Signature help and hover does not handle elegantly overloaded functions i.e. interfaces
6767

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-
8568
## Installation
8669

8770
### PyPi
@@ -162,6 +145,23 @@ An example for a Configuration file is given below
162145
| `textDocument/didChange` | Document synchronisation upon changes to the document |
163146
| `textDocument/codeAction` | **Experimental** Generate code |
164147

148+
## Future plans
149+
150+
`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+
165165
## `fortls` vs `fortran-language-server`
166166

167167
This project was originally based on `fortran-language-server` LSP implementation, but the two projects have since diverged.

0 commit comments

Comments
 (0)