#microeditor — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #microeditor, aggregated by home.social.
-
Back when I was looking at switching command line editors, #MicroEditor had top notch mouse support, while #HelixEditor had first class #TreeSitter and #LanguageServerProtocol support (and I wanted both).
My hunch was improving mouse support in hx was much more doable (correct, as that PR showed - but it never got accepted), and I've been using hx.
Meanwhile LSP support doesn't seem to have improved much in Micro, sadly. eg LSP feature request https://github.com/micro-editor/micro/issues/1138 opened in 2018 and closed in frustration in 2023, and discussion https://github.com/micro-editor/micro/discussions/3231 links to several since abandoned plugins, but also https://github.com/Andriamanitra/mlsp/
-
Back when I was looking at switching command line editors, #MicroEditor had top notch mouse support, while #HelixEditor had first class #TreeSitter and #LanguageServerProtocol support (and I wanted both).
My hunch was improving mouse support in hx was much more doable (correct, as that PR showed - but it never got accepted), and I've been using hx.
Meanwhile LSP support doesn't seem to have improved much in Micro, sadly. eg LSP feature request https://github.com/micro-editor/micro/issues/1138 opened in 2018 and closed in frustration in 2023, and discussion https://github.com/micro-editor/micro/discussions/3231 links to several since abandoned plugins, but also https://github.com/Andriamanitra/mlsp/
-
Back when I was looking at switching command line editors, #MicroEditor had top notch mouse support, while #HelixEditor had first class #TreeSitter and #LanguageServerProtocol support (and I wanted both).
My hunch was improving mouse support in hx was much more doable (correct, as that PR showed - but it never got accepted), and I've been using hx.
Meanwhile LSP support doesn't seem to have improved much in Micro, sadly. eg LSP feature request https://github.com/micro-editor/micro/issues/1138 opened in 2018 and closed in frustration in 2023, and discussion https://github.com/micro-editor/micro/discussions/3231 links to several since abandoned plugins, but also https://github.com/Andriamanitra/mlsp/
-
Back when I was looking at switching command line editors, #MicroEditor had top notch mouse support, while #HelixEditor had first class #TreeSitter and #LanguageServerProtocol support (and I wanted both).
My hunch was improving mouse support in hx was much more doable (correct, as that PR showed - but it never got accepted), and I've been using hx.
Meanwhile LSP support doesn't seem to have improved much in Micro, sadly. eg LSP feature request https://github.com/micro-editor/micro/issues/1138 opened in 2018 and closed in frustration in 2023, and discussion https://github.com/micro-editor/micro/discussions/3231 links to several since abandoned plugins, but also https://github.com/Andriamanitra/mlsp/
-
Back when I was looking at switching command line editors, #MicroEditor had top notch mouse support, while #HelixEditor had first class #TreeSitter and #LanguageServerProtocol support (and I wanted both).
My hunch was improving mouse support in hx was much more doable (correct, as that PR showed - but it never got accepted), and I've been using hx.
Meanwhile LSP support doesn't seem to have improved much in Micro, sadly. eg LSP feature request https://github.com/micro-editor/micro/issues/1138 opened in 2018 and closed in frustration in 2023, and discussion https://github.com/micro-editor/micro/discussions/3231 links to several since abandoned plugins, but also https://github.com/Andriamanitra/mlsp/
-
@gedankenstuecke @Kroc Our cluster admin tolerated using VS Code, but people regularly ignored the guidelines and bogged down the head mode.
I never liked VS Code, and am still learning the ropes with #HelixEditor after years of using surface level emacs. The #MicroEditor is also nice (with better mouse support), but having built-in LSP support is great (this powered much of what appealed to me in VS Code).
-
For example, just one of my #DotConfig files currently in flux is my #HelixEditor and #MicroEditor configurations (which I want to be able to use on remote servers and clusters), as I fine tune the keyboard mappings - using scp to sync assorted #DotFiles between machines is getting tedious!
-
Trying out two terminal editors (#HelixEditor and #MicroEditor), and starting to work out what I like best in each that is missing from the other, e.g. helix mouse support is lagging https://github.com/helix-editor/helix/issues/12500 while micro’s Python syntax support doesn’t handle f-strings yet https://github.com/zyedidia/micro/issues/3605
-
@b0rk thanks for sharing this. I’d already had a play with the #HelixEditor (impressive first class #LanguageServerProtocol support) and had a look tonight at the #MicroEditor (nice mouse support, assorted plugins but no official channel). Neither seems a perfect match but with a little personalisation either might serve - precisely your wider point about effort and configuration 😉
-
@b0rk thanks for sharing this. I’d already had a play with the #HelixEditor (impressive first class #LanguageServerProtocol support) and had a look tonight at the #MicroEditor (nice mouse support, assorted plugins but no official channel). Neither seems a perfect match but with a little personalisation either might serve - precisely your wider point about effort and configuration 😉
-
@b0rk thanks for sharing this. I’d already had a play with the #HelixEditor (impressive first class #LanguageServerProtocol support) and had a look tonight at the #MicroEditor (nice mouse support, assorted plugins but no official channel). Neither seems a perfect match but with a little personalisation either might serve - precisely your wider point about effort and configuration 😉
-
@b0rk thanks for sharing this. I’d already had a play with the #HelixEditor (impressive first class #LanguageServerProtocol support) and had a look tonight at the #MicroEditor (nice mouse support, assorted plugins but no official channel). Neither seems a perfect match but with a little personalisation either might serve - precisely your wider point about effort and configuration 😉
-
@b0rk thanks for sharing this. I’d already had a play with the #HelixEditor (impressive first class #LanguageServerProtocol support) and had a look tonight at the #MicroEditor (nice mouse support, assorted plugins but no official channel). Neither seems a perfect match but with a little personalisation either might serve - precisely your wider point about effort and configuration 😉
-
The correlations between #typesetting engines to their #terminal text editors are irrefutable:
* #TeXLaTeX is #emacs.
* #SILE is #neovim.
* #Typst is #helix.
* #WeasyPrint is #nano.
* #Speedata is #microeditor
Now back to your regularly scheduled indentation. -
Oh my goshhh... 😱
After #Geany also the #microeditor got a #LSP implementation! 😭
My two favorite editors are getting serious!
😎
-
E via, ora che ho preso una tastierina per il tablet #Android, non potevano mancare #Termux, #Ranger per file manager e #MicroEditor, così posso scrivere in estrema mobilità senza dover toccare mai lo schermo. Per ora sono soddisfatto così, devo solo spostare le configurazioni di Ranger e Micro per personalizzare il tema.
Poi, con calma, vedrò se sarà il caso di vedere se non servirà fare i salti mortali per mettere evil e la org mode, così magari ci butto su anche #Emacs. Ma mooolto con calma. -
It's a very specific to me terminal workflow, but I must say: the combo of #Wezterm + #Nushell + #MicroEditor works pretty darn nice for me across Windows, Linux, and macOS.
-
Big editors are fun, but I really do prefer
$EDITORto be smaller and more focused. Plugins are okay, but not so much "redefine your whole workflow and learn a new packaging system twice a year just for your editor."Anyways, just my periodic cheerleading for #MicroEditor after I installed its LSP plugin. The bindings were listed right there in the README, and I didn't have to tune anything to get
golspworking with this code.GitHub - AndCake/micro-plugin-lsp: An LSP Client implementation for the Micro Editor
-
Hmm, apparently #MicroEditor needs either xclip on #X11 or wl-clipboard on #Wayland to allow to copy from it and paste outside it.
-
As editors do more and more I find myself cozying up closer to stuff like #MicroEditor that does just a little bit less.
-
Need to update some #Nushell config for 0.78 and a pleasant surprise with #MicroEditor giving me syntax highlighting! The name's a pun on Nano because it's supposed to be kind of a minimal editor, but it's full of happy little surprises.
-
Finding the #microeditor to be a really nice replacement for #emacs so far.
-
@RL_Dane <serious>
Take a look at #microEditor https://micro-editor.github.io/
It's really good with being intuitive to use. It's also really nice to work with.
</serious> -
Do you enable line numbers in the margin of your text editor? (boost for more data!)
#emacs #vim #vi #nano #microeditor #kakoune #kak #vis #viseditor #vscode #atom #texteditor #notepadplusplus #notepad #text #editors #programming #coding #writing #poll #linenumbers
-
CW: re: Python CLI workaround for accessing Kate bookmarks.
@woozle yeah, I realise the command-line isn't for everyone. :)
Still, was a nice exercise for me. ;)Recording of the final version that uses #fzf to filter and preview, and #micro editor to edit (while focused on the bookmarked line): https://asciinema.org/a/YQSLCHdawYpL8PosYFgvvAKJB
(Using #microEditor as editor in this example since I couldn't figure out how to launch the Windows version of #KateEditor from the #WSL command-line).
And for completeness sake, even though it won't be useful to you, the final source code:
#!/usr/bin/env python3
import linecache
from pathlib import Path
import configparser
config = configparser.ConfigParser()
config.read('/mnt/c/Users/FiXato/AppData/Local/Packages/KDEe.V.Kate_7vt06qxq7ptv8/LocalCache/Local/katemetainfos')
for section in config.sections():
clean_section = section.replace('file:///C:/', '/mnt/c/')
filename = str(Path(clean_section))
if not config[section]['Bookmarks']:
continue
for linenr in config[section]['Bookmarks'].split(','):
line = linecache.getline(filename, int(linenr) + 1)
print(f"""{int(linenr) + 1} {filename} # {filename}:{int(linenr)} # {line.strip()}""")and the launcher #oneliner:
./fzf-katemarks.py | fzf --with-nth 4..-1 --preview="sed '{1}q;d' {2}" --bind "enter:execute(micro '{2}':{1})"