| Age | Commit message (Collapse) | Author |
|
|
|
Emacs seems to take margins into account when deciding whether a
window can be split horizontally. So with my current personal config,
a full-width Gnus article window would have huge margins, and could
not be split horizontally because a half-width window would not have
enough room for these margins.
|
|
Move other MLs further down to keep things alphabetized 🤓
|
|
So as not to catch e.g. <https://static.lwn.net/kerneldoc/>.
|
|
Lots of commands in Gnus buffers try to reinstate the setup defined in
gnus-buffer-configuration, so when eg drafting a message with the
original article displayed on the side, and using P or N to move
around the thread, there ends up being some friction in window
management.
So stop using the Group buffer as a way to left-pad articles; it
doesn't even look good on half-width frames anyway.
|
|
Make it more outline-friendly.
|
|
Couple of mistakes there:
* buffer-local-value was called too late,
* the symbol wasn't quoted, so buffer-local-value ended up taking a
peek at fill-column directly, because that's what my/centered-width
defaults to.
Just wrap the whole thing in with-current-buffer. That'll make it
easier to introduce new buffer-local variables set via mode hooks.
|
|
|
|
|
|
See <https://lwn.net/Articles/902796/bigpage#Briefs>.
|
|
|
|
|
|
Moving around in Rust code is a pretty nerve-racking experience
otherwise.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
https://lwn.net/Articles/884301/
|
|
|
|
I could update the Custom value to add NonGNU ELPA, but at this point
I'd rather forsake Custom for lists altogether.
|
|
|
|
Using an array makes it easier to add/comment out stuff.
NB: Cannot compile --with-xwidgets on Tumbleweed right now, because
the version requirement is too strict IIUC. I remember messing around
with *FLAGS and compiling/running successfully, but that knowledge
vanished along with some Git stash.
|
|
The body diet continueþ.
|
|
TTYs seem to have a glyph for that one.
|
|
Darker backgrounds; also try to catch all those weird instances where
the background is reset to white.
|
|
|
|
Removing the padding made the main column hide beneath the left menu
when reducing the window width.
|
|
|
|
- give my eyes and neck a rest from tilting left to right on a wide
screen,
- remove cruft.
|
|
LWN lets users do that, but (1) it's only colors (2) it does not
cover *every* color, so trying to create a "dark theme" yields
e.g. unreadable buttons.
|
|
|
|
> That feels like too much power.
> I like it.
— Daniel Floyd
November 2, 2021
|
|
- clarify package initialization comments
- load Modus theme on terminal too
- use emoji variation selector when appropriate
- open patches in read-only mode
- now that Modus has been updated, ditch obsolete option
- etc.
|
|
|
|
I keep pressing "f" for "file-related commands", instead of "c" for
"current file-related commands". Cave in and move "f" to "C-f".
|
|
|
|
The pgtk build will not honor X resources anymore; move with the
times.
On my Debian XFCE laptop with a 1366x768 screen, this setting seems to
yield acceptable results:
$ gsettings set org.gnome.desktop.interface monospace-font-name \
'DejaVu Sans Mono 11'
|
|
|
|
- add [SPAM UNSURE]
- make tailing " :" optional
|
|
modus-themes-slanted-constructs still needs to be updated to
modus-themes-italic-constructs, but the built-in version of the theme
has a quirk that makes customization a bit wonky.
|