all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "David J. Biesack" <David.Biesack@sas.com>
Cc: 4448@emacsbugs.donarmstrong.com
Subject: bug#4448: 23.1; unrmail fails if buffer has mixed line endings (patch)
Date: Thu, 17 Sep 2009 10:06:05 -0400	[thread overview]
Message-ID: <jwvbpl91xcs.fsf-monnier+emacsbugreports@gnu.org> (raw)
In-Reply-To: <ytbws3xwwwt.fsf@sas.com> (David J. Biesack's message of "Thu, 17 Sep 2009 08:58:10 -0400")

>> > If you have to modify the code to detect the situation and generate
>> > an more meaningful error message, there should be clear
>> > instructions on how to fix it.... which is still not very friendly.
>> Run it through dos2unix or "flip -u", or even find-file-literally in
>> Emacs, then remove all ^M characters and save.
> Yes, I know how to convert; I have an elisp function named ^m that
> does this, but it's an annoyance and it is unknown how many other
> users will encounter this.  Again, I assert that if Emacs created rmail
> files with ^m in them, then  Emacs should repair them, especially if
> Emacs forces mbox conversion.

Agreed.
Of course, maybe the ^Ms were not added by Emacs but by your networked
file system.  Still, if the BABYL file worked fine with Emacs-22,
I think we should try and make it work fine with Emacs-23 as well.


        Stefan





  reply	other threads:[~2009-09-17 14:06 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16 13:28 bug#4448: 23.1; unrmail fails if buffer has mixed line endings (patch) David J. Biesack
2009-09-16 17:17 ` Eli Zaretskii
2009-09-16 17:48   ` David J. Biesack
2009-09-16 20:33     ` Eli Zaretskii
2009-09-17 12:58       ` David J. Biesack
2009-09-17 14:06         ` Stefan Monnier [this message]
2009-09-17 14:56           ` David J. Biesack

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=jwvbpl91xcs.fsf-monnier+emacsbugreports@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=4448@emacsbugs.donarmstrong.com \
    --cc=David.Biesack@sas.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.