From: asjo@koldfront.dk (Adam Sjøgren)
To: info-gnus-english@gnu.org
Subject: Re: Colouring diff-part of an email
Date: Wed, 06 Mar 2013 15:53:33 +0100 [thread overview]
Message-ID: <871ubs4m1d.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87wqtk1wa8.fsf@thinkpad.tsdh.de>
On Wed, 06 Mar 2013 14:40:31 +0100, Tassilo wrote:
> #+BEGIN_SRC diff
> +Some text added
> -Some text deleted
> +Some more text added
> #+END_SRC
> Not sure if that does obey `org-src-fontify-natively' (which should be
> set to t), though. Well see when we receive this very mail.
After setting it to t, and editing one of the commit emails, it looks
perfect.
Great tip, thanks!
... maybe I can even make a washing function that adds those #+-thingies
automatically for me, so my colleagues don't have to see them in the
emails :-)
Best regards,
Adam
--
"Set out on a laughless day Adam Sjøgren
Like a troupe of clowns" asjo@koldfront.dk
next prev parent reply other threads:[~2013-03-06 14:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-06 9:58 Adam Sjøgren
2013-03-06 13:40 ` Tassilo Horn
2013-03-06 14:53 ` Adam Sjøgren [this message]
2013-03-06 17:41 ` Sivaram Neelakantan
[not found] <mailman.21536.1362563949.855.info-gnus-english@gnu.org>
2013-03-06 17:58 ` Frank Terbeck
2013-03-13 20:08 ` Adam Sjøgren
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=871ubs4m1d.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--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).