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

Two Years of Emacs Solo

rahuljuliato.com

Post reply on HN
Print view View original

81–90 of 147 posts

Re: Two Years of Emacs Solo

#81

Post by qazxcvbnm »

jharsman wrote: post #70
qazxcvbnm wrote: post #38

The new Emacs features sound great! (We have native window management finally) I wish we would someday be able to edit in xref too, wgrep having landed in Emacs 30 (especially since project.el grep goes to xref by default). By the way, anyone more informed know about any work on getting a graphical browser to work on latest Emacs, now that webkit xwidgets is dead for Emacs 30+? (Have tried EAF; extremely buggy on Mac…

Emacs solo actually contains functionality for just that, the below snippet which allows exporting xref buffers to grep format by pressing 'E'. You can then use wgrep etc. ;; Makes any xref buffer "exportable" to a grep buffer with "E" so you can edit it with "e". (defun emacs-solo/xref-to-grep-compilation () "Export the current Xref results to a grep-like buffer (Emacs 30+)." (interactive) (unless (derived-mode-p 'x…

My goodness, how so thoughtful Emacs Solo is!

Re: Two Years of Emacs Solo

#82

Post by mark_l_watson »

mhd wrote: post #58
NetOpWibby wrote: post #27

I’m always impressed by people who are hardcore EMacs or Vim devs, their setups are impressive af. I’m a GUI guy though. As soon as I try delving in, I abort when I see things like “just type c-C dingle bob to do x thing.” I’m happy these people found something that works with their brains. I just want a GUI that works like what they use. I recently saw a Zed fork stripped of AI stuff but there’s no binaries yet (you…

I'd say most people run Emacs in the GUI mode, not in a terminal. So these days, you're pretty much on the same level as most rivals. Sadly, "these days" is a low bar. The days of consistent platform-specific "Human Interface Guidelines" are over, it's all just a browser wrapped in a top-level window or something that simulates that, with most interaction patterns being a cargo cult of how it's remembered from the 90…

I mostly run Emacs in a terminal, except I configure for two finger scroll on Mac trackpad and tap to move cursor. I also reduced the size of my .emacs by 60% in the last year.

Re: Two Years of Emacs Solo

#83

Post by maleldil »

noosphr wrote: post #61
k_bx wrote: post #53

Earlier quoted context omitted.

It's a very different experience: - I already have tmux launched, if ssh drops – I can continue - I don't have to match windows to ssh sessions -- just have them in my tmux

Yes, tmux vastly inferior to tramp. Tramp runs in your local Emacs and edits files remotely. It can also launch processes remotely and keep track of them.

How does it handle things like LSPs?

Re: Two Years of Emacs Solo

#84

Post by gpderetta »

yunnpp wrote: post #3

Is Eglot on par with emacs-lsp for C++? Specifically thinking about pointing it to a compile_commands.json and all of the usual C++ nonsense required for code navigation and autocomplete.

Pretty much yes. I switched to eglot from emacs-lsp because of some frequent random errors ("document not added") that required me to frequently kill clangd; might be a PEBCAK problem, but went away with eglot.

Everything mostly worked out of the box.

Re: Two Years of Emacs Solo

#86

Post by mksybr »

k_bx wrote: post #79
AJRF wrote: post #68

Earlier quoted context omitted.

Surprised to hear people told you not to change that - one of the earliest bits of advice I got on using emacs is to set the location of those files to a hidden directory in your home folder.

I was proposing to make default where those files are not created, since Emacs is actually surprisingly great out of the box with no configuration, except for this "little" thing. Apparrently, some people believe it's perfect as it is

It should default to a single location maybe a XDG directory instead of polluting every directory

Re: Two Years of Emacs Solo

#88

Post by pqs »

widdershins wrote: post #66
jimbokun wrote: post #24

This article shows how Emacs remains a beautiful, relevant project several decades after it was first created. The core design and implementation’s ability to evolve into something still useful today and competitive with modern tools is an amazing achievement. Also, with LLMs driving so much of current development it potentially makes Emacs even more competitive relative to modern IDEs. Development can be driven prim…

> I imagine an LLM would be very good at writing Elisp to leverage EMacs’ strong core functionality Yes, they are pretty good. I have set up GPTel (an excellent Emacs package for interacting with LLMs) with some tools allowing it to run Elisp, inspect files (Elisp functions know what file they were defined in, so it's easy to find stuff) and read Emacs documentation. LLMs use this to good effect, and iterate on my co…

Indeed. I always used Emacs, but not, thanks to AI agents, Emacs is better than ever, as it can write the lisp I can't write, and it can read the docs I don't have the time to read.

Re: Two Years of Emacs Solo

#89

Post by kidsil »

Funny, this mirrors almost exactly a decision I made after about a year of struggling with ELPA packages breaking on me repeatedly.

I ended up cutting Emacs off from ELPA entirely, settled on a ~700-line init.el, and now use Emacs as a glorified Org-mode agenda keeper. It's been heavenly (especially with a dedicated monitor).

The one thing I'm still working out is syncing with calendars and email.

Re: Two Years of Emacs Solo

#90

Post by muyuu »

k_bx wrote: post #31

> — Sensible file handling: backups and auto-saves in a cache/ directory, recentf for recent files, clean buffer naming with uniquify It's crazy to me how out of the box when you edit nginx file at /etc/nginx/sites-enabled/foo it creates another file foo~ there and nginx tries to load that too When I tried to ask emacs reddit community they started attacking me for changing the default that only I need and fits every…

there's pros and cons

using the same directory drastically reduces the amount of assumptions about your system's permissions and your own installation (or lack thereof)

old school *nix editors typically do something like emacs and vi typically do, whereas old WinDOS/Mac single-user systems would have an installation file and a cache system-wide, and post NT and OS-X they have roughly the same but in a centralised user directory that is not system-wide, but is located as if it were (different evolution path)

Post reply on HN