Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Mastering Emacs

masteringemacs.org

Post reply on HN
Print view View original

81–90 of 131 posts

Re: Mastering Emacs

#81

Post by bjoli »

pluijzer wrote: post #63
geokon wrote: post #48

Earlier quoted context omitted.

> "M-x magit" get a nice list of the status of the files in the current branch. Except it will randomly split your frame and show up in a seemingly arbitrary location - often obscuring what you're working on. I find the whole layout system in Emacs completely chaotic. I guess it comes with the flexibility (VS a fixed system like most Ides) nor do I have any particular solution in mind I'm curious if anyone has tamed…

I have my Emacs setup to never split anything and just use the whole frame (window). That also goes for things like helm. Instead of splitting I prefer to open multiple frames and let my window manager, manage them. This really improved my workflow.

Same here, but I let most things replace the current buffer. Magit always fills the frame though.

Re: Mastering Emacs

#82

Post by onehair »

lbj wrote: post #15

It's crazy that here in 2023, Emacs is still the absolute beast when it comes to developer productivity. I had a colleague review one of my workflows the other week and after a minute or so he said "Whoa, I would have been in 5 different tools by now". If you're not into Emacs, I suggest you give it a whirl. For most development, nothing else will get you close to the joy and productivity that a well configured Emacs…

> that a well configured Emacs can

Well, that's the real issue for me. I spent a month an a half working on "configuring" NeoVim. I got it to a somewhat ready to use state for my usual workflows. But I still had a big pile of tasks in my backlog to actually get it finally 100% mine.

Then I discovered Helix, which doesn't need any configuration, no plugins to play around with. Builtin LSP, Builtin Fuzzy Finding of files, TreeSitter and the list goes on.

Even though it's still not fully checking all the boxes I need to have a 1 to 1 mapping of my previous workflows to what Helix offers. I find not having to build my own editor out of the Lego pieces and always needing to improve what it can offer me, makes the editor actually enjoyable.

IMO, VIM, NeoVIM and Emacs should start looking into implementing a bit more than just the barebones, some of these new features that people are accustomed to in 2023, and more and more will flock to these good editors.

Re: Mastering Emacs

#83

Post by omaranto »

lproven wrote: post #79

I will take the time to master Emacs when Emacs comes to meet me in the middle, and adopts what has been the industry-standard UI for a third of a century: CUA. I would love someone to do an Emacs distro which integrated ErgoEmacs into it from the beginning: https://ergoemacs.github.io/ No, CUA-mode is not enough.

Why is CUA-mode not enough?

Re: Mastering Emacs

#84

Post by MassiveBonk51 »

Emacs is quite alluring as an idea. I wish we had a "higher" level version of it that could support composing in proper browsers etc. Now I realize this is basically a tiling WM, but I guess I want more interoperability between programs and ability to pass data between them programmatically.

Re: Mastering Emacs

#85

Post by grymoire1 »

j7ake wrote: post #7
psunavy03 wrote: post #4

I don't see why people are still using 1970s-era IDEs in 2023. Sure, it's a joke that emacs and vim users are at loggerheads, but name me one user of either who isn't a graybeard at this point. And specifically a graybeard who refuses to use more modern tools.

Systems admin people who deal with computing clusters often use vim.

I would ssh into remote systems, start emacs as my first command, and do everything inside of that emacs window - editing (scripts, config files, code), running shell scripts and programs, reading man pages, executing make, compiling, etc.)

Others would use tramp mode, and open multiple remote sessions within a single emacs. This makes it easy to cut and paste between systems.

Re: Mastering Emacs

#86

Post by mrbadguy »

onehair wrote: post #82
lbj wrote: post #15

It's crazy that here in 2023, Emacs is still the absolute beast when it comes to developer productivity. I had a colleague review one of my workflows the other week and after a minute or so he said "Whoa, I would have been in 5 different tools by now". If you're not into Emacs, I suggest you give it a whirl. For most development, nothing else will get you close to the joy and productivity that a well configured Emacs…

> that a well configured Emacs can Well, that's the real issue for me. I spent a month an a half working on "configuring" NeoVim. I got it to a somewhat ready to use state for my usual workflows. But I still had a big pile of tasks in my backlog to actually get it finally 100% mine. Then I discovered Helix, which doesn't need any configuration, no plugins to play around with. Builtin LSP, Builtin Fuzzy Finding of fil…

[dead]

Re: Mastering Emacs

#87

Post by hatmatrix »

struanr wrote: post #46
jgilias wrote: post #37

Earlier quoted context omitted.

Try Doom Emacs and configure it with evil mode (vim keybindings). Presto, problem solved!

Also worth swapping the control and caps lock keys (system wide if possible). Takes a while to relearn but much easier to reach with your pinky.

On macOS, you can remap command to control within emacs.

Control with the thumb was the original configuration when emacs was built.

Re: Mastering Emacs

#88

Post by hatmatrix »

Been using emacs since 2003.

One thing I turn to VS Code these days for is Jupyter / Quarto notebooks.

It's not possible to have the same development workflow with Quarto and Org-babel since you can't run/rerun code chunks up to your current cell and automate figure management (for Org-babel).

I think these are not difficult to implement but these days I just want to use something that has these features out of the box and that notebook space is rapidly changing.

Re: Mastering Emacs

#89

Post by geokon »

pluijzer wrote: post #63
geokon wrote: post #48

Earlier quoted context omitted.

> "M-x magit" get a nice list of the status of the files in the current branch. Except it will randomly split your frame and show up in a seemingly arbitrary location - often obscuring what you're working on. I find the whole layout system in Emacs completely chaotic. I guess it comes with the flexibility (VS a fixed system like most Ides) nor do I have any particular solution in mind I'm curious if anyone has tamed…

I have my Emacs setup to never split anything and just use the whole frame (window). That also goes for things like helm. Instead of splitting I prefer to open multiple frames and let my window manager, manage them. This really improved my workflow.

How do I go about doing this ?

Seems potentially workable. Youd just jump back to the last buffer a lot of time, but that's quick and intuitivr.

Re: Mastering Emacs

#90

Post by chewxy »

geokon wrote: post #48
llm_thr wrote: post #25

Earlier quoted context omitted.

Magit is probably the easiest one for casual devs to appreciate. "M-x magit" get a nice list of the status of the files in the current branch. After you mark which ones you want to keep by moving up and down pressing s(tage) u(nstage) you just press "c c" and write your commit message. Then you press P and your git repo is up to date. At a previous job the head engineer flagged the number of commits I was making as a…

> "M-x magit" get a nice list of the status of the files in the current branch. Except it will randomly split your frame and show up in a seemingly arbitrary location - often obscuring what you're working on. I find the whole layout system in Emacs completely chaotic. I guess it comes with the flexibility (VS a fixed system like most Ides) nor do I have any particular solution in mind I'm curious if anyone has tamed…

Add something like this?

    (add-to-list 'display-buffer-alist
          '("\\*Magit*\\*"
            (display-buffer-reuse-window display-buffer-in-direction
            (direction . bottom)
            (window . root)
            (inhibit-same-window . t)))*
Post reply on HN