Editing Code in Emacs
Mood
informative
Sentiment
positive
Category
tech_discussion
Key topics
Emacs
Code Editing
Productivity
Discussion Activity
Moderate engagementFirst comment
4h
Peak period
8
Hour 5
Avg / period
4.5
Based on 36 loaded comments
Key moments
- 01Story posted
Nov 23, 2025 at 9:59 AM EST
16h ago
Step 01 - 02First comment
Nov 23, 2025 at 1:42 PM EST
4h after posting
Step 02 - 03Peak activity
8 comments in Hour 5
Hottest window of the conversation
Step 03 - 04Latest activity
Nov 23, 2025 at 8:59 PM EST
5h ago
Step 04
Generating AI Summary...
Analyzing up to 500 comments to identify key contributors and discussion patterns
Is there still hope for me?
I think my biggest issue is that I am a slow coder and I never feel in a hurry.
I am an experienced emacs user and I still use CUA mode, arrow keys, and I wrote a package which completely overhauls built-in "word jumping" commands (called bbww on melpa.)
You don't need to worry about upholding traditional emacs orthodoxy
Emacs shines when packages combine to form a whole greater than the sum of its parts. Changing basic key bindings is the quickest way to vitiate that symbiosis.
Unfortunately.
And while they may be old school, traditional, and orthodox, they are by no means idiosyncratic. They’re widely supported: readline , bash, everywhere on macos, even modern browsers. Eg you can actually paste in bash: try killing something with C-w or C-k, and paste it back using C-y. Or transpose arguments using C-M-t. Navigate suggestions in Firefox using C-n and C-p. Bash even supports undo using C-/.
All to say: learning emacs movement keys pays off.
Though I have one minor nit against one point, that I've seen basically in every similar article:
> This means no arrow keys and no mouse
I use Neovim daily, and there is no denying that 98% of the time, using mouse is less efficient than doing a fancy search or jump. But for the remaining 2%, it's provably true that mouse is better - like, selecting an arbitrary block of code (without {} or any keyword to hang on). So I always recommend leaving the mouse enabled. Just use it when it makes sense.
This is definitely true. The thing is that using the mouse is a habit, and until you break it, people find themselves instinctively using it in situations where it would be better to use the keyboard. So the 'hard' mouse disable is more of a 'going cold-turkey' type thing to try and break the habit. I agree that once it's broken it makes sense to relax this.
(or I could pick up the mouse, I know, but that's not why we're here)
(This is my understanding at least; I'm open to correction.)
I'm a lover of Vim bindings, and so I appreciate keyboard controls, but where Vim enables working with files and text in a general and powerful way, avy enables avoiding one click with the mouse. I don't use Vim to avoid the mouse, I use it so I can hack some Vim macros together when I'm editing text on a text-level. Vim (or Emacs) is an eternal tool that can do big things, avy just positions my cursor.
I feel like moving from a large monitor to a small monitor would limit the usefulness of avy; it's weird that the physical size of a monitor would limit a tool like this.
I almost never use windows. I almost never look at more than one file at once that fills my entire screen. Can avy still do things for me?
avy does more than just jump the cursor to a specific place. It also allows you search for, copy and move text round without needing to move your cursor to that text. It is extremely easy to use and very efficient.
What I love about functionality like this is it's completely generic. It's just text. I don't need any lsp support to get me "go to def" or something. I can open a file in a language I've never seen before and use the exact same interface I'm used to to navigate around.
Maybe if I combine it with eye tracking so I can limit letter assignment to the foveated region I can reduce the cycle count and make this style of navigation win.
C-x p f (find any file in the current "project", e.g. git repo)
C-x p v (grep the whole project super fast)
It's embarrassing how long it took me to realize it was there all along. :-)
Maybe a bit OT, but I think I saw here a week or more ago a post about magit, I am toying with using it, but seems to be a rather big package. Plus I wonder why dash is needed:
https://emacsdocs.org/docs/magit/Installing-from-the-Git-Rep...
In anycase to avoid downloading additional packages I may use Melpa
I really like Emacs' flexibility + evil-mode and reactivity, recently I searched for something similar and found Lem: https://github.com/lem-project/lem, looks promising, I'll try it out and compare with Emacs when I have the chance and time.
A few useful pieces of advice beside that, too. The workflow the author describes is not how I prefer to do things, but the author mentions a number of important capabilities to be aware of: operating at sexp level, subword motion, etc. Narrowing and folding, which I like to use, are not mentioned.
No mention of LSPs or compilers, but these are their own large topic.
Want the full context?
Jump to the original sources
Read the primary article or dive into the live Hacker News thread when you're ready.