From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: Automatically displaying content of [some] attachments
Date: Tue, 25 Aug 2020 10:30:53 +0100 [thread overview]
Message-ID: <87y2m3t6lu.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87k0xzhccw.fsf@tullinup.koldfront.dk>
On Saturday, 15 Aug 2020 at 22:40, Adam Sjøgren wrote:
> Then I send the question, and it triggers an "aww, let me just take a
> quick look, how hard can it be, it's Emacs, for crying out loud"-reaction.
This is a summary of my experience practically every time I've posted a
question on either gnus or emacs groups... You would think I would have
learned by now but it still happens to me all the time.
On the other hand, I can rationalise that having posted the question and
the answer will help others in the future. ;-)
--
Eric S Fraga via Emacs 28.0.50 & org 9.3.7 on Debian bullseye/sid
prev parent reply other threads:[~2020-08-25 9:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 10:12 Adam Sjøgren
2020-08-15 10:45 ` Adam Sjøgren
2020-08-15 10:51 ` Adam Sjøgren
2020-08-15 18:41 ` Wayne Harris
2020-08-15 20:40 ` Adam Sjøgren
2020-08-19 1:50 ` Wayne Harris
2020-08-19 20:02 ` Adam Sjøgren
2020-08-20 2:21 ` Rafi Khan
2020-08-25 9:30 ` Eric S Fraga [this message]
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=87y2m3t6lu.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).