From: Kai Harries <kai.harries@gmail.com>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: bounce/forward not working due to CR at line end
Date: Thu, 16 Nov 2017 20:48:48 +0100 [thread overview]
Message-ID: <87shdeovhb.fsf@x230.kaiha.invalid> (raw)
In-Reply-To: <877eur5i33.fsf@tesseract.cs.unb.ca>
David Bremner <david@tethera.net> writes:
> Kai Harries <kai.harries@gmail.com> writes:
>
>> David Bremner <david@tethera.net> writes:
>>
>>> During off-list discussion, Kai mentioned id:87a7zsm5ol.fsf@gmail.com as
>>> a message that he cannot bounce (and also not forward?). For me this
>>> forwards fine, but does not bounce because it has a corrupted Cc header,
>>> and my MTA rejects it. That doesn't sound related to the original
>>> problem report (nothing about line endings).
>>
>> Can you please evaluate the following on your system:
>>
>> (call-process "notmuch" nil t nil "show" "--format=raw" "id:87a7zsm5ol.fsf@gmail.com")
>>
>> If I do this on my system, then the text that is inserted into the
>> buffer has ^M (CR) at the line endings. Is this expected?
>
> No ^M line endings for me. Can you check the file on disk? Maybe "od -a"
> lacking a better idea.
`od -a` does also show that the lines are ending with 'cr' and 'nl'
this is correct according to RFC 2822 [1].
According to this [2] Emacs normally converts line endings to only 'nl'
(newline) when opening a DOS file. This works on my system, if I open the
file from disk no carriage-return (^M) is shown.
Not working is inserting the output of `notmuch show` into a buffer. If
I do this, then the carriage-return (^M) is shown.
David, I assume your system is also a Linux, does
notmuch show --format=raw id:1472041345236.7014@de.bosch.com | od -a
also show 'cr' and 'nl' as line ending?
If No, then my `notmuch show` behaves different.
If Yes, then my Emacs behaves different when inserting text with DOS
line endings into a buffer.
[1] https://tools.ietf.org/html/rfc2822#section-2.2
[2] https://www.gnu.org/software/emacs/manual/html_mono/emacs.html#Coding-Systems
next prev parent reply other threads:[~2017-11-16 19:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 20:34 bounce/forward not working due to CR at line end Kai Harries
2017-11-15 12:43 ` David Bremner
2017-11-15 21:08 ` Kai Harries
2017-11-15 21:48 ` David Bremner
2017-11-16 15:57 ` Tomi Ollila
2017-11-16 19:48 ` Kai Harries [this message]
2017-11-17 1:08 ` David Bremner
2017-11-17 18:16 ` Kai Harries
2017-11-18 15:30 ` David Bremner
2017-11-19 12:25 ` Gaute Hope
2017-11-19 15:33 ` Kai Harries
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87shdeovhb.fsf@x230.kaiha.invalid \
--to=kai.harries@gmail.com \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/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 public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).