![]() ![]() The corporate image hasn't caught up yet with the creators edition. I ended up switching back to basic PuTTY for SSH and will only use CMDer when I absolutely need to interact with my windows box in a POSIX environment. plus just do a quick search and you'll find many other complaints online). ![]() the latency of the tool was unbearable (at home and work, so it's not just my corporate environment. I switched to CMDer which is beautiful and wraps Git Bash, but alas. I used to use BusyBox tools on windows and LOVED them! But work now utilizes an anti-virus/malware tool called Cylance and it kills anything from BusyBox. Maybe you've tuned your configurations, and if so please provide the deets, but I know I'm not alone in the default config being abysmally slow. I do too, and I've been using vi 20+ years.Īctually it doesn't matter if I'm on my developer laptop (which is a beast) or my high (okay mid. But it's no surprise that new users find these two things awkward. I guess both have historical reasons, and of course you can change default behaviour. so why not have :q (the lesser used function) assigned to macros instead? ![]() surely they need to quit more often than record macros. Even for users that make lots of use of macros. Given that this issue alone is the #1 reason behind vi's reputation issues - you'd think there could at least be a tip shown on screen to help the n00bs out (like there is for ctrl-c). Not only does it not do what the user expects, but it takes the user another level further away from that. q will quit many other interactive terminal programs, including less / man pages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |