Gnus development mailing list
 help / color / mirror / Atom feed
From: Xavier Maillard <zedek@gnu-rox.org>
Subject: Re: Embedded lisp in the message body: hwoto ?
Date: Sat, 02 Oct 2004 17:55:59 +0200	[thread overview]
Message-ID: <plop87r7ohi06o.fsf@gnu-rox.org> (raw)
In-Reply-To: <m3acv6fg9s.fsf@defun.localdomain>

[-- Attachment #1: Type: text/plain, Size: 361 bytes --]

On  1 oct 2004, Jesper Harder wrote:

> Xavier Maillard <zedek@gnu-rox.org> writes:
> 
> > 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
> 
> This should be easy.  Just use inline attachments:
> 
> (defun foo (x)
> (+ 2 x))
> i.e.
> 
> 

[-- Attachment #2: Type: application/emacs-lisp, Size: 30 bytes --]

[-- Attachment #3: Type: text/plain, Size: 3343 bytes --]


Well I try to see if, at least, Gnus was "aware" of the inlined
lisp part.

It seems it is (M-x debug-on-entry RET mm-display-elisp-inline
RET):

,----
| 
| Debugger entered--returning value: (lambda nil (let (buffer-read-only) (delete-region #<marker at 2464 in *Article*> #<marker at 2490 in *Article*>)))
|   mm-display-elisp-inline((#<buffer  *mm*<3>> ("application/emacs-lisp") nil (lambda nil (let ... ...)) ("inline") nil nil nil))
|   mm-display-inline((#<buffer  *mm*<3>> ("application/emacs-lisp") nil (lambda nil (let ... ...)) ("inline") nil nil nil))
|   mm-display-part((#<buffer  *mm*<3>> ("application/emacs-lisp") nil (lambda nil (let ... ...)) ("inline") nil nil nil) t)
|   byte-code("\bƒ\x17\0Æ\b‰A\x10@	\"ƒ\0\0ÇÀÈ\"ˆ‚\0\0É\n!?…1\0Ê\n8?†1\0Ê\n8@Ëš†1\0Ì\n!‰\x13ƒS\0Í\n!ƒS\0Î\n!ƒH\0Ï\n!„N\0Ð	!ƒS\0Ñ\x14‚d\0\n\x1aÒÓ\n!Ô\"@)Õšƒd\0Ñ\x15\x0e\"GTÈ\x1e#‰\x1e$\nB\x0e\"B\x16\"\fƒ\x7f\0Ö	!„•\0×\n\x0e$\f†Œ\0\v…Œ\0\rC#ˆØ ˆÑ\x16%`\x16#\fƒÂ\0\x0e%ƒ§\0Ùyˆ`\x16#\x0e&ŠÈÚۏˆ\x0e')\x1e(\x1e)Ü\nÑ\"ˆ*dbˆ‚â\0\rƒâ\0\vƒâ\0\x0e%ƒÕ\0Ùyˆ`\x16#Ø ˆÝ\nÞ\n!\"ˆdbˆŠŒ\x0e#`}ˆßÈ\x0e$à\x0e*@!ƒù\0á‚ý\0\x0e*GS\n‰\x1a@;ƒ\n\x01\n@‚\x0e\x01á\n8@)$,‡" [ignored type handle not-attachment display text string-match throw nil mm-inline-override-p 4 "inline" mm-attachment-override-p mm-automatic-display-p mm-inlinable-p mm-inlined-p mm-automatic-external-display-p t split-string mm-handle-media-type "/" "text" gnus-unbuttonized-mime-type-p gnus-insert-mime-button gnus-article-insert-newline -1 (set-buffer gnus-summary-buffer) ((error)) mm-display-part mm-insert-inline mm-get-part gnus-treat-article bufferp 1 gnus-article-mime-handle-alist beg id move gnus-newsgroup-charset gnus-newsgroup-ignored-charsets mail-parse-ignored-charsets mail-parse-charset gnus-article-mime-handles] 7)
|   gnus-mime-display-single((#<buffer  *mm*<3>> ("application/emacs-lisp") nil (lambda nil (let ... ...)) ("inline") nil nil nil))
|   gnus-mime-display-part((#<buffer  *mm*<3>> ("application/emacs-lisp") nil (lambda nil (let ... ...)) ("inline") nil nil nil))
|   mapcar(gnus-mime-display-part ((#<buffer  *mm*<2>> ("text/plain") nil (lambda nil ...) nil nil nil nil) (#<buffer  *mm*<3>> ("application/emacs-lisp") nil (lambda nil ...) ("inline") nil nil nil) (#<buffer  *mm*<4>> ("text/plain") nil nil ("inline") nil nil nil)))
|   gnus-mime-display-mixed(((#<buffer  *mm*<2>> ("text/plain") nil (lambda nil ...) nil nil nil nil) (#<buffer  *mm*<3>> ("application/emacs-lisp") nil (lambda nil ...) ("inline") nil nil nil) (#<buffer  *mm*<4>> ("text/plain") nil nil ("inline") nil nil nil)))
|   gnus-mime-display-part((#("multipart/mixed" 0 15 (start nil from "harder@ifa.au.dk" buffer #<buffer  *mm*> boundary "=-=-=")) (#<buffer  *mm*<2>> ("text/plain") nil (lambda nil ...) nil nil nil nil) (#<buffer  *mm*<3>> ("application/emacs-lisp") nil (lambda nil ...) ("inline") nil nil nil) (#<buffer  *mm*<4>> ("text/plain") nil nil ("inline") nil nil nil)))
|   gnus-display-mime()
|   gnus-article-prepare-display()
|   gnus-article-prepare(15605 nil)
|   gnus-summary-display-article(15605 nil)
|   gnus-summary-select-article(nil nil pseudo)
|   gnus-summary-scroll-up(1)
|   call-interactively(gnus-summary-scroll-up)
`----

Do you think this is normal ? (what about the famous marker in
the *Article* buffer ?)

Regards
-- 
Hito no kokoro wa kawareru mono


  parent reply	other threads:[~2004-10-02 15:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-30 23:42 Xavier Maillard
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   ` Xavier Maillard [this message]
2004-10-07  8:27   ` Embedded lisp in the message body: hwoto ? 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=plop87r7ohi06o.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).