Any sneak peaks on what's next?

[jcmkk3]

I don't have any expectation of a roadmap or even a planned direction, but I see that zyedidia has a bunch of interesting packages* that seem like they could be useful in the context of micro. Any current ideas on what areas that micro might want to explore or what existing experiments might stick? This is really just the editor geek in me that is curious to see this innovation.

*Some of these might already be used and I missed it

• https://github.com/zyedidia/sregx
• https://github.com/zyedidia/gpeg
• https://github.com/zyedidia/flare
• https://github.com/zyedidia/kbd

[zyedidia]

Yes I've been doing some more long-horizon explorations in the projects you linked. I'm hoping to integrate them into micro at some point, but haven't been able to find the time/motivation. The first update would be changing the backend data structure to a line rope, and then updating the syntax highlighting engine to use flare/gpeg. A couple stoppers for now are a difference in interface between the current data structure and the one I want to update to regarding unicode handling, and a lack of language support in flare compared to the current highlighter.

[rajeevedmonds]

+1 for mentioning potential LSP support in the future. That's the only feature missing for me. Everything else works like a charm.

Hopefully, the lead developers have this in mind (LSP).

[gdoth]

Just wondering if this projects still alive, it's been almost a year since the last update. It would be sad to lose it as this is a nice middle ground for a terminal text editor that isn't vim/emacs etc.

[Fig-Amarole]

Just wondering if this projects still alive, it's been almost a year since the last update. It would be sad to lose it as this is a nice middle ground for a terminal text editor that isn't vim/emacs etc.

While there hasn't been a versioned release in a year, Micro is still getting new commits and pull requests with fixes and features.
Is there a specific update/feature that you were wanting?

[srobertjames]

LSP would be amazing.

[Haitham-Shalaby]

bump golang version and other 3pp dependencies to handle CVEs

[maddes8cht]

Just wondering if this projects still alive, it's been almost a year since the last update. It would be sad to lose it as this is a nice middle ground for a terminal text editor that isn't vim/emacs etc.

While there hasn't been a versioned release in a year, Micro is still getting new commits and pull requests with fixes and features. Is there a specific update/feature that you were wanting?

release early, release often!

As it makes open source project more attractive to other developers to jump in and help when they see their contributions to be included soon and beeing received as useful.
There is nothing special I'm waiting for - especially no special feature or commit from the last year that I'm particularly waiting to see in a release.
But it has accumulated quite a bit of small improvements.
In many small details the current release version does feel a bit "clumsy" - and some commits from last year sound like they have reduced this "clumsyness" overall.

by the way:

I like the statusbar-commit, the multiopen-commit and the fake-cursor-commit, but it's even more the small fixes like these syntax-highlighting fixes, comment-detection fix, or the buffer view relocation improvement that reduce the "clumsyness"-feeling.

Yes, i can compile it myself, but ...
Every now and then i would like people who are only moderately familiar with the commandline to use a snappy commandline editor from there.
One that at least uses the usual "normal" shortcut keys and feels reasonably familiar - not vim. In many respects, micro is the best there is.
But then I don't tell them: compile it yourself first.

So yes, I think there is enough reason to do a bugfix-release.

And as long as there are no known newly introduced unfixed bugs in the Codebase, I would suggest you should do bugfix releases every now and then.
It also will help to improve visibility of µ.