From: James Thomas via Emacs news and miscellaneous discussions outside the scope of other Emacs mailing lists <emacs-tangents@gnu.org>
To: emacs-tangents@gnu.org
Subject: Re: 2024-11-11 Emacs news
Date: Wed, 13 Nov 2024 11:46:31 +0530 [thread overview]
Message-ID: <86cyizu08w.fsf@gmx.net> (raw)
In-Reply-To: <87ikst7q7q.fsf@sachachua.com> (Sacha Chua's message of "Mon, 11 Nov 2024 10:19:37 -0500")
Sacha Chua wrote:
> * Tip: you can use magit-find-file to find any version of a file
> quickly
In VC, for e.g. 'C-x v ~ master@{4_months_ago} RET': any spec in (man
"gitrevisions(7)") should work.
> * Aimé Bertrand: Mu4e - save attachments faster - an update
>> my solution for saving multiple attachements at once without a
>> completion
FYI: In Gnus, 'X m'.
> * Thanos Apollo: RSS Mastery with RSS-Bridge & Elfeed [Video]
>> RSS-Bridge
Looks heavy: (info "(gnus) Web Searches") is better IMO, using a custom
'nnweb-type-definition'. (caveat: all these could lull us into a false
sense of convenience with a non-free service, until they up their game,
by when it's too late)
> * What are your bad habits?
>> Using C-x b RET instead of C-x LEFT to go to the previous buffer
>>> this is a very good habit, the position of arrow keys is terrible on
>>> most keyboards
So I have C-<return> and C-M-<return> (previously C-z and C-x C-z) bound
to bury- and unbury-buffer respectively (C-j is used for RET anyway):
they double as the above. Also useful in between minibuffer editing.
>> Forget to save window configurations in registers
'winner-undo'.
>> (python related, especially painful with git worktrees) Why did I not
>> make sure I was using the right venv with pyvenv?
Use buffer-env. Also, a modeline indicator or custom eshell prompt?
--
---
via emacs-tangents mailing list (https://lists.gnu.org/mailman/listinfo/emacs-tangents)
parent reply other threads:[~2024-11-13 6:16 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <87ikst7q7q.fsf@sachachua.com>]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86cyizu08w.fsf@gmx.net \
--to=emacs-tangents@gnu.org \
--cc=jimjoe@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).