Gnus development mailing list
 help / color / mirror / Atom feed
From: Uwe Brauer <oub@mat.ucm.es>
To: ding@gnus.org
Subject: what is the best way to include code snippets in plain mail body
Date: Sat, 11 Nov 2023 14:21:24 +0100	[thread overview]
Message-ID: <87zfzk4e97.fsf@mat.ucm.es> (raw)


Hi

Sometimes I have to include an example which is some code.
If it is on a emacs mailing list I would do 
#+begin_src 
\documentclass{article}
\usepackage{mathtools}
\mathtoolsset{showonlyrefs}
\usepackage[colorlinks]{hyperref}
\usepackage{xpatch}
\makeatletter
\xpretocmd\HyRef@autoref{\noeqref{#2}}{}{}% small hack
\makeatother
#+end_src


And this  is fine.

If I write to an author that used some html based mail, (using a gmail
account or thunderbird) I would use org-mime to htmlize the above code,
but in general I would use

,----
| \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



Regards

Uwe Brauer 



-- 
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/



             reply	other threads:[~2023-11-11 13:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-11 13:21 Uwe Brauer [this message]
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
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=87zfzk4e97.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).