* Embedded lisp in the message body: hwoto ?
@ 2004-09-30 23:42 Xavier Maillard
2004-10-01 18:24 ` Jesper Harder
0 siblings, 1 reply; 12+ messages in thread
From: Xavier Maillard @ 2004-09-30 23:42 UTC (permalink / 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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Embedded lisp in the message body: hwoto ?
2004-09-30 23:42 Embedded lisp in the message body: hwoto ? Xavier Maillard
@ 2004-10-01 18:24 ` Jesper Harder
2004-10-01 20:28 ` Xavier Maillard
` (3 more replies)
0 siblings, 4 replies; 12+ messages in thread
From: Jesper Harder @ 2004-10-01 18:24 UTC (permalink / raw)
[-- Attachment #1: Type: text/plain, Size: 273 bytes --]
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:
[-- Attachment #2: Type: application/emacs-lisp, Size: 26 bytes --]
[-- Attachment #3: Type: text/plain, Size: 211 bytes --]
i.e.
<#part type="application/emacs-lisp" disposition=inline>
(defun foo (x)
(+ 2 x))
<#part type="text/plain" disposition=inline>
--
Jesper Harder <http://purl.org/harder/>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Embedded lisp in the message body: hwoto ?
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
` (2 subsequent siblings)
3 siblings, 1 reply; 12+ messages in thread
From: Xavier Maillard @ 2004-10-01 20:28 UTC (permalink / raw)
[-- 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: 275 bytes --]
Just didn't work here :(
How can I configure Gnus to force it to "render" the inline
part ?
Thank you
--
"sometimes i feel like we're making emacs better and better because we don't
know what to do with emacs once it is finished."
-- AlexSchroeder on #emacs @OPN
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Embedded lisp in the message body: hwoto ?
2004-10-01 18:24 ` Jesper Harder
2004-10-01 20:28 ` Xavier Maillard
@ 2004-10-01 20:49 ` Xavier Maillard
2004-10-02 19:44 ` Jesper Harder
2004-10-02 15:55 ` Embedded lisp in the message body: hwoto ? Xavier Maillard
2004-10-07 8:27 ` Cristian Gutierrez
3 siblings, 1 reply; 12+ messages in thread
From: Xavier Maillard @ 2004-10-01 20:49 UTC (permalink / raw)
[-- 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: 4267 bytes --]
Well I searched and found something about inlined content.
From what I see, all is correct:
,----[ C-h v mm-inlined-types RET ]
| mm-inlined-types's value is
| ("application/msword" "image/.*" "text/.*" "message/delivery-status" "message/rfc822" "message/partial" "message/external-body" "application/emacs-lisp" "application/x-emacs-lisp" "application/pgp-signature" "application/x-pkcs7-signature" "application/pkcs7-signature" "application/x-pkcs7-mime" "application/pkcs7-mime")
|
|
| List of media types that are to be displayed inline.
| See also `mm-inline-media-tests', which says how to display a media
| type inline.
|
| You can customize this variable.
|
| Defined in `mm-decode'.
|
| [back]
`----
and
,----[ C-h v mm-inline-media-tests RET ]
| mm-inline-media-tests's value is shown below.
|
| Alist of media types/tests saying whether types can be displayed inline.
|
| You can customize this variable.
|
| Defined in `mm-decode'.
|
| Value:
| (("application/msword"
| (lambda
| (handle)
| (mm-inline-render-with-stdin handle nil "antiword" "-"))
| identity)
| ("image/p?jpeg" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'jpeg handle)))
| ("image/png" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'png handle)))
| ("image/gif" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'gif handle)))
| ("image/tiff" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'tiff handle)))
| ("image/xbm" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'xbm handle)))
| ("image/x-xbitmap" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'xbm handle)))
| ("image/xpm" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'xpm handle)))
| ("image/x-xpixmap" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'xpm handle)))
| ("image/bmp" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'bmp handle)))
| ("image/x-portable-bitmap" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'pbm handle)))
| ("text/plain" mm-inline-text identity)
| ("text/enriched" mm-inline-text identity)
| ("text/richtext" mm-inline-text identity)
| ("text/x-patch" mm-display-patch-inline
| (lambda
| (handle)
| (locate-library "diff-mode")))
| ("application/emacs-lisp" mm-display-elisp-inline identity)
| ("application/x-emacs-lisp" mm-display-elisp-inline identity)
| ("text/dns" mm-display-dns-inline identity)
| ("text/html" mm-inline-text-html
| (lambda
| (handle)
| (or mm-inline-text-html-renderer mm-text-html-renderer)))
| ("text/x-vcard" mm-inline-text-vcard
| (lambda
| (handle)
| (or
| (featurep 'vcard)
| (locate-library "vcard"))))
| ("message/delivery-status" mm-inline-text identity)
| ("message/rfc822" mm-inline-message identity)
| ("message/partial" mm-inline-partial identity)
| ("message/external-body" mm-inline-external-body identity)
| ("text/.*" mm-inline-text identity)
| ("audio/wav" mm-inline-audio
| (lambda
| (handle)
| (and
| (or
| (featurep 'nas-sound)
| (featurep 'native-sound))
| (device-sound-enabled-p))))
| ("audio/au" mm-inline-audio
| (lambda
| (handle)
| (and
| (or
| (featurep 'nas-sound)
| (featurep 'native-sound))
| (device-sound-enabled-p))))
| ("application/pgp-signature" ignore identity)
| ("application/x-pkcs7-signature" ignore identity)
| ("application/pkcs7-signature" ignore identity)
| ("application/x-pkcs7-mime" ignore identity)
| ("application/pkcs7-mime" ignore identity)
| ("multipart/alternative" ignore identity)
| ("multipart/mixed" ignore identity)
| ("multipart/related" ignore identity)
| ("audio/.*" ignore ignore)
| ("image/.*" ignore ignore)
| (".*" mm-inline-text mm-readable-p))
|
| [back]
`----
All is ok, isn't it ?
P.S: sorry for this crap
--
Hacker Wonderland Xavier Maillard| "Stand Back! I'm a programmer!"
.0. zedek@gnu-rox.orgz|
..0 (+33) 326 770 221 | Webmaster, emacsfr.org
000 PGP : 0x1E028EA5 | Membre de l' APRIL
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Embedded lisp in the message body: hwoto ?
2004-10-01 20:28 ` Xavier Maillard
@ 2004-10-01 20:49 ` Jesper Harder
0 siblings, 0 replies; 12+ messages in thread
From: Jesper Harder @ 2004-10-01 20:49 UTC (permalink / raw)
Xavier Maillard <zedek@gnu-rox.org> writes:
> On 1 oct 2004, Jesper Harder wrote:
>
>> This should be easy. Just use inline attachments:
>
> Just didn't work here :(
>
> How can I configure Gnus to force it to "render" the inline part ?
It works by default. You must have included some customization which
disables it.
--
Jesper Harder <http://purl.org/harder/>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Embedded lisp in the message body: hwoto ?
2004-10-01 18:24 ` Jesper Harder
2004-10-01 20:28 ` Xavier Maillard
2004-10-01 20:49 ` Xavier Maillard
@ 2004-10-02 15:55 ` Xavier Maillard
2004-10-07 8:27 ` Cristian Gutierrez
3 siblings, 0 replies; 12+ messages in thread
From: Xavier Maillard @ 2004-10-02 15:55 UTC (permalink / raw)
[-- 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Æ\bA\x10@ \"\0\0ÇÀÈ\"\0\0É\n!?
1\0Ê\n8?1\0Ê\n8@Ë1\0Ì\n!\x13S\0Í\n!S\0Î\n!H\0Ï\n!N\0Ð !S\0Ñ\x14d\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
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Embedded lisp in the message body: hwoto ?
2004-10-01 20:49 ` Xavier Maillard
@ 2004-10-02 19:44 ` Jesper Harder
2004-10-03 14:24 ` Xavier Maillard
0 siblings, 1 reply; 12+ messages in thread
From: Jesper Harder @ 2004-10-02 19:44 UTC (permalink / raw)
Xavier Maillard <zedek@gnu-rox.org> writes:
> On 1 oct 2004, Jesper Harder wrote:
>
>> This should be easy. Just use inline attachments:
>
> All is ok, isn't it ?
Why don't you just try with a clean ~/.gnus ? If that works, then
you'll know for certain that one of your settings is wrong.
--
Jesper Harder <http://purl.org/harder/>
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Embedded lisp in the message body: hwoto ?
2004-10-02 19:44 ` Jesper Harder
@ 2004-10-03 14:24 ` Xavier Maillard
2004-10-05 1:24 ` Katsumi Yamaoka
0 siblings, 1 reply; 12+ messages in thread
From: Xavier Maillard @ 2004-10-03 14:24 UTC (permalink / raw)
Jesper Harder <harder <at> ifa.au.dk> writes:
>
> Xavier Maillard <zedek <at> gnu-rox.org> writes:
>
> > On 1 oct 2004, Jesper Harder wrote:
> >
> >> This should be easy. Just use inline attachments:
> >
> > All is ok, isn't it ?
>
> Why don't you just try with a clean ~/.gnus ? If that works, then
> you'll know for certain that one of your settings is wrong.
>
I just try removing my .gnus file and it doesn't work more :/
It seems it come from my .emacs but I can't isolate the incrimined part. Could
you, please, give me informations on what I should check ??
What can prevent from rendering such MIME object ?
I think about emacs-lisp mode customization but I really can't find it. All I
know, is, if I comment almost 99% of my .emacs file, it seems to render.
Any hint appreciated.
Xavier
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Embedded lisp in the message body: hwoto ?
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
0 siblings, 1 reply; 12+ messages in thread
From: Katsumi Yamaoka @ 2004-10-05 1:24 UTC (permalink / raw)
>>>>> In <loom.20041003T162131-939@post.gmane.org> Xavier Maillard wrote:
> I think about emacs-lisp mode customization but I really can't find
> it. All I know, is, if I comment almost 99% of my .emacs file, it
> seems to render.
Isn't it about font-lock'ing that you are talking? If so, I
guess you are using
(add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
instead of
(global-font-lock-mode 1)
In that case, font-lock is turned on by the hook and then turned
off by jit-lock-refontify by way of mm-display-inline-fontify.
It doesn't seem easy to fix the problem by Gnus and I think it
is proper to recommend Emacs users to use global-font-lock-mode
and also the font-lock-global-modes variable.
^ permalink raw reply [flat|nested] 12+ messages in thread
* [SOLVED] (was: Embedded lisp in the message body: hwoto ?)
2004-10-05 1:24 ` Katsumi Yamaoka
@ 2004-10-05 4:45 ` Xavier Maillard
0 siblings, 0 replies; 12+ messages in thread
From: Xavier Maillard @ 2004-10-05 4:45 UTC (permalink / raw)
On 5 oct 2004, Katsumi Yamaoka wrote:
> > > > > > In <loom.20041003T162131-939@post.gmane.org> Xavier Maillard wrote:
>
> > I think about emacs-lisp mode customization but I really
> > can't find it. All I know, is, if I comment almost 99% of my
> > .emacs file, it seems to render.
>
> Isn't it about font-lock'ing that you are talking? If so, I
> guess you are using
>
> (add-hook 'emacs-lisp-mode-hook 'turn-on-font-lock)
>
> instead of
>
> (global-font-lock-mode 1)
No. My .emacs take care of this. And as I posted in another
message, the problem occured when I activated a code snippet
which was using zmacs-region.
Regards.
--
Registered Linux-User #340967 with the Linux Counter, http://counter.li.org.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Embedded lisp in the message body: hwoto ?
2004-10-01 18:24 ` Jesper Harder
` (2 preceding siblings ...)
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
3 siblings, 1 reply; 12+ messages in thread
From: Cristian Gutierrez @ 2004-10-07 8:27 UTC (permalink / raw)
Este viernes, Jesper Harder dijo:
> 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.
>
> <#part type="application/emacs-lisp" disposition=inline>
> (defun foo (x)
> (+ 2 x))
> <#part type="text/plain" disposition=inline>
Amazing! Is there any chance to highlight snippets in other languages?
(Perl/Python for example). Inlining a little perl snippet (text/x-perl)
didn't work here...
--
Cristian Gutierrez http://www.dcc.uchile.cl/~crgutier
crgutier[@]dcc.uchile.cl Jabber:crgutier@jabber.org
Programmer: The device for converting coffee into software.
^ permalink raw reply [flat|nested] 12+ messages in thread
* Re: Embedded lisp in the message body: hwoto ?
2004-10-07 8:27 ` Cristian Gutierrez
@ 2004-10-07 15:45 ` Xavier Maillard
0 siblings, 0 replies; 12+ messages in thread
From: Xavier Maillard @ 2004-10-07 15:45 UTC (permalink / raw)
[-- Attachment #1: Type: text/plain, Size: 428 bytes --]
On 7 oct 2004, Cristian Gutierrez wrote:
> Este viernes, Jesper Harder dijo:
> > 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: 36 bytes --]
[-- Attachment #3: Type: text/plain, Size: 4133 bytes --]
>
> Amazing! Is there any chance to highlight snippets in other
> languages? (Perl/Python for example). Inlining a little perl
> snippet (text/x-perl) didn't work here...
Yes and the cool and neat thing, you can add your own !
For inlined content, just check:
,----[ C-h v mm-inlined-types RET ]
| mm-inlined-types's value is
| ("image/.*" "text/.*" "message/delivery-status"
|"message/rfc822" "message/partial" "message/external-body"
|"application/emacs-lisp" "application/x-emacs-lisp"
|"application/pgp-signature" "application/x-pkcs7-signature"
|"application/pkcs7-signature" "application/x-pkcs7-mime"
|"application/pkcs7-mime")
|
|
| List of media types that are to be displayed inline.
| See also `mm-inline-media-tests', which says how to display a media
| type inline.
|
| You can customize this variable.
|
| Defined in `mm-decode'.
`----
Plus:
,----[ C-h v mm-inline-media-tests RET ]
| mm-inline-media-tests's value is shown below.
|
| Alist of media types/tests saying whether types can be displayed inline.
|
| You can customize this variable.
|
| Defined in `mm-decode'.
|
| Value:
| (("image/p?jpeg" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'jpeg handle)))
| ("image/png" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'png handle)))
| ("image/gif" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'gif handle)))
| ("image/tiff" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'tiff handle)))
| ("image/xbm" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'xbm handle)))
| ("image/x-xbitmap" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'xbm handle)))
| ("image/xpm" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'xpm handle)))
| ("image/x-xpixmap" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'xpm handle)))
| ("image/bmp" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'bmp handle)))
| ("image/x-portable-bitmap" mm-inline-image
| (lambda
| (handle)
| (mm-valid-and-fit-image-p 'pbm handle)))
| ("text/plain" mm-inline-text identity)
| ("text/enriched" mm-inline-text identity)
| ("text/richtext" mm-inline-text identity)
| ("text/x-patch" mm-display-patch-inline
| (lambda
| (handle)
| (locate-library "diff-mode")))
| ("application/emacs-lisp" mm-display-elisp-inline identity)
| ("application/x-emacs-lisp" mm-display-elisp-inline identity)
| ("text/dns" mm-display-dns-inline identity)
| ("text/html" mm-inline-text-html
| (lambda
| (handle)
| (or mm-inline-text-html-renderer mm-text-html-renderer)))
| ("text/x-vcard" mm-inline-text-vcard
| (lambda
| (handle)
| (or
| (featurep 'vcard)
| (locate-library "vcard"))))
| ("message/delivery-status" mm-inline-text identity)
| ("message/rfc822" mm-inline-message identity)
| ("message/partial" mm-inline-partial identity)
| ("message/external-body" mm-inline-external-body identity)
| ("text/.*" mm-inline-text identity)
| ("audio/wav" mm-inline-audio
| (lambda
| (handle)
| (and
| (or
| (featurep 'nas-sound)
| (featurep 'native-sound))
| (device-sound-enabled-p))))
| ("audio/au" mm-inline-audio
| (lambda
| (handle)
| (and
| (or
| (featurep 'nas-sound)
| (featurep 'native-sound))
| (device-sound-enabled-p))))
| ("application/pgp-signature" ignore identity)
| ("application/x-pkcs7-signature" ignore identity)
| ("application/pkcs7-signature" ignore identity)
| ("application/x-pkcs7-mime" ignore identity)
| ("application/pkcs7-mime" ignore identity)
| ("multipart/alternative" ignore identity)
| ("multipart/mixed" ignore identity)
| ("multipart/related" ignore identity)
| ("audio/.*" ignore ignore)
| ("image/.*" ignore ignore)
| (".*" mm-inline-text mm-readable-p))
|
| [back]
`----
You can add a perl highlithing engine quite easily.
Regards.
--
Registered Linux-User #340967 with the Linux Counter, http://counter.li.org.
^ permalink raw reply [flat|nested] 12+ messages in thread
end of thread, other threads:[~2004-10-07 15:45 UTC | newest]
Thread overview: 12+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2004-09-30 23:42 Embedded lisp in the message body: hwoto ? 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 ` Embedded lisp in the message body: hwoto ? Xavier Maillard
2004-10-07 8:27 ` Cristian Gutierrez
2004-10-07 15:45 ` Xavier Maillard
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).