Gnus development mailing list
 help / color / mirror / Atom feed
From: Xavier Maillard <zedek@gnu-rox.org>
Subject: Embedded lisp in the message body: hwoto ?
Date: Fri, 01 Oct 2004 01:42:48 +0200	[thread overview]
Message-ID: <plop87vfdvjpc7.fsf@gnu-rox.org> (raw)

Hello,

Well I had already asked for this some time ago but since I
couldn't get it working, I am trying again.

So the problem is quite simple:

1. I have USENET group susceptible to have lisp in the article
   body I would like to render using emacs-lisp/lisp mode
   automatically
2. I have friends of mine with whoom I often exchange Lisp
   snippets and so I would like to have the lisp snippet rendered
   differently from the rest of the article

So how can I do that ? Someone gave me some code which should
have done this, but it didn't work for me.

Should the lisp part of a message be "formatted" in a specific
way (section delimiter to show where the code begins and where it
ends) ? Is this really possible to have article/message buffer
rendered differently (ie. with more than the default text-mode) ?

Help grantly appreciated on this topic.

And sorry for the guy that gave me the code, if he could explain
how to use it and how to test it ... :/

Thank you very much
-- 
.o.   Xavier Maillard            Tel: +33 6 68 04 64 37
..o  
ooo   




             reply	other threads:[~2004-09-30 23:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 23:42 Xavier Maillard [this message]
2004-10-01 18:24 ` Jesper Harder
2004-10-01 20:28   ` Xavier Maillard
2004-10-01 20:49     ` Jesper Harder
2004-10-01 20:49   ` Xavier Maillard
2004-10-02 19:44     ` Jesper Harder
2004-10-03 14:24       ` Xavier Maillard
2004-10-05  1:24         ` Katsumi Yamaoka
2004-10-05  4:45           ` [SOLVED] (was: Embedded lisp in the message body: hwoto ?) Xavier Maillard
2004-10-02 15:55   ` Embedded lisp in the message body: hwoto ? Xavier Maillard
2004-10-07  8:27   ` Cristian Gutierrez
2004-10-07 15:45     ` Xavier Maillard

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=plop87vfdvjpc7.fsf@gnu-rox.org \
    --to=zedek@gnu-rox.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).