vim-sensible VS micro-editor

That’s a good question. The built in tutorial is actually really good, you can launch it with “vimtutor” on the command line. It doesn’t give you everything, but its instructions and text to try things out on in the editor itself, which I find a good way to learn. It isn’t particularly programming focused either.

For getting used to the motions especially https://vim-adventures.com can be a fun way, in its game format.

For getting started I’d say don’t worry about plugins much, but get https://github.com/tpope/vim-sensible at least so the defaults meant for vi don’t get in the way. The only other thing you might want is a format syntax if your preferred note syntax isn’t highlighted well by default or something. Polyglot can be good to stave that off but really I’d say learn on a really lean config, and get used to using :help or similar. It’s the best way to learn the parts that work everywhere.

it's modified from tpope's https://github.com/tpope/vim-sensible, and https://github.com/mhinz/vim-galore#tips-1.

I didn't realise vim Vs vi purist was a thing.

I'm aware that for a while vim has had some backwards compatibility setting that people recommended turning off to get more modern defaults.

And that Tim Pope had a plugin that took you one step beyond that:

https://github.com/tpope/vim-sensible

> Think of sensible.vim as one step above 'nocompatible' mode: a universal set of defaults that (hopefully) everyone can agree on.

And that neovim took the opportunity to make an updated set of defaults:

https://neovim.io/doc/user/vim_diff.html#nvim-defaults

tpope/vim-sensible, because the Vim defaults aren't for everyone.

A while back I did a public Neovim options survey (here are the results). One of the goals was to gather a commonly used option values to create a "crowd-sourced" moderate version of tpope/vim-sensible. Well, this is it.

opps.. forgot to mention timpopes : https://github.com/tpope/vim-sensible settings :D

You don’t want any modern conveniences? Not even stuff from here[0]?

[0]: https://github.com/tpope/vim-sensible/blob/master/plugin/sen...

If you use vim-sensible, which you should, you can reset the highlight with ctrl+l.

Check out sensible.vim for lots of settings you might want to turn on.

What I plan to do with results: - The summary of results will be released in some way, shape, or form after survey is closed (at least two weeks from now when there is a 24 hours without new entries). It will be announced in this sub. - Possibly use the most commonly set non-default settings to power a Neovim variant, crowd-sourced version of tpope/vim-sensible.

To see more screenshots of micro, showcasing some of the default color schemes, see here.

Not sure these are really popular, but I cannot resist advertising a few utilities written in Go that I regularly use in my daily workflow:

- gdu: a NCDU clone, much faster on SSD mounts [1]

- duf: a `df` clone with a nicer interface [2]

- massren: a `vidir` clone (simpler to use but with fewer options) [3]

- gotop: a `top` clone [4]

- micro: a nice TUI editor [5]

Building this kind of tools in Go makes sense, as the executables are statically compiled and are thus easy to install on remote servers.

[1]: https://github.com/dundee/gdu

[2]: https://github.com/muesli/duf

[3]: https://github.com/laurent22/massren

[4]: https://github.com/xxxserxxx/gotop

[5]: https://github.com/zyedidia/micro

> The worst way to store and manipulate text is to use an array.

Claim made from theoretical considerations, without any actual reference to real-world editors. The popular Micro[1] text editor uses a simple line array[2], and performs fantastically well on real-world editing tasks.

Meanwhile, ropes are so complicated that even high-quality implementations have extremely subtle bugs[3] that can lead to state or content corruption.

Which data structure is "best" is not just a function of its asymptotic performance. Practical considerations are equally important (arguably more so).

[1] https://github.com/zyedidia/micro

[2] https://github.com/zyedidia/micro/blob/master/internal/buffe...

[3] https://github.com/cessen/ropey/pull/67

There are two main ways to configure sudo.The first one is using the sudoers file.It is located at /etc/sudoers for Linux,and /usr/local/etc/sudoers for FreeBSD respectively.The paths are different,but the configuration works in the same way. A typical sudoers file looks like this. The sudoers file must be edited with the visudo command,which ensures the config is free of errors.Running this command as the root user will result in opening vi by default.If you want to use a different editor you can set the VISUAL environment varaible to the editor you want. For example,if you want to use micro as the text editor run:

found that micro has dedicated info page for copy paste

micro: winget install zyedidia.micro