From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: quoting code blocks in Gnus without Org functions
Date: Fri, 08 Apr 2011 00:52:42 -0500 [thread overview]
Message-ID: <877hb570id.fsf@lifelogs.com> (raw)
In-Reply-To: <87ipuppxlz.fsf@lifelogs.com>
On Thu, 07 Apr 2011 16:20:24 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote:
TZ> On Thu, 07 Apr 2011 14:57:41 -0500 Ted Zlatanov <tzz@lifelogs.com> wrote:
TZ> On Thu, 07 Apr 2011 09:38:48 +0200 Julien Danjou <julien@danjou.info> wrote:
JD> You do not need a cond. Simply put the current major mode symbol's name
JD> without the -mode, e.g. lisp-interaction-mode -> lisp-interaction.
TZ> #+begin_src emacs-lisp
TZ> This doesn't syntax-highlight like "lisp" does. So "lisp" is still
TZ> better currently.
Huh, "lisp" is also not highlighted correctly in Gnus. I distinctly
recall the Emacs Lisp highlighting was applied to some examples you
posted, Julien. Is my example wrong or have I misconfigured something?
Thanks
Ted
next prev parent reply other threads:[~2011-04-08 5:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 4:02 draft group weirdness Eric Abrahamsen
2011-04-05 10:48 ` Richard Riley
2011-04-06 0:24 ` Lars Magne Ingebrigtsen
2011-04-06 1:43 ` Eric Abrahamsen
2011-04-06 13:28 ` quoting code blocks in Gnus without Org functions (was: draft group weirdness) Ted Zlatanov
2011-04-06 14:14 ` quoting code blocks in Gnus without Org functions Julien Danjou
2011-04-06 14:21 ` Ted Zlatanov
2011-04-06 14:45 ` Julien Danjou
2011-04-06 16:24 ` Ted Zlatanov
2011-04-07 7:38 ` Julien Danjou
2011-04-07 19:57 ` Ted Zlatanov
2011-04-07 21:20 ` Ted Zlatanov
2011-04-08 5:52 ` Ted Zlatanov [this message]
2011-04-08 9:34 ` Balázs Tóth
2011-04-08 9:40 ` Julien Danjou
2011-04-11 18:47 ` Ted Zlatanov
2011-04-10 15:50 ` draft group weirdness Eric Abrahamsen
2011-04-11 18:39 ` Ted Zlatanov
2011-04-10 15:54 ` Eric Abrahamsen
2011-04-12 16:21 ` Lars Magne Ingebrigtsen
2011-04-12 23:02 ` Eric Abrahamsen
2011-04-12 16:19 ` Lars Magne Ingebrigtsen
2011-05-18 11:39 ` Eric Abrahamsen
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=877hb570id.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).