Re: How to display a mail in raw format

2001-04-13 Thread John P. Verel

On 04/13/01, 08:39:03AM -0400, darren chamberlain wrote:
 Dave Pearson ([EMAIL PROTECTED]) said something to this effect on 04/13/2001:
Toggling header mode ("h") will let you see all the headers in the mutt
pager, but it won't show you the entire e-mail as "raw" since it still
parser MIME. Editing the messages ("e") doesn't show you all the headers
(at least, not in v1.2.4i that I'm running).
  
   Depends on the editor, perhaps.  With vim 5.7 all headers are visible.
  
  How does choice of editor affect which headers are passed to it for editing
  by mutt?
 
 I did hit 'h' to show all the headers, and then 'e' to edit the
 message in $editor, and all headers were displayed and editable.
 If you hit 'e', without turning off header weeding, then $editor
 will only open up what you see. Does that work for anyone else?
If I press 'e' with $editor set to vim, I see all headers.  Having
pressed 'h' before makes no difference.  I have not experimented with
other editors (emacs, joe, pico, etc) to see if there is any difference
in behavior.

John
 
 (darren)
 
 -- 
 What you do instead of your real work *is* your real work.
 -- Roger Ebert

-- 
John P. Verel
Norwalk, CT



Re: How to display a mail in raw format

2001-04-13 Thread Mike Broome

On Thu, Apr 12, 2001 at 09:42:52PM -0400, John P. Verel wrote:
 On 04/12/01, 05:22:21PM -0400, Mike Broome wrote:
  I've found that piping the message out to cat (eg. "|cat") or more
  (eg. "|more") does the trick for me.  This will dump the entire
  message, including header, MIME separators, unrecognized (to mutt)
  attachments.
  
  Toggling header mode ("h") will let you see all the headers in the
  mutt pager, but it won't show you the entire e-mail as "raw" since it
  still parser MIME.  Editing the messages ("e") doesn't show you all the
  headers (at least, not in v1.2.4i that I'm running).
  
 Depends on the editor, perhaps.  With vim 5.7 all headers are visible.

I don't see how it could plausibly depend on the editor since it's mutt
that decides what to give to the editor to edit.

But now that I look at it in more detail, it looks like I actually *am*
getting all the headers in the editor (of course, I have to have
"edit_hdrs" set in .muttrc to get any headers).  I thought I wasn't
getting all the Received: lines and the initial From_ line, but if I
scroll up in the editor, I see them.  It must have been an artifact of
invoking vim with the argument '+/^$' to have it search for the first
blank line; that scrolls most of the header lines off the screen.

Mike

-- 
Mike Broome
mbroome(at)employees.org



Re: How to display a mail in raw format

2001-04-13 Thread Thomas Roessler

On 2001-04-13 09:33:17 -0400, John P. Verel wrote:

 If I press 'e' with $editor set to vim, I see all headers.
 Having pressed 'h' before makes no difference.  I have not
 experimented with other editors (emacs, joe, pico, etc) to see if
 there is any difference in behavior.

You may wish to make sure that you both have bound edit-message to
'e', and not resend-mesasge.

-- 
Thomas Roessler [EMAIL PROTECTED]



Re: How to display a mail in raw format

2001-04-13 Thread John P. Verel

On 04/13/01, 04:10:46PM +0200, Thomas Roessler wrote:
 On 2001-04-13 09:33:17 -0400, John P. Verel wrote:
 
  If I press 'e' with $editor set to vim, I see all headers.
  Having pressed 'h' before makes no difference.  I have not
  experimented with other editors (emacs, joe, pico, etc) to see if
  there is any difference in behavior.
 
 You may wish to make sure that you both have bound edit-message to
 'e', and not resend-mesasge.
 
Confirmed.  My bindings are default as respects these.  Escape e yields
resend, e opens vim.  Resend-message produces just the standard headers.
e produces the whole landslide of 'em :)

John
 -- 
 Thomas Roessler   [EMAIL PROTECTED]

-- 
John P. Verel
Norwalk, CT



How to display a mail in raw format

2001-04-12 Thread Tobias Schenk

Hello,

I was wondering how one can display any mail in it's pure, raw format within Mutt. So 
as to get the same result than if I would load the mbox file into an editor and look 
at a particular message.

Did I miss how to do it in the docs? Thank you.

Toby




Re: How to display a mail in raw format

2001-04-12 Thread Lars Hecking


 I was wondering how one can display any mail in it's pure, raw format within Mutt. 
So as to get the same result than if I would load the mbox file into an editor and 
look at a particular message.

e   edit   edit the raw message

 if you can exit your editor without saving anything back to disk ;-)




Re: How to display a mail in raw format

2001-04-12 Thread Michael Galloway

Hi Tobias!

if you just want to see all the headers, the command h will show you them.

-- michael

On Thu, 12 Apr 2001, Tobias Schenk wrote:

 Hello,
 
 I was wondering how one can display any mail in it's pure, raw format within Mutt. 
So as to get the same result than if I would load the mbox file into an editor and 
look at a particular message.
 
 Did I miss how to do it in the docs? Thank you.
 
 Toby
 
 



Re: How to display a mail in raw format

2001-04-12 Thread John P. Verel

On 04/12/01, 05:22:21PM -0400, Mike Broome wrote:
 I've found that piping the message out to cat (eg. "|cat") or more
 (eg. "|more") does the trick for me.  This will dump the entire
 message, including header, MIME separators, unrecognized (to mutt)
 attachments.
 
 Toggling header mode ("h") will let you see all the headers in the
 mutt pager, but it won't show you the entire e-mail as "raw" since it
 still parser MIME.  Editing the messages ("e") doesn't show you all the
 headers (at least, not in v1.2.4i that I'm running).
 
Depends on the editor, perhaps.  With vim 5.7 all headers are visible.

John
 Mike
 
 On Thu, Apr 12, 2001 at 11:32:00AM +0200, Tobias Schenk wrote:
  Hello,
  
  I was wondering how one can display any mail in it's pure, raw format within Mutt. 
So as to get the same result than if I would load the mbox file into an editor and 
look at a particular message.
  
  Did I miss how to do it in the docs? Thank you.
  
  Toby
 
 -- 
 Mike Broome
 mbroome(at)employees.org

-- 
John P. Verel
Norwalk, CT