multipart/related test

multipart/related test

[Lars Magne Ingebrigtsen]

[-- Attachment #1.1: Type: text/plain, Size: 63 bytes --]

This is the text/plain part, which doesn't look very exciting.

[-- Attachment #1.2: Type: text/html, Size: 830 bytes --]

[-- Attachment #2: Type: image/gif, Size: 775 bytes --]

[-- Attachment #3: Type: image/gif, Size: 5665 bytes --]

Re: multipart/related test

[Kai.Grossjohann]

Just installed pgnus-0.56 and w3-4.0pre.30 on Emacs 20.3, and this is
what happened:

,-----
| Signaling: (wrong-number-of-arguments #<subr buffer-string> 3)
|   (buffer-string nil nil (mm-handle-buffer part))
|   (setq data (buffer-string nil nil (mm-handle-buffer part)) content-type (mm-handle-type part) encoding (symbol-name (mm-handle-encoding part)))
|   (if (not part) (message "Unknown CID encounterred: %s" url) (setq data (buffer-string nil nil ...) content-type (mm-handle-type part) encoding (symbol-name ...)) (if (= 0 ...) (setq content-type "text/plain")) (if (= 0 ...) (setq encoding "8bit")) (if (listp content-type) (setq content-type ...)) (setq url-current-content-length (length data) url-current-mime-type content-type url-current-mime-encoding encoding url-current-mime-headers (list ... ...)) (and data (insert data)))
|   (let ((content-type nil) (encoding nil) (part nil) (data nil)) (setq part (mm-get-content-id url)) (if (not part) (message "Unknown CID encounterred: %s" url) (setq data ... content-type ... encoding ...) (if ... ...) (if ... ...) (if ... ...) (setq url-current-content-length ... url-current-mime-type content-type url-current-mime-encoding encoding url-current-mime-headers ...) (and data ...)))
|   url-cid-gnus("003e01be1642$a526f940$b86efea9@win")
|   (cond ((fboundp ...) (url-cid-gnus url)) (t (message "Unable to handle CID URL: %s" url)))
|   (if (not (string-match "^cid:\\(.*\\)" url)) (message "Malformed CID URL: %s" url) (setq url (url-unhex-string ...)) (cond (... ...) (t ...)))
|   url-cid("cid:003e01be1642$a526f940$b86efea9@win")
|   url-retrieve-internally("cid:003e01be1642$a526f940$b86efea9@win" nil)
|   url-retrieve("cid:003e01be1642$a526f940$b86efea9@win")
|   w3-fetch("cid:003e01be1642$a526f940$b86efea9@win")
|   widget-image-notify((image :args nil alt "[cid:003e01be1642$a526f940$b86efea9@win]" ismap nil usemap nil :href nil :target nil :button-face (w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00001 w3-style-face-00000 w3-style-face-00000) :src "cid:003e01be1642$a526f940$b86efea9@win" where #<marker at 2295 in *Article*> :children ((item :args nil :value usemap :format "%[%t%]" :tag "[cid:003e01be1642$a526f940$b86efea9@win]" :button-face ... :tab-order -1 :delete widget-default-delete :action widget-default-action :notify widget-image-callback :parent #0 :help-echo widget-image-summarize :button-overlay #<overlay from 2295 to 2335 in *Article*> :from #<marker (before-insertion) at 2295 in *Article*> :to #<marker at 2335 in *Article*>)) buffer #<buffer *Article*>) (item :args nil :value usemap :format "%[%t%]" :tag "[cid:003e01be1642$a526f940$b86efea9@win]" :button-face (w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w
 3!
!
-style-face-00002 w3-style-face-00001 w3-style-face-00000 w3-style-face-00000) :tab-order -1 :delete widget-default-delete :action widget-default-action :notify widget-image-callback :parent (image :args nil alt "[cid:003e01be1642$a526f940$b86efea9@win]" ismap nil usemap nil :href nil :target nil :button-face (w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00001 w3-style-face-00000 w3-style-face-00000) :src "cid:003e01be1642$a526f940$b86efea9@win" where #<marker at 2295 in *Article*> :children (#0) buffer #<buffer *Article*>) :help-echo widget-image-summarize :button-overlay #<overlay from 2295 to 2335 in *Article*> :from #<marker (before-insertion) at 2295 in *Article*> :to #<marker at 2335 in *Article*>) nil)
|   widget-apply((image :args nil alt "[cid:003e01be1642$a526f940$b86efea9@win]" ismap nil usemap nil :href nil :target nil :button-face (w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00001 w3-style-face-00000 w3-style-face-00000) :src "cid:003e01be1642$a526f940$b86efea9@win" where #<marker at 2295 in *Article*> :children ((item :args nil :value usemap :format "%[%t%]" :tag "[cid:003e01be1642$a526f940$b86efea9@win]" :button-face ... :tab-order -1 :delete widget-default-delete :action widget-default-action :notify widget-image-callback :parent #0 :help-echo widget-image-summarize :button-overlay #<overlay from 2295 to 2335 in *Article*> :from #<marker (before-insertion) at 2295 in *Article*> :to #<marker at 2335 in *Article*>)) buffer #<buffer *Article*>) :notify (item :args nil :value usemap :format "%[%t%]" :tag "[cid:003e01be1642$a526f940$b86efea9@win]" :button-face (w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 
 w!
!
3-style-face-00002 w3-style-face-00001 w3-style-face-00000 w3-style-face-00000) :tab-order -1 :delete widget-default-delete :action widget-default-action :notify widget-image-callback :parent (image :args nil alt "[cid:003e01be1642$a526f940$b86efea9@win]" ismap nil usemap nil :href nil :target nil :button-face (w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00001 w3-style-face-00000 w3-style-face-00000) :src "cid:003e01be1642$a526f940$b86efea9@win" where #<marker at 2295 in *Article*> :children (#0) buffer #<buffer *Article*>) :help-echo widget-image-summarize :button-overlay #<overlay from 2295 to 2335 in *Article*> :from #<marker (before-insertion) at 2295 in *Article*> :to #<marker at 2335 in *Article*>) nil)
|   widget-default-action((item :args nil :value usemap :format "%[%t%]" :tag "[cid:003e01be1642$a526f940$b86efea9@win]" :button-face (w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00001 w3-style-face-00000 w3-style-face-00000) :tab-order -1 :delete widget-default-delete :action widget-default-action :notify widget-image-callback :parent (image :args nil alt "[cid:003e01be1642$a526f940$b86efea9@win]" ismap nil usemap nil :href nil :target nil :button-face (w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00001 w3-style-face-00000 w3-style-face-00000) :src "cid:003e01be1642$a526f940$b86efea9@win" where #<marker at 2295 in *Article*> :children (#0) buffer #<buffer *Article*>) :help-echo widget-image-summarize :button-overlay #<overlay from 2295 to 2335 in *Article*> :from #<marker (before-insertion) at 2295 in *Article*> :to #<marker at 2335 in *Article*>) nil)
|   widget-apply((item :args nil :value usemap :format "%[%t%]" :tag "[cid:003e01be1642$a526f940$b86efea9@win]" :button-face (w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00001 w3-style-face-00000 w3-style-face-00000) :tab-order -1 :delete widget-default-delete :action widget-default-action :notify widget-image-callback :parent (image :args nil alt "[cid:003e01be1642$a526f940$b86efea9@win]" ismap nil usemap nil :href nil :target nil :button-face (w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00001 w3-style-face-00000 w3-style-face-00000) :src "cid:003e01be1642$a526f940$b86efea9@win" where #<marker at 2295 in *Article*> :children (#0) buffer #<buffer *Article*>) :help-echo widget-image-summarize :button-overlay #<overlay from 2295 to 2335 in *Article*> :from #<marker (before-insertion) at 2295 in *Article*> :to #<marker at 2335 in *Article*>) :action nil)
|   widget-apply-action((item :args nil :value usemap :format "%[%t%]" :tag "[cid:003e01be1642$a526f940$b86efea9@win]" :button-face (w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00001 w3-style-face-00000 w3-style-face-00000) :tab-order -1 :delete widget-default-delete :action widget-default-action :notify widget-image-callback :parent (image :args nil alt "[cid:003e01be1642$a526f940$b86efea9@win]" ismap nil usemap nil :href nil :target nil :button-face (w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00002 w3-style-face-00001 w3-style-face-00000 w3-style-face-00000) :src "cid:003e01be1642$a526f940$b86efea9@win" where #<marker at 2295 in *Article*> :children (#0) buffer #<buffer *Article*>) :help-echo widget-image-summarize :button-overlay #<overlay from 2295 to 2335 in *Article*> :from #<marker (before-insertion) at 2295 in *Article*> :to #<marker at 2335 in *Article*>) nil)
|   widget-button-press(2300)
|   call-interactively(widget-button-press)
`-----

kai
-- 
Life is hard and then you die.

Re: multipart/related test

[Kai.Grossjohann]

Kai.Grossjohann@CS.Uni-Dortmund.DE writes:

  > Just installed pgnus-0.56 and w3-4.0pre.30 on Emacs 20.3, and this
  > is what happened: [...]

Err.  When I invoked the cid button thingy, that is.

kai
-- 
Life is hard and then you die.

Re: multipart/related test

[Lars Magne Ingebrigtsen]

Kai.Grossjohann@CS.Uni-Dortmund.DE writes:

> Just installed pgnus-0.56 and w3-4.0pre.30 on Emacs 20.3, and this is
> what happened:
> 
> ,-----
> | Signaling: (wrong-number-of-arguments #<subr buffer-string> 3)
> |   (buffer-string nil nil (mm-handle-buffer part))

My bad.  Emacs 20.3's `buffer-string' doesn't take a BUFFER
parameter.

Er.  How weird.  `buffer-string' is an alias for `buffer-substring' in
XEmacs 21.2.  Has it always been that way?  And jere I just convinced
RMS to let `buffer-string' take an optional BUFFER parameter in Emacs
20.4, all for naught, it seems...

To clarify: In Emacs 20.4, `buffer-substring' takes mandatory START
and END params, while `buffer-string' takes an optional BUFFER param.
In XEmacs 21.2, there's only one function, which takes three optional
params -- start, end, and buffer.  I think the Emacs 20.4 thing makes
more sense.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: multipart/related test

[Hrvoje Niksic]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Kai.Grossjohann@CS.Uni-Dortmund.DE writes:
> 
> > Just installed pgnus-0.56 and w3-4.0pre.30 on Emacs 20.3, and this is
> > what happened:
> > 
> > ,-----
> > | Signaling: (wrong-number-of-arguments #<subr buffer-string> 3)
> > |   (buffer-string nil nil (mm-handle-buffer part))
> 
> My bad.  Emacs 20.3's `buffer-string' doesn't take a BUFFER
> parameter.
> 
> Er.  How weird.  `buffer-string' is an alias for `buffer-substring' in
> XEmacs 21.2.  Has it always been that way?  And jere I just convinced
> RMS to let `buffer-string' take an optional BUFFER parameter in Emacs
> 20.4, all for naught, it seems...
> 
> To clarify: In Emacs 20.4, `buffer-substring' takes mandatory START
> and END params, while `buffer-string' takes an optional BUFFER
> param.  In XEmacs 21.2, there's only one function, which takes three
> optional params -- start, end, and buffer.  I think the Emacs 20.4
> thing makes more sense.

So things were changed incompatibly -- again?  :-(

We can implement XEmacs `buffer-string' like this, but that's
monstrosity:

(defun buffer-string (&optional x y z)
  "@#$#@%#@$%#@$$@#$@#$@#"
  (if (or (bufferp x)
          (stringp x))
      (buffer-substring nil nil x)
    (buffer-substring x y z)))

After the `point-at-bol' fiasco, I'm not sure I want to see this code
in XEmacs.  :-(

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Be nice to your kids.
They'll choose your nursing home.

Re: multipart/related test

[Lars Magne Ingebrigtsen]

Hrvoje Niksic <hniksic@srce.hr> writes:

> We can implement XEmacs `buffer-string' like this, but that's
> monstrosity:

If it makes any difference

$ grep -n "(buffer-string" */*.el | grep -v "buffer-string)"

in xemacs-packages/lisp results in:

gnus/nndb.el:296:    (setq msg (buffer-string (point-min) (point-max)))
gnus/nndb.el:323:  (buffer-string (point-min) (point-max)))
text-modes/image-mode.el:36:		  (vector type :data (buffer-string start end)) nil nil 'no-error)))

I've now fixed nndb.el.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: multipart/related test

[Hrvoje Niksic]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Hrvoje Niksic <hniksic@srce.hr> writes:
> 
> > We can implement XEmacs `buffer-string' like this, but that's
> > monstrosity:
> 
> If it makes any difference
> 
> $ grep -n "(buffer-string" */*.el | grep -v "buffer-string)"
> 
> in xemacs-packages/lisp results in:
[...]

We cannot really know how many people are using `buffer-string' in
their code.  Fortunately, it is possible to make the function backward
compatible, but I, for one, will not bother sending out the patch; I'm 
way too disgusted.

As strange as it may sound, XEmacs has a user-base of its own, and
IMHO we cannot afford to change documented interfaces on Stallman's
whims, at least not in areas where XEmacs implemented stuff before FSF
Emacs.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Your lucky number today is 29842924728.  Look for it everywhere.

Re: multipart/related test

[Lars Magne Ingebrigtsen]

Hrvoje Niksic <hniksic@srce.hr> writes:

> As strange as it may sound, XEmacs has a user-base of its own, and
> IMHO we cannot afford to change documented interfaces on Stallman's
> whims, at least not in areas where XEmacs implemented stuff before FSF
> Emacs.

Well, this is my whim, and not Stallman's.  :-)

Here's how I think it happened:  I was programming under XEmacs, and I 
wrote `(buffer-string some-buffer)'.  I then switched to Emacs, and
the thing bugged out, of course.  (As it would have done under XEmacs, 
but I guess I never tried.)  I grumbled and rewrote it as
`(save-excursion (set-buffer some-buffer) (buffer-string))'.

And then I sent a patch to Stallman to make Emacs XEmacs-compliant (as
I, in a particularly dizzy moment, thought it to be), and he accepted
it.

I still do think that my dizzyness yielded a better function than the
hard truth.  `buffer-string' and `buffer-substring' have different
feeling, and I think it makes sense to have them as separate
functions.  I mean -- you seldom want to give a buffer argument to
`buffer-substring', but you often want to give it to `buffer-string',
so having to write `(buffer-string nil nil some-buffer)' feels weird
to me. 

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: multipart/related test

[Jan Vroonhof]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> And then I sent a patch to Stallman to make Emacs XEmacs-compliant (as
> I, in a particularly dizzy moment, thought it to be), and he accepted
> it.

This is FSF 20.4 isn't it, so there is still time to change it
back...Or has FSF 20.4 been released now.

Jan

Re: multipart/related test

[Hrvoje Niksic]

Jan Vroonhof <vroonhof@math.ethz.ch> writes:

> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> 
> > And then I sent a patch to Stallman to make Emacs XEmacs-compliant (as
> > I, in a particularly dizzy moment, thought it to be), and he accepted
> > it.
> 
> This is FSF 20.4 isn't it, so there is still time to change it
> back...

Only if you convince Stallman to either back out the BUFFER argument
to `buffer-substring' (unlikely) or to make `buffer-string' alias for
`buffer-substring', and allow optional arguments to the latter
(impossible.)

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Predestination was doomed from the start.

Re: multipart/related test

[Kai.Grossjohann]

[[ buffer-string vs. buffer-substring ]]

Here's what I see:

Emacs 20.3:     (buffer-string)
                (buffer-substring START END)

XEmacs 20.4:    (buffer-string &optional START END BUFFER)
                (buffer-substring &optional START END BUFFER)

So a compatible change would be to add an optional argument BUFFER to
the Emacs 20.3 implementation of buffer-substring.

buffer-string is more difficult, but I don't quite understand the
START and END arguments in XEmacs 20.4 here, anyway.  Either it's just
one function like XEmacs 20.4 buffer-substring, or it's two functions:

    (buffer-string &optional BUFFER)
    (buffer-substring START END &optional BUFFER)

Both ways have their merit.

Whatcha think?

kai
-- 
Life is hard and then you die.

Re: multipart/related test

[Simon Josefsson]

Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

> This email was kinda originated by Outlook Express, but I've edited
> it by hand afterwards. This text is green. In the left margin
> there's a background picture. And here:
> [cid:003e01be1642$a526f940$b86efea9@win] there's a picture with
> baseline alignment.

It turned out OK here, but after viewing one of theese HTML emails,
the Subject: lines has disappeared from all articles (in the article
buffer, they look alright in the summary buffer).

Perhaps it's a w3 matter, but how do I make it not listen
bgcolor/fgcolor stuff when my emacs is on a tty?  It looks kind of
ugly..

Re: multipart/related test

[William M. Perry]

Simon Josefsson <jas@pdc.kth.se> writes:

> Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
> 
> > This email was kinda originated by Outlook Express, but I've edited
> > it by hand afterwards. This text is green. In the left margin
> > there's a background picture. And here:
> > [cid:003e01be1642$a526f940$b86efea9@win] there's a picture with
> > baseline alignment.
> 
> It turned out OK here, but after viewing one of theese HTML emails,
> the Subject: lines has disappeared from all articles (in the article
> buffer, they look alright in the summary buffer).
> 
> Perhaps it's a w3 matter, but how do I make it not listen
> bgcolor/fgcolor stuff when my emacs is on a tty?  It looks kind of
> ugly..

  (setq w3-user-colors-take-precedence t)

-bp