111–120 of 507 posts
> Programmer standing next to the SAGE computer's control program
> Image courtesy the Computer History Museum and the MITRE Corporation
I switched from emacs after college and haven’t looked back. Plus everyone constantly ridiculed me for using it.
Does anyone have a good video comparing vim speed coding vs vscode using built in editor features? I’ve been using vscode for years and the YouTube videos that demo vim features are shallow (like how to enter a blank line - really?). I can do the same thing I have seen in vim videos without memorizing a bunch of strange key bindings all while being able to edit code instantly without changing modes. I would love to s…
you totally can! I could talk for a while about customization and ctags to address some other points you made but at the end of the day its a text editor, vim and vscode are both text editors. it sounds like you really like using vscode so you should stick with it, I really love vim and it works really well for me, and my boss loves using a near vanilla sublimetext 2 install. programming will never be about typing and editing speed but being comfortable with your development environment and hopefully even enjoying it is very important.
Comes with every *nix distribution. Fast to start. I use Emacs for programming but if I have one single file, like a config file, that needs a quick edit, use vi(m) because otherwise I have to either: 1. Go to my open Emacs and navigate to the location of the file needing the quick edit 2. Open a second Emacs instance, and hope I don't lose the desktop settings for the "real" instance. Especially if the file needs to…
I'm confused by your workflow. Why are you opening a second Emacs instance? In Emacs you just C-x C-f /path/to/config, for sudo C-x C-f /sudo::/path/to/config. Starting location will be home, or the parent of the active file (if the active buffer is an editor).
Even though I live in Emacs, I frequently use GP's workflow as well. For me, it's often the fact that I am already working in the terminal when I need to edit the config, so going to Emacs is a context switch. Moreover, I often fist do a cd /path/to/config; once there it's trivial to do vim foo or sudo vim foo.
I have an alias that can send that file to emacsclient -- but again, it takes me away from the terminal, and will not work with sudo.
Also, I've tried possibly every emacs package that helps with path completion, but they all seem to get in the way when I already know exactly what I want. Vanilla bash completion (and don't forget about fzf!!) are a better experience for me; YMMV.
Earlier quoted context omitted.
Kakoune is definitely an attempt at redoing the vim concept from scratch. I spent a few weeks trying it out and attempting to get used to it. Ultimately, I came away from it feeling disappointed. I think the basic premise of multiple cursors editing as a preferred model (which is what Kakoune does) is flawed. Why? Because large-scale scale changes are the exception, not the rule. By emphasizing multiple cursors, Kako…
If you stuck with it long enough do you think the multiple cursors would have given you an increase in productivity over vim? Like maybe it has a high learning curve (like vim).
Others have tried kakoune and really loved it. I don't understand it. I really tried to figure it out, I just don't grok it.
[1] https://www.oreilly.com/library/view/learning-the-vi/9780596...
Earlier quoted context omitted.
AFAIK it still tries to stay mostly compatible with regards to how it is controlled, doesn't it? So while the internals are perhaps new, the frontend is not. But I think Kakoune https://kakoune.org would fit the bill
Kakoune is definitely an attempt at redoing the vim concept from scratch. I spent a few weeks trying it out and attempting to get used to it. Ultimately, I came away from it feeling disappointed. I think the basic premise of multiple cursors editing as a preferred model (which is what Kakoune does) is flawed. Why? Because large-scale scale changes are the exception, not the rule. By emphasizing multiple cursors, Kako…
Earlier quoted context omitted.
Kakoune is definitely an attempt at redoing the vim concept from scratch. I spent a few weeks trying it out and attempting to get used to it. Ultimately, I came away from it feeling disappointed. I think the basic premise of multiple cursors editing as a preferred model (which is what Kakoune does) is flawed. Why? Because large-scale scale changes are the exception, not the rule. By emphasizing multiple cursors, Kako…
I switched to kakoune from vim in early 2020, and I really like it (previously: emacs 1994-2004, vim 2004-2020). It's worth prefacing what follows by saying that I heavily relied on the visual selection features in vim. kakoune provides a limited orthogonal toolset that composes extremely well. After a week using kakoune I felt at least as confident with its command language as I did with vim's after years of use. As…
> Kakoune actively makes it harder to do the normal thing people do in a text editor: jump around a file and make specific edits to individual lines. Instead, a bunch of normal movement commands (such as forward and backward search) leave extra cursors in your wake, forcing you to press an extra key to dismiss them otherwise you'll get erroneous edits
Do you find that's the case? If so, how do you deal with it? Just remember to dismiss the extra cursors?
Disappointed the article went straight from punch cards to video terminals without mentioning teletypes. > Having that thing show up on computers in those days was pretty tricky, and some considered it a resource hog. Well in the 60's and 70's, you didn't necessarily even have a display, you might be using a physical teletype. `ed` is built for that. Even when you had a display, it could be slow. The VT05 from 1970,…
https://m.youtube.com/watch?v=2XLZ4Z8LpEE
Watching it for the first time is what finally made ed click for me.
And yes, I was disappointed that the author clearly didn't understand why ed has the UI it does. It's about the teletype, not the computational cost of having a WYSIWIG UI.
Earlier quoted context omitted.
Kakoune is definitely an attempt at redoing the vim concept from scratch. I spent a few weeks trying it out and attempting to get used to it. Ultimately, I came away from it feeling disappointed. I think the basic premise of multiple cursors editing as a preferred model (which is what Kakoune does) is flawed. Why? Because large-scale scale changes are the exception, not the rule. By emphasizing multiple cursors, Kako…
I switched to kakoune from vim in early 2020, and I really like it (previously: emacs 1994-2004, vim 2004-2020). It's worth prefacing what follows by saying that I heavily relied on the visual selection features in vim. kakoune provides a limited orthogonal toolset that composes extremely well. After a week using kakoune I felt at least as confident with its command language as I did with vim's after years of use. As…
Most of what I do in vim is now so heavily ingrained in muscle memory that I just don't think, I see the text change to what I want it to be. Perhaps that's too hard of a habit to break for me.