61–70 of 102 posts
If you're on OSX and want a good Emacs, go to https://github.com/railwaycat/emacs-mac-port and read the installation instructions under the Homebrew section. It follows the official Emacs repo pretty closely, but has useful OSX additions (smooth scrolling, gesture support [font size e.g] and more).
I get my emacs from here http://emacsformacosx.com
Earlier quoted context omitted.
ctrl-k ctrl-y ?
Not quite the same. For instance, to duplicate a line in Emacs you have to go to the beginning of the line, kill it and then yank twice, and it doesn't even work always, particularly at the end of a buffer. In vi, it's just yyp. No corner cases.
What I like most about emacs though is that I rarely have to do repetitive tasks because I can write a bit of lisp code to do them instead.
I hadn't tried Magit before now, but on the suggestion of this blog I'm giving it a look through. Looks good so far. I also enjoy the style the blog is using: anyone know what backend the author is using?
One thing I hated about magit was that I couldn't stage multiple files with a region or similar. I'm currently on my phone for the rest of the evening so I won't have chance to check - if you notice this has arrived in your testing, do let me know! I usually use shell emulator + company for dir/file autocomplete. This is the fastest I've got to staging individuals files or dirs, especially with projects that have a d…
I can also expand them and highlight multiple chunks to stage just those chunks.
The are only two major things I don't know how to do with the current stable version of Magit (1.4). One is starting an interactive rebase. It can take you through the commits and let you edit the buffer, but I haven't figured out if it's possible to start an interactive rebase without using the "!" command line.
The other thing is checking out files in order to revert them, I'm sure there's a way but using "!" and pasting the file names in still seems fastest.
I've also been wondering if it's possible to write a command to manage the `--skip-worktree` status of files, showing which are currently skipped in magit-status-mode. That would be a useful thing for me to have.
Earlier quoted context omitted.
Intuitiveness is subjective. Take cursor movement for example. I understand now h,j,k,l is a remnant from historic keyboards, but when I started learning vim, I couldn't fathom why 'h' moves a cursor to left and 'l' to the right, though I got used to it eventually. The emacs 'C-f' for forward and 'C-b' for backward were definitely more intuitive. Of course, depending on the mode, some emacs commands can be cryptic an…
hjkl is QWERTY-centric, and would be totally nonsensical to a user of a different keyboard layout, like Dvorak. C-f, C-b are English-centric, and would be totally nonsensical to a user of a different language. Intuitive is hard.
I hadn't tried Magit before now, but on the suggestion of this blog I'm giving it a look through. Looks good so far. I also enjoy the style the blog is using: anyone know what backend the author is using?
One thing I hated about magit was that I couldn't stage multiple files with a region or similar. I'm currently on my phone for the rest of the evening so I won't have chance to check - if you notice this has arrived in your testing, do let me know! I usually use shell emulator + company for dir/file autocomplete. This is the fastest I've got to staging individuals files or dirs, especially with projects that have a d…
Is it weird that I wish somebody would make a terminal-ized version of newer editors like Atom/ST/Brackets?
I haven't read this, but from the contents it seems like you can learn everything there is in the book from the official Emacs GNU documentation: https://www.gnu.org/software/emacs/manual/html_node/emacs/in...
I'm embarrassed to say how long I used Emacs knowing about C-h f -- but not noticing and using C-h i to read the full documentation from inside Emacs. I wish I'd appreciated that from the start.
At this point I've read the full Info doc at least once through, some sections multiple times. It's impressively good, especially for getting a crisper understanding of topics you only sort of understand. It's one of Emacs best features.
But I can totally see the value of a good introduction book, and wish I'd had one when I was starting out. So although I don't know how good this book is, I don't think a book is pointless.
I really like this blog, it's great. Very engaging. Would recommend subscribing to it! ps thanks for the downvote HN - classy :-)
I didn't downvote your post, but I can see why others might feel that it doesn't contribute to the conversation because basically the only possible responses are "Me too" and "You are wrong". Adding the complaint about the downvote would ordinarily get a downvote from me, but I'd already used my vote in search of justice. Anyway, consider the downvotes editorial feedback and perhaps taking advantage of the opportunit…
Earlier quoted context omitted.
ctrl-k ctrl-y ?
Not quite the same. For instance, to duplicate a line in Emacs you have to go to the beginning of the line, kill it and then yank twice, and it doesn't even work always, particularly at the end of a buffer. In vi, it's just yyp. No corner cases.