From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Need coding system expert assistance! (nnimap on Windows problem)
Date: Sat, 27 Dec 2008 16:05:42 +0100 [thread overview]
Message-ID: <ur63tacah.fsf@dod.no> (raw)
Hi,
Could someone that are experts in coding systems and mule, please take a
look at the thread starting here?
http://thread.gmane.org/gmane.emacs.gnus.general/67809
nntp://news.gmane.org/gmane.emacs.gnus.general/67809
The short form of this story is:
In GNU emacs on windows there is a translation of end of line in the
*nnimap* buffer from LF to CRLF, that is messed up when a CRLF sequence
is encounted in the IMAP protocol. It turns into CRCRLF, and that
messes up the IMAP traffic
Does anyone know what may be causing this? And if so, what to set to
avoid it?
Thanx!
- Steinar
reply other threads:[~2008-12-27 15:05 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ur63tacah.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).