3 ms·
Yeah, but it's possible to quickly type the next command (that you would after exiting vim) as the encryption key. That said, given that neovim doesn't have th
by manaskarekar 4y ago
Yeah, but it's possible to quickly type the next command (that you would after exiting vim) as the encryption key.
That said, given that neovim doesn't have this feature at all makes it less of an issue to me.
- bravetraveler 4y agoOn my build, I have to confirm the key -- is this not the case with yours? I suppose one could naively type the same thing twice, but I feel like some caution also goes a long way. Driving without looking at the road is generally dangerous Any time I accidentally shift-mod my saves, I immediately see the encryption prompt, and back out with SIGINT. I don't really buy the problem, so to speak
- withinboredom 4y agoOn a laggy/slow ssh connection, if you don't notice the encryption prompt, it is quite easy to just try the exact same thing again.
- bravetraveler 4y agoIndeed - hence the tendency towards caution over what I type I understand how it manifests... but I find it not that difficult to avoid My answer to lacking feedback isn't moving forward headstrong - it's verify the delicate combination went through fine
- withinboredom 4y agoEveryone has different responses when things don’t work out exactly how we think they will. Ideally, we write software that doesn’t surprise us, however we choose to react.
- bravetraveler 4y agoThe endless battle continues, be brave