headers
noreply | 10 Mar 2002 00:40
Picon
Favicon

[ mh-e-Feature Requests-527946 ] Make show buffer read-only

Feature Requests item #527946, was opened at 2002-03-09 15:40
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=363357&aid=527946&group_id=13357

Category: General
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Bill Wohler (wohler)
Assigned to: Nobody/Anonymous (nobody)
Summary: Make show buffer read-only

Initial Comment:
From: Greg Hudson <ghudson <at> MIT.EDU>
To: bug-gnu-emacs <at> gnu.org
Subject: mh-e and buffer read-only status
Date: Wed, 6 Mar 2002 15:51:26 -0500

This is just a suggestion, not a bug report, so no
precise version or platform information should be
needed.  I verified that emacs 21.1 has the behavior
I'm complaining about.

A user here noticed that when you use rmail, your mail
messages show up in a read-only buffer; however, when
you use mh-e, the mail messages show up in a writable
buffer, although any modifications you make to the
buffer are lost (I think after prompting the user) when
you show the next message.
(Continue reading)

Permalink | Reply | 0 comments |
headers
noreply | 10 Mar 2002 23:55
Picon
Favicon

[ mh-e-Feature Requests-527946 ] Make show buffer read-only

Feature Requests item #527946, was opened at 2002-03-09 15:40
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=363357&aid=527946&group_id=13357

Category: General
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Bill Wohler (wohler)
Assigned to: Nobody/Anonymous (nobody)
Summary: Make show buffer read-only

Initial Comment:
From: Greg Hudson <ghudson <at> MIT.EDU>
To: bug-gnu-emacs <at> gnu.org
Subject: mh-e and buffer read-only status
Date: Wed, 6 Mar 2002 15:51:26 -0500

This is just a suggestion, not a bug report, so no
precise version or platform information should be
needed.  I verified that emacs 21.1 has the behavior
I'm complaining about.

A user here noticed that when you use rmail, your mail
messages show up in a read-only buffer; however, when
you use mh-e, the mail messages show up in a writable
buffer, although any modifications you make to the
buffer are lost (I think after prompting the user) when
you show the next message.
(Continue reading)

Permalink | Reply | 0 comments |
headers
chad | 11 Mar 2002 04:25
Picon
Favicon

Re: Nicer display of MIME messages

This looks promising, although it mirrors some work that one of the
other mh-e developers was talking about in the recent past.  If you're
interested in following it up, I'll point out that it stomps over the
built-in mh-e message header highlighting, and it breaks use of
goto-addr.  I'm sending this along with your original message to
mh-e-devel, in case some people there aren't on the -users list.

chad

> From: Satyaki Das <satyakid <at> stanford.edu>
> Subject: Nicer display of MIME messages
> To: mh-e-users <at> lists.sourceforge.net
> Date: Sun, 10 Mar 2002 17:48:54 -0800
> 
> 
> Recently I modified one of the functions used by mh-e to
> display messages to use MML, the mime display engine of GNUS.
> This makes mh-e really pretty. It does inline images in
> Emacs 21, button-like display of attachments, PGP/MIME
> support, X-Face etc.
> 
> It is quite easy to use the mime composition part by binding
> some of the keys to use MML functions. The mime handling is
> a XML-like version of mhn/mhbuild. The only advantage over
> mhn is that it does PGP/MIME out of the box. Some keybindings
> for mime composition is added in the .emacs snippet below.
> 
> Now that you are convinced that this is all good, here are
> some potential problems:
>   1. You need a CVS version of gnus, the later the better.
(Continue reading)

Permalink | Reply | 18 comments |
headers
Satyaki Das | 11 Mar 2002 06:24
X-Face
Picon
Favicon

Re: Nicer display of MIME messages

chad <y <at> mit.edu> writes:
> 
> This looks promising, although it mirrors some work that one of the
> other mh-e developers was talking about in the recent past.

Indeed. I looked at the mh-e-users archives and saw a
discussion under a thread with subject "Ideas for future mh-e
releases".

>                                                              If you're
> interested in following it up, I'll point out that it stomps over the
> built-in mh-e message header highlighting, 

Yes, you are right. Gnus has GNUS-VISIBLE-HEADERS and
GNUS-IGNORED-HEADERS which are roughly analogous to
MH-VISIBLE-HEADERS and MH-INVISIBLE-HEADERS. So binding
GNUS-*-HEADERS appropriately in the MH-DISPLAY-MSG function
should fix this problem.

>                                            and it breaks use of
> goto-addr.  I'm sending this along with your original message to
> mh-e-devel, in case some people there aren't on the -users list.

I think the problem with GOTO-ADDR can be avoided if we could
figure out how to get WIDGET-BUTTON-PRESS to call the right
function. I will investigate that.

Satyaki
--

-- 
All say, "How hard it is that we have to die"--a strange complaint to come from
(Continue reading)

Permalink | Reply | 17 comments |
headers
Bill Wohler | 11 Mar 2002 16:02
X-Face
Picon
Picon
Gravatar

Re: Nicer display of MIME messages

Satyaki Das <satyakid <at> stanford.edu> writes:
> Recently I modified one of the functions used by mh-e to
> display messages to use MML, the mime display engine of GNUS.

  That's essentially what I had in mind...

>   1. You need a CVS version of gnus, the later the better.

  Unfortunately, mh-e has to work with Emacs 20.

>   2. I couldn't get mailcrypt to work for PGP support.

  This is not good.

>   3. I don't understand the MML code very well. So I was leaking
>      buffers like crazy.

  Nor that ;-).

  When you think you've addressed these issues, I would be grateful if
  you could submit a patch at mh-e.sourceforge.net. You can also post it
  here for us to try first. Note that I use mailcrypt every day,
  although if gpg.el works, that might be OK.

  Thanks!

--
Bill Wohler <wohler <at> newt.com>  http://www.newt.com/wohler/  GnuPG ID:610BD9AD
Maintainer of comp.mail.mh FAQ and mh-e. Vote Libertarian!
If you're passed on the right, you're in the wrong lane.
(Continue reading)

Permalink | Reply | 1 comment |
headers
noreply | 11 Mar 2002 21:07
Picon
Favicon

[ mh-e-Feature Requests-527946 ] Make show buffer read-only

Feature Requests item #527946, was opened at 2002-03-09 18:40
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=363357&aid=527946&group_id=13357

Category: General
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Bill Wohler (wohler)
Assigned to: Nobody/Anonymous (nobody)
Summary: Make show buffer read-only

Initial Comment:
From: Greg Hudson <ghudson <at> MIT.EDU>
To: bug-gnu-emacs <at> gnu.org
Subject: mh-e and buffer read-only status
Date: Wed, 6 Mar 2002 15:51:26 -0500

This is just a suggestion, not a bug report, so no
precise version or platform information should be
needed.  I verified that emacs 21.1 has the behavior
I'm complaining about.

A user here noticed that when you use rmail, your mail
messages show up in a read-only buffer; however, when
you use mh-e, the mail messages show up in a writable
buffer, although any modifications you make to the
buffer are lost (I think after prompting the user) when
you show the next message.
(Continue reading)

Permalink | Reply | 0 comments |
headers
noreply | 11 Mar 2002 21:08
Picon
Favicon

[ mh-e-Feature Requests-527946 ] Make show buffer read-only

Feature Requests item #527946, was opened at 2002-03-09 18:40
You can respond by visiting: 
http://sourceforge.net/tracker/?func=detail&atid=363357&aid=527946&group_id=13357

Category: General
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Bill Wohler (wohler)
Assigned to: Nobody/Anonymous (nobody)
Summary: Make show buffer read-only

Initial Comment:
From: Greg Hudson <ghudson <at> MIT.EDU>
To: bug-gnu-emacs <at> gnu.org
Subject: mh-e and buffer read-only status
Date: Wed, 6 Mar 2002 15:51:26 -0500

This is just a suggestion, not a bug report, so no
precise version or platform information should be
needed.  I verified that emacs 21.1 has the behavior
I'm complaining about.

A user here noticed that when you use rmail, your mail
messages show up in a read-only buffer; however, when
you use mh-e, the mail messages show up in a writable
buffer, although any modifications you make to the
buffer are lost (I think after prompting the user) when
you show the next message.
(Continue reading)

Permalink | Reply | 0 comments |
headers
Satyaki Das | 12 Mar 2002 03:34
X-Face
Picon
Favicon

Re: Nicer display of MIME messages

Bill Wohler <wohler <at> newt.com> writes:
> Satyaki Das <satyakid <at> stanford.edu> writes:
> > Recently I modified one of the functions used by mh-e to
> > display messages to use MML, the mime display engine of GNUS.
>   
>   That's essentially what I had in mind...
> 
> >   1. You need a CVS version of gnus, the later the better.
> 
>   Unfortunately, mh-e has to work with Emacs 20.

I guess mh-e could just continue to use the current code for
emacs 20 and use the new stuff for emacs with a later version
of gnus. Anyway, what I have has way too many issues for
general use right now. I will try to see if I can solve them.

> 
> >   2. I couldn't get mailcrypt to work for PGP support.
> 
>   This is not good.

Actually I went back and tried mailcrypt once more. It seems
to work okay for non-mime messages but fails with the newer
pgp/mime messages that seem to be the rage these days :-).

> 
> >   3. I don't understand the MML code very well. So I was leaking
> >      buffers like crazy.
> 
>   Nor that ;-).
(Continue reading)

Permalink | Reply | 0 comments |
headers
Satyaki Das | 17 Mar 2002 06:37
X-Face
Picon
Favicon

Re: Nicer display of MIME messages

I have rewritten the mime display code from last week. It
should work much better now. I don't have to "advice"
functions to clean up buffers anymore :-).

Another thing I noticed was that in the definition of
mh-show-mode, font-lock-support-mode is set to nil. This
makes font-lock slower for larger emails in Emacs 21. Is
there any particular reason to do this?

Thanks,
Satyaki

--- .emacs ---
(require 'mh-e)
(require 'mh-ext)
(setq mm-verify-option 'always)
(setq mm-decrypt-option 'always)
(setq mm-discouraged-alternatives '("text/html"))
(add-hook 'mh-before-send-letter-hook 'mh-mml-to-mime)
(add-hook
 'mh-letter-mode-hook
 (lambda ()
   (define-key mh-letter-mode-map "\C-cs" 'mml-secure-message-sign-pgpmime)
   (define-key mh-letter-mode-map "\C-ce"
     'mml-secure-message-encrypt-pgpmime)
   (define-key mh-letter-mode-map "\C-ca" 'mml-attach-file)
   (define-key mh-letter-mode-map "\C-cm" 'mh-mml-to-mime)))

--- mh-ext.el ---
(require 'cl)
(Continue reading)

Permalink | Reply | 0 comments |
headers
chad | 17 Mar 2002 18:31
Picon
Favicon

Re: Nicer display of MIME messages

You latest code throws an error for the message at http://www.mit.edu/~yandros/break-mh-ext.mail

 Debugger entered--Lisp error: (wrong-type-argument stringp nil)
  string-match("text/plain" nil)
  mm-automatic-display-p(nil)
  mh-mime-display-single(nil)
  mh-mime-display-part(nil)
  mh-mm-inline-message((#<buffer  *mm-uu*<2>> ("message/rfc822" (charset . gnus-decoded)) nil
(lambda nil (let ... ... ...)) nil nil nil nil))
  mm-display-inline((#<buffer  *mm-uu*<2>> ("message/rfc822" (charset . gnus-decoded)) nil (lambda
nil (let ... ... ...)) nil nil nil nil))
  mm-display-part((#<buffer  *mm-uu*<2>> ("message/rfc822" (charset . gnus-decoded)) nil (lambda nil
(let ... ... ...)) nil nil nil nil) t)
  mh-mime-display-single((#<buffer  *mm-uu*<2>> ("message/rfc822" (charset . gnus-decoded)) nil
(lambda nil (let ... ... ...)) nil nil nil nil))
  mh-mime-display-part((#<buffer  *mm-uu*<2>> ("message/rfc822" (charset . gnus-decoded)) nil
(lambda nil (let ... ... ...)) nil nil nil nil))
  mapcar(mh-mime-display-part ((#<buffer  *mm-uu*> ("text/plain" ...) nil (lambda nil ...) nil nil nil
nil) (#<buffer  *mm-uu*<2>> ("message/rfc822" ...) nil (lambda nil ...) nil nil nil nil) (#<buffer 
*mm-uu*<3>> ("text/plain" ...) nil nil nil nil nil nil)))
  mh-mime-display-mixed(((#<buffer  *mm-uu*> ("text/plain" ...) nil (lambda nil ...) nil nil nil nil)
(#<buffer  *mm-uu*<2>> ("message/rfc822" ...) nil (lambda nil ...) nil nil nil nil) (#<buffer 
*mm-uu*<3>> ("text/plain" ...) nil nil nil nil nil nil)))
  mh-mime-display-part(("multipart/mixed" (#<buffer  *mm-uu*> ("text/plain" ...) nil (lambda nil ...)
nil nil nil nil) (#<buffer  *mm-uu*<2>> ("message/rfc822" ...) nil (lambda nil ...) nil nil nil nil)
(#<buffer  *mm-uu*<3>> ("text/plain" ...) nil nil nil nil nil nil)))
  mh-mime-display()
  mh-display-msg(347 "+inbox")
  mh-show-msg(nil)
  mh-show()
(Continue reading)

Permalink | Reply | 16 comments |

Gmane