From: Andreas Reuleaux <rx@a-rx.info>
To: info-gnus-english@gnu.org
Subject: cut here markers for code snippets in mail
Date: Thu, 26 Aug 2021 19:23:22 +0100 [thread overview]
Message-ID: <87v93snjz9.fsf@softland> (raw)
Hi,
I have seen people highlighting code snippets in mail
with "cut here markers": some ascii art for scissors, "cut here",
"start", "end", ..., like so:
--8<---------------cut here---------------start------------->8---
rm -f /etc/fonts/conf.d/70-no-bitmaps.conf
ln -f -s /usr/share/fontconfig/conf.avail/70-yes-bitmaps.conf /etc/fonts/conf.d
--8<---------------cut here---------------end--------------->8---
which is kind of nice, and simple (as I don't want to get into
composing html mails with org-mime or the like).
I get to see them "green on yellow" in gnus (once I have received
such mails), or when in draft status (in my drafts folder).
Two questions (at least):
For one thing, I wonder if this behaviour is anywhere
documented/specified/explained in more detail?
And then: I would like to see my code green-on-yellow snippets in
message mode as well (when composing mail), or at least as a toggle:
see how my mail would look to the recipient.
And how are people actually using these "cut here markers":
insert them by hand, as I did above? Or is there some automatic support
for this hidden somewhere? - Or any other mechanisms for
such code snippets highlighting - in org mode nevertheless perhaps [?]:
I don't want to send html mails, but maybe org-mime / orgmsg / etc.
are useful for composing mails?
I only use gnus - nothing else (TM).
Thanks in advance,
-A
next reply other threads:[~2021-08-26 20:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-26 18:23 Andreas Reuleaux [this message]
2021-08-26 21:41 ` Eric Abrahamsen
2021-08-27 0:22 ` Andreas Reuleaux
2021-08-27 5:23 ` Enrico Schumann
2021-08-27 11:28 ` Andreas Reuleaux
2021-09-19 16:35 ` Wayne Harris via Announcements and discussions for GNUS, the GNU Emacs Usenet newsreader (in English)
2021-09-20 7:20 ` Alexandre Duret-Lutz
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=87v93snjz9.fsf@softland \
--to=rx@a-rx.info \
--cc=info-gnus-english@gnu.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).