From: Emanuel Berg <incal@dataswamp.org>
To: ding@gnus.org
Subject: Re: what is the best way to include code snippets in plain mail body
Date: Sat, 11 Nov 2023 20:32:06 +0100 [thread overview]
Message-ID: <8734xcgk7d.fsf@dataswamp.org> (raw)
In-Reply-To: <87y1f4jdr7.fsf@mat.ucm.es>
Uwe Brauer wrote:
> Ah, message-mark-inserted-region and friends I the answer,
> sorry for the noise then.
Let me try that on what you just wrote,
--8<---------------cut here---------------start------------->8---
Ah, message-mark-inserted-region and friends I the answer,
sorry for the noise then.
--8<---------------cut here---------------end--------------->8---
Oh, those I do recognize!
Okay, so what are they supposed to do?
Actually I have a function that removes them [1] but if they
are beneficial, maybe I'll allow them then.
[1] https://dataswamp.org/~incal/emacs-init/gnus/article.el
--
underground experts united
https://dataswamp.org/~incal
next prev parent reply other threads:[~2023-11-11 19:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-11 13:21 Uwe Brauer
2023-11-11 13:39 ` Emanuel Berg
2023-11-11 15:47 ` Uwe Brauer
2023-11-11 18:41 ` Arash Esbati
2023-11-11 19:44 ` Emanuel Berg
2023-11-11 19:23 ` Uwe Brauer
2023-11-11 19:32 ` Emanuel Berg [this message]
2023-11-11 22:22 ` 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=8734xcgk7d.fsf@dataswamp.org \
--to=incal@dataswamp.org \
--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).