On 20 Nov, Jon Steinhart wrote:
Disagreement is good. I do it too! If I get a message with 20 photos
attached, I hate having to hit Ctrl-C 20 times just to get to the next
message. And I also have problems with multiple text parts since the
way things get exec'd I haven't found a
So to summarize thus far, the MH-E needs of nmh are:
- A boolean function for mh-format which is true if attachments are
present (say, called attach).
- Content-Disposition support (inline, attachment, filename).
- Better PGP/MIME (RFC 3056) composition (perhaps this *can* be
Where we're had to move away from nmh towards gnus is in MIME
composition (e.g. for the ability to specify inline/attachment).
You might want to look at the attachment stuff that I checked in a while
back. I implemented it in such a way that it could easily be incorporated
into MH-E. The
Jon Steinhart [EMAIL PROTECTED] wrote:
Where we're had to move away from nmh towards gnus is in MIME
composition (e.g. for the ability to specify inline/attachment).
You might want to look at the attachment stuff that I checked in a while
back. I implemented it in such a way that it
In message [EMAIL PROTECTED], Jon Steinhart
writes:
Seems to me that my notion of scanning attachments is getting the most
attention here, even though it's not the most important part to me. My
main interest is in being able to read attachments in a more consistent
way. Maybe an example
Jon Steinhart wrote:
If I get a message with 20 photos
attached, I hate having to hit Ctrl-C 20 times just to get to the next
message.
I'm not disagreeing with you ;-), Jon... the interface *is* klunky.
But, FWIW, Ctrl-\ will abort showing the current message.
Jerry
--
Jerry Peek, [EMAIL
I've changed the Subject and included [EMAIL PROTECTED]
since we've spent the last year improving MIME handling in Gnus since
raw MH wouldn't work for us. We should be able to provide some
suggestions which would allow us to use more MH and less Gnus. Peter?
Satyaki?
Jon Steinhart
I've changed the Subject and included [EMAIL PROTECTED]
since we've spent the last year improving MIME handling in Gnus since
raw MH wouldn't work for us. We should be able to provide some
suggestions which would allow us to use more MH and less Gnus. Peter?
Satyaki?
Yeah, should
On Tue, Nov 19, 2002 at 08:42:42PM -0800, Bill Wohler wrote:
This might be an intriguing option to some, but it should not be the
default.
Agreed. I'd use it sometimes.
Matt
If you're passed on the right, you're in the wrong lane.
Or in Britain or some ex-British colony!
Jon Steinhart [EMAIL PROTECTED] wrote:
What I have in mind is twofold. First, I'd like to be able to optionally
scan with message parts listed. Second, I'd like to be able to have an
option to show/next/prev that says show the cur/next/prev message part.
I just use
mhlist next
when I
10 matches
Mail list logo
