Gnus development mailing list
 help / color / mirror / Atom feed
From: Julien Danjou <julien@danjou.info>
To: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: quoting Emacs Lisp
Date: Thu, 20 Jan 2011 22:31:55 +0100	[thread overview]
Message-ID: <87k4hzb6t0.fsf@keller.adm.naquadah.org> (raw)
In-Reply-To: <87pqrrl1g7.fsf@lifelogs.com>


[-- Attachment #1.1: Type: text/plain, Size: 1002 bytes --]

On Thu, Jan 20 2011, Ted Zlatanov wrote:

> That's cool.  We should publicize it more, it's extremely useful,

Isn't it! :)

> especially if it takes off and other MUAs support it, and such bells and
> whistles are always popular with the Gnus users.  Can you explain more,
> with examples for other languages (and how to add more if they are
> missing)?

Well, the block is extracted by Gnus and displayed inline as an org-mode
buffer (see commit 2d2f709ab067c5688f325fc64c618988ed6fd178 for
implementation detail, it's really simple).

The font lock is then done by org-mode itself with the help of Babel[1].

Note that attaching file inline (or making them rendered inline with
`K i') is now also supported by Gnus if the file has a correct
content-type. I've added for example shell script colorization with
commit 6242139e39fe923bf469377ed1d64487c900d0eb. You just have to
copy/paste this for other language you usually find in attached file.

This should be fontified:


[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1.2: arf.sh --]
[-- Type: text/x-sh, Size: 24 bytes --]

# Some comment
echo foo

[-- Attachment #1.3: Type: text/plain, Size: 106 bytes --]



[1]  http://orgmode.org/worg/org-contrib/babel/

-- 
Julien Danjou
❱ http://julien.danjou.info

[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2011-01-20 21:31 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-13 10:42 Problem displaying multipart/alternative messages Michael Piotrowski
2011-01-20 14:21 ` Michael Piotrowski
2011-01-20 17:55   ` Julien Danjou
2011-01-20 20:56     ` quoting Emacs Lisp (was: Problem displaying multipart/alternative messages) Ted Zlatanov
2011-01-20 21:05       ` quoting Emacs Lisp Julien Danjou
2011-01-20 21:17         ` Ted Zlatanov
2011-01-20 21:31           ` Julien Danjou [this message]
2011-01-20 21:36             ` Julien Danjou
2011-01-24  1:00             ` Lars Ingebrigtsen
2011-01-24 10:29               ` Julien Danjou
2011-01-24 17:51                 ` Ted Zlatanov
2011-01-24 21:47                   ` Lars Ingebrigtsen
2011-01-24 22:09                     ` Ted Zlatanov
2011-01-24 22:26                       ` Daniel Pfeiffer
2011-01-25 10:18                   ` Julien Danjou
2011-01-22  4:50         ` Lars Ingebrigtsen
2011-01-24  1:06     ` Problem displaying multipart/alternative messages Lars Ingebrigtsen
2011-01-22  4:48   ` Lars Ingebrigtsen
2011-01-22  8:06     ` Julien Danjou
2011-01-22 19:50       ` Eric S Fraga

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=87k4hzb6t0.fsf@keller.adm.naquadah.org \
    --to=julien@danjou.info \
    --cc=ding@gnus.org \
    --cc=tzz@lifelogs.com \
    /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).