Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: [Patch] define-composed-chars mistake, additions
- X-seq: zsh-workers 26269
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxxxxx
- Subject: Re: [Patch] define-composed-chars mistake, additions
- Date: Fri, 09 Jan 2009 09:39:34 -0800
- In-reply-to: <2d460de70901090830s77bbb789p6190a0f2822544ed@xxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <alpine.LNX.2.00.0901090157360.21189@xxxxxxxxxxxxxxx> <2d460de70901090118y4e2926e8g61bf0aaca8bc12f6@xxxxxxxxxxxxxx> <090109080136.ZM1522@xxxxxxxxxxxxxxxxxxxxxx> <2d460de70901090830s77bbb789p6190a0f2822544ed@xxxxxxxxxxxxxx>
On Jan 9, 5:30pm, Richard Hartmann wrote:
}
} Inline stuff can be affected by line breaks and other crap, though.
If that hasn't been a problem for the previous more than ten years,
why it is going to suddenly become a problem now?
I suppose the answer is "web-based mail clients." Grumble.
} If you want, I can start sending my patches both inline & attached,
} though.
Please don't do that; it both exposes the MIME structure in the mailing
list archive *and* duplicates the information.
If you simply must use attachments, just label them text/plain, unless
they're so huge you've compressed them or some such, of course.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author