8 ms·
In neovim, :X (and cryptography in general) is removed https://github.com/neovim/neovim/commit/85338fe https://github.com/neovim/neovim/commit/85338fe
by kqbx 4y ago
In neovim, :X (and cryptography in general) is removed
https://github.com/neovim/neovim/commit/85338fe https://github.com/neovim/neovim/commit/85338fe
- freedomben 4y agoThanks great link. tldr: > vim encryption uses old, obsolete algorithms that are poorly implemented. Since insecure cryptography is worse than no cryptgraphy, the community voted in favor of removing all crypto.
- jpavel2 4y agoThis was in 2014. Since then, Vim has added non-obsolete encryption algorithms (some provided by libsodium), used by default.
- raydiatian 4y agoThis is different from :x though
- isbjorn16 4y agoI think their point is sometimes their left pinky is a bit lazy and won't get off the fucking shift key
- raydiatian 4y ago[dead]
- ajford 4y agoI've been a vim user for 15 years and I still often type `:Q` and `:W`. Everyone types differently and some people make mistakes. Your blaming the victim instead of the software.
- raydiatian 4y agoWhat parent @waisbrot is saying seems uncommon (the source of this whole conversation), but granted, perhaps common enough (or is it instead worrisome enough) that nvim community took it out. I still type :Q and :W as well, but that is not what is being discussed. Have you ever irrevocably bricked your system, as @waisbrot mentioned they have twice, from typing :W or :Q? Have you ever bricked your system from typing :X? If so, that isn’t a “use :x vs :wq” problem, that’s seems more of a use common sense problem.
- mega_dingus 4y agoOP said exactly "I've twice encrypted my file with password like `cd tmp`" Not sure how you get "irrevocably bricked your system" from "encrypted my file", but you do you, I guess You should also let the OP do the OP. They said they made a mistake. Simply, without complaining, and they do something else now. It's that simple
- raydiatian 4y agoParent (not OP) said more exactly > I've twice encrypted my file with password like `cd tmp`, then saved the config file, breaking my system. I get “irrevocably bricked system” from the fact that they “broke their system” and I am inferring it could only be something worth mentioning if it were irreversible. I originally was trying to point out that parent was off-topic, because :x and :X are different. But a fleet of downvotes flooded in, so I defended my viewpoint for the catharsis.
- isbjorn16 4y agoMe either, but that's because I type `:wq!` every single time instead. I'm not one of those who is afraid of typing more than a single character so I don't care if it's actually 3 I'm hitting. I am someone whose entire brain comes to an absolute crash if I type "wq" and it's asking me if I want to save over a RO file. It's like having a belt loop or pocket catch on a door handle and I despise it. So, `:wq!`, or as I call it "write the fucking file and quit, _with feeling_"
- an-honest-moose 4y agoThe only reason the footgun is there is because vim put it there. Seems reasonable to me to be frustrated by that.
- raydiatian 4y agoThen upgrade to nvim like everybody else idk
- the_fury 4y agoIt is, but accidentally hitting capslock instead of shift when hitting the colon is extremely easy to do.
- drdaeman 4y agoCaps Lock is that key that's best replaced with Ctrl? ;)
- MayeulC 4y agoOnly for Emacs users. Vim users generally replace it with Escape.
- bombela 4y agoExcept that vim was designed on a keyboard with the Ctrl key at the place of your current capslock (for most keyboards, Japanese still have Ctrl at the "right" plac).
- vasac 4y agoWhy not both ;) - ESC when tapped, CTRL as a modifier key when pressed together with some other key.
- MayeulC 4y agoGood idea! Though aborting a Ctrl-C could close a dialog window :/
- pxx 4y agoI'm a vim user and replace it with Ctrl. It's much more useful and you can use ^[ to get Escape.
- still_grokking 4y agoI like Compose on CapsLock more.
- tomcam 4y ago