Open DoTheEvo opened 4 years ago
Yeah I get that this is annoying. Early on, Ctrl-d
was bound to "duplicate line" before multiple cursors existed in the editor. I've tried to avoid changing default bindings, but maybe this is a case where the change is warranted.
I use ctrl+d as duplicate line
for years, so I like the way alt+n
is right now, So please if changing add an option for it to be opt-in.
How and where exactly would he add some opt-in option? It does not work like that I fear.
Either all them people coming from sublime text, atom, VScode and probably some other editors... will be forced to change settings, or few people who got used to double the line with it will have to change keybinds.
@DoTheEvo on the settings.json
file it can be included a feature flag? or maybe just the matter of changing the Keybind (is not that already possible right now?)
micro has been added to the official repository on arch.
Thought it is a good opportunity to remind that it might be a good idea to rip off the band aid before it takes off even more with bigger number of users, and make micro more in line with what is contemporary standard.
Again, VSCode, Atom, Sublime all share same hotkey - ctrl+d for multicursor. That is a huge chunk of the text editor market, millions of people worldwide and it is of course expected to grow.
It would be so nice to just have this editor in distros and be usable in large regard without need to edit settings and customize.
thnx.
Just imagine that in ~10 years when it will be as wide spread as nano, and be in every distro.. that changes like these were what made life of people using it easier.
In 2022 I would like to again ask for switch default hotkey to be more compatible with major other editors. particularly the huge rise in VScode is what makes more people feel at home in micro, rather than notepad++ userbase that is used to doubling.
finally a great terminal editor with flawlessly working multicursor out of the box.
Puts the default hotkey on two hand, or acrobatic pinky hotkey alt+n
ctrl+d used by sublime, VSCode or Atom might be problematic for some I guess, as it logs out of terminal, but inside the editor it works nicely... and considering how nicely micro is keeping with ctrl+z and ctrl+s and ctrl+c and ctrl+v,.. to which old school might also rebel..
well I keep changing it obviously in my config, it would just be nicer if it was just there