From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: Re: what is the best way to include code snippets in plain mail body
Date: Sat, 11 Nov 2023 16:47:36 +0100 [thread overview]
Message-ID: <871qcwnvfr.fsf@mat.ucm.es> (raw)
In-Reply-To: <874jhsif3z.fsf@dataswamp.org>
[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]
>>> "EB" == Emanuel Berg <incal@dataswamp.org> writes:
> Uwe Brauer wrote:
>> ,----
>> | \documentclass{article}
>> | \usepackage{mathtools}
>> | \mathtoolsset{showonlyrefs}
>> | \usepackage[colorlinks]{hyperref}
>> | \usepackage{xpatch}
>> | \makeatletter
>> | \xpretocmd\HyRef@autoref{\noeqref{#2}}{}{}% small hack
>> | \makeatother
>> `----
>>
>> Is there any better way for plain based mailing lists say
> That makes kill/yank slower and don't really increase
> readability to an eye that is even remotely trained, which
> will instantly recognize it as LaTeX source, box or no box.
Ok point taken whats about the famous
--8<---------------cut here---------------start------------->8---
\documentclass{article}
\usepackage{mathtools}
\mathtoolsset{showonlyrefs}
\usepackage[colorlinks]{hyperref}
\usepackage{xpatch}
\makeatletter
\xpretocmd\HyRef@autoref{\noeqref{#2}}{}{}% small hack
\makeatother
--8<---------------cut here---------------end--------------->8---
BTW, I swore I have seen code for inserting some code or marking the
code and inserting these lines, but I can't find it anymore
Any ideas?
Regards
--
I strongly condemn Hamas heinous atrocities on Israel, especially the despicable pogroms.
I strongly condemn Putin's war of aggression against Ukraine.
I support to deliver weapons to Ukraine's military.
I support the NATO membership of Ukraine.
I support the EU membership of Ukraine.
https://addons.thunderbird.net/en-US/thunderbird/addon/gmail-conversation-view/
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
next prev parent reply other threads:[~2023-11-11 15:48 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 [this message]
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
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=871qcwnvfr.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--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).