From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: .mailrc alias won't auto-expand anymore
Date: Mon, 14 Dec 2020 15:01:28 +0000 [thread overview]
Message-ID: <874kkosa7r.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87eejssdfq.fsf@zoho.eu>
On Monday, 14 Dec 2020 at 14:51, Emanuel Berg wrote:
> No, it worked for me,
Interesting. I'm actually glad it doesn't work for me as otherwise I
would have sent the wrong email to the wrong person in some (many)
cases... having the expansion happen in front of me before composing is
quite important for me!
It'll be interesting to see what you might have configured to allow
expansion after asking to send the email. Good luck finding it!
(something about "twisty little passages" comes to mind ;-))
--
Eric S Fraga via Emacs 28.0.50 & org 9.4 on Debian bullseye/sid
next prev parent reply other threads:[~2020-12-14 15:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-13 23:37 Emanuel Berg
2020-12-14 2:43 ` Pankaj Jangid
2020-12-14 2:56 ` Emanuel Berg
2020-12-14 10:50 ` 황병희
2020-12-14 13:31 ` Emanuel Berg
2020-12-14 13:44 ` Eric S Fraga
2020-12-14 13:51 ` Emanuel Berg
2020-12-14 15:01 ` Eric S Fraga [this message]
2020-12-15 2:11 ` 황병희
2020-12-15 2:25 ` Emanuel Berg
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874kkosa7r.fsf@ucl.ac.uk \
--to=e.fraga@ucl.ac.uk \
--cc=ding@gnus.org \
/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 NNTP newsgroup(s).