Skip to main content

in reply to It's FOSS

In the terminal, I like Micro but I just came across Amp (terminaltrove.com/amp/) today and I need to give it a look.
in reply to Ike

@ike
I've been using #NeoVim for a while now. And honestly the learning curve to configure all the plugins really is a bit much. While I have a nice config I've been using for a while now, I've been tempted by some newer simpler editors like #HelixEditor. I've been peeking at that one lately. Looks like it might be a bit similar to Amp that you mention. I'll have to give that a look.
in reply to Mark Stosberg

@markstos @finner @ike alternative solution: stop installing new plugins? I'm using the same six I've had for about ten years.
in reply to Jonathan Hartley

@tartley @finner @ike I previously posted an analysis of my Neovim plugins. I had 34 and all but about 4 were replaced by the out of the box #HelixEditor functionality.

It’s not that I want extreme or exotic configuration, but that expectations have been raised for what’s considered basic functionality. Fuzzy finders, LSP language enabled, git integration all seem like things that shouldn’t require plugins now.

in reply to It's FOSS

the editor wars #vi vs #emacs are over #vi won.
The current editor war is #vim vs #nvi
#emacs #vi #vim #nvi
in reply to It's FOSS

I found micro and switched to that. I only use vi/vim if I am on a remote server and I need to edit a file.
in reply to It's FOSS

I like base vim, I'm going to change to nvim at some point
Unknown parent

mastodon - Link to source
It's FOSS
@nazokiyoubinbou If it works, it works! 😄
@Nazo
in reply to It's FOSS

pico/nano, vi/vim at command line.
Geany, Gedit, Kwrite/Kate, Leafpad, Mousepad when in graphical mode!

I mostly work with the tools I've at that moment.

in reply to Zabuxx

@Zabuzzman You actually started with Emacs as your first editor? 😲
in reply to Karl Voit

@publicvoit Well, I did flirt around with Vi and Pico, but settled for Emacs pretty fast. Also, Emacs was "strongly" encouraged on my first job (1999), those key-bindings have been a second nature since.
in reply to Karl Voit

@publicvoit Very nice article! Seems our paths were rather similar! Just wondering, was not Pico the editor of Pine instead of JOE?
in reply to Zabuxx

@Zabuzzman 🤔 Hm, possible.

From en.wikipedia.org/wiki/Pine_%28… and en.wikipedia.org/wiki/Joe%27s_… I can not tell.

The first mentions:
"its message editor inspired the text editor Pico." ... which would indicate that Pico is not the editor of Pine.

in reply to Karl Voit

@publicvoit en.wikipedia.org/wiki/Pico_(te…

From the Pine FAQ: "Pine's message composition editor is also available as a separate stand-alone program, called PICO. PICO is a very simple and easy-to-use text editor offering paragraph justification, cut/paste, and a spelling checker..."

in reply to Karl Voit

@publicvoit @Zabuzzman pico was written for and bundled with pine. In fact it was the only way to get pico back in the early 90’s.
in reply to It's FOSS

Vim or Neovim for me, but I hear you: Use what works for you!
in reply to It's FOSS

the arc of the editor universe is long, but it bends towards vim
in reply to It's FOSS

Sublime Text is the God.
If I need to edit in terminal, like writing emails or something, then vim.
in reply to It's FOSS

NE or Nano. It depends what I'm doing.
NE definitely needs more love round here. 😃👍
in reply to It's FOSS

Gedit for simple GUI editing, Neovim for everything else.