From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: quoting Emacs Lisp
Date: Thu, 20 Jan 2011 15:17:28 -0600 [thread overview]
Message-ID: <87pqrrl1g7.fsf@lifelogs.com> (raw)
In-Reply-To: <87d3nrcmks.fsf@keller.adm.naquadah.org>
On Thu, 20 Jan 2011 22:05:55 +0100 Julien Danjou <julien@danjou.info> wrote:
JD> On Thu, Jan 20 2011, Ted Zlatanov wrote:
>> On Thu, 20 Jan 2011 18:55:36 +0100 Julien Danjou <julien@danjou.info> wrote:
>>
JD> #+begin_src emacs-lisp
JD> (unless (with-current-buffer (mm-handle-buffer handle)
JD> …))
JD> #+end_src
>>
>> Where are these markers from? Are they standard in any way?
JD> *cough* *cough*
JD> I was just trying my recent pushed patches.[1]
JD> [1] http://julien.danjou.info/blog/2011.html#Code_fontification_with_Gnus_and_Org-mode
That's cool. We should publicize it more, it's extremely useful,
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)?
Thanks
Ted
next prev parent reply other threads:[~2011-01-20 21:17 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 [this message]
2011-01-20 21:31 ` Julien Danjou
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=87pqrrl1g7.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).