From: Dan Schmidt <dfan@harmonixmusic.com>
Subject: Re: pop error in 0.81 and 0.82
Date: 20 Jan 1997 13:37:13 -0500 [thread overview]
Message-ID: <wkiv4sqjl2.fsf@harmonixmusic.com> (raw)
In-Reply-To: Karl Kleinpaste's message of 20 Jan 1997 12:29:01 -0500
Karl Kleinpaste <karl@jprc.com> writes:
| The change below ("diff -u", 0.80 -> 0.82) breaks movemail usage for
| POP mail access:
|
| --- nnmail.el Sat Jan 18 13:13:58 1997
| +++ .bad/nnmail.el Thu Jan 16 18:45:30 1997
| @@ -548,7 +550,7 @@
| exec-directory)
| nil errors nil inbox tofile)
| (when nnmail-internal-password
| - (list nnmail-internal-password))))))
| + (list (prin1-to-string nnmail-internal-password)))))))
| (if (not (buffer-modified-p errors))
| ;; No output => movemail won
| (progn
|
| The problem is that
| (list nnmail-internal-password)
| generates
| ("xxxxx")
| while
| (list (prin1-to-string nnmail-internal-password))
| generates
| ("\"xxxxx\"")
|
| Reverting to the non-prin1 case makes it work again.
This is my code (sorry); I added it because otherwise passwords with
spaces were being passed to movemail as two separate arguments.
Is there a solution that will work for both of us?
Dan
prev parent reply other threads:[~1997-01-20 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-01-20 17:29 Karl Kleinpaste
1997-01-20 18:37 ` Dan Schmidt [this message]
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=wkiv4sqjl2.fsf@harmonixmusic.com \
--to=dfan@harmonixmusic.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.
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).