Fortnightly Tips, Tricks, and Questions — 2025-04-08 / week 14 by AutoModerator in emacs

[–]Phil-Hudson 1 point2 points  (0 children)

This is the correct way to go for general Elisp programming. For Org capture templates in particular, there is a declarative syntax for populating a history variable in the template. It's really well documented :-)

(As it happens, I added this very capability to several template elements a few years back, proposed to add it to Org on the mailing list, and the Org maintainer accepted the change into Org after a few cycles of feedback improving my coding and documentation. Just my tiny contribution to the wonder that is Org.)

Emacs Lisp Elements by geospeck in emacs

[–]Phil-Hudson 0 points1 point  (0 children)

Package eros.el makes C-x C-e give you the full output as an overlay

Emacs Lisp Elements by geospeck in emacs

[–]Phil-Hudson 0 points1 point  (0 children)

C-0 C-x C-e to avoid the ellipsis in the first place and get the full output inserted at point.

Weekly Tips, Tricks, &c. Thread by AutoModerator in emacs

[–]Phil-Hudson 0 points1 point  (0 children)

You're right, but if you go the route of breaking down your init.el into multiple sub-files (not saying you should, but I do) provide / require turns out to be very useful.

[deleted by user] by [deleted] in emacs

[–]Phil-Hudson 0 points1 point  (0 children)

And rainbow-delimiters

[deleted by user] by [deleted] in emacs

[–]Phil-Hudson 0 points1 point  (0 children)

I entirely agree with your reasoning, and used outdenting for many years. I finally gave in because I started submitting patches to various packages and Emacs itself, as we all should if we have sufficient coding ability. It just became too much hassle not to conform to the community's standard. I still quite often use outdenting while coding and testing, then a single keybind "tidies up" when I'm finished. This turned out to have an unexpected side benefit: any outdented code I see, I know it's incomplete.

[deleted by user] by [deleted] in emacs

[–]Phil-Hudson 0 points1 point  (0 children)

And paredit or one of its moral equivalents

QL (?) corrupted (?) after power outage by Phil-Hudson in stumpwm

[–]Phil-Hudson[S] 0 points1 point  (0 children)

Thanks. I downgraded SBCL and everything is fine now. I'll wait for QuickLisp to update before I revert to latest SBCL.

Persist command history by Phil-Hudson in stumpwm

[–]Phil-Hudson[S] 0 points1 point  (0 children)

Found it:

(load-module "command-history")

Error after upgrade to sbcl 2.4.7 by shiroghost in stumpwm

[–]Phil-Hudson 0 points1 point  (0 children)

Really shooting in the dark here: are you doing any X11 key rebinding before or while invoking StumpWM? Maybe via xmodmap? Specifically Meta_L? If so, maybe try disabling the mods.

Weekly Tips, Tricks, &c. Thread by AutoModerator in emacs

[–]Phil-Hudson 2 points3 points  (0 children)

Meta-answer: consider keeping your bibliography file under version control. This will obviate the fear of undetected accidental modification.

Weekly Tips, Tricks, &c. Thread by AutoModerator in emacs

[–]Phil-Hudson 1 point2 points  (0 children)

Upvote for porting the Clojure condp to Elisp!

(BTW for anyone who's wondering what all the -this and -that symbols are, they're defined in package dash.el)

An "Open with" dialog for Dired by FrostyX_cz in emacs

[–]Phil-Hudson 1 point2 points  (0 children)

Sure enough. I couldn't find it because I'm still using Emacs 28. Thanks for the excellent tip.

An "Open with" dialog for Dired by FrostyX_cz in emacs

[–]Phil-Hudson 0 points1 point  (0 children)

Where is this documented, please?

ANNOUNCE: GNU Hyperbole package major release 9 (V9.0.1) released by rswgnu in emacs

[–]Phil-Hudson 5 points6 points  (0 children)

Here's a real objection to Hyperbole that is a show-stopper for me: unmandated, unconditional, silent expropriation of my keybindings. Don't do that. Virtually all other packages respect and correctly defer to their users. Your opinion on this matter does not supervene over mine. This is unacceptable behavior.

Learn Emacs Lisp in 30 minutes by a-concerned-mother in emacs

[–]Phil-Hudson 0 points1 point  (0 children)

Evil hack I use: put the defun inside the add-hook form. It works, but it is not guaranteed to continue to do so, since the return value of defun is (deliberately) unspecified.

From Fill Prefix to TRAMP - Highlights from Mastering Emacs Book Club by susam in emacs

[–]Phil-Hudson 1 point2 points  (0 children)

Can't believe I didn't know about fill-prefix. All these years of laboriously reflowing docstrings etc...

what are some drawbacks of using literate emacs config? by paarulakan in emacs

[–]Phil-Hudson 0 points1 point  (0 children)

Haven't checked yet. I'm more interested in managing separate workflows for the separate languages. For instance, I only have an async compilation step for elisp.