From: dhall@apk.net (d. hall)
Subject: POP3 function, and user format functions
Date: 11 Jan 1996 14:35:01 -0500 [thread overview]
Message-ID: <yv1ent6le3e.fsf_-_@junior.wariat.org> (raw)
In-Reply-To: "d. cord hall"'s message of Wed, 10 Jan 1996 14:14:40 -0500
-----BEGIN PGP SIGNED MESSAGE-----
the following function i wrote to bypass having to recompile movemail.
(require 'ange-ftp)
(defvar mail-pop-user nil)
(defvar mail-pop-pass nil)
(defvar mail-pop-host "pop")
(defvar mail-pop-spool-file nil)
(defun mail-pop-mail-retrieve ()
(interactive)
(let ((user-name (or mail-pop-user
(user-login-name)))
(my-passwd (or mail-pop-pass
(ange-ftp-read-passwd "Enter your password: ")))
(pop-server mail-pop-host)
(spool-file (or mail-pop-spool-file
(getenv "MAIL")
(concat rmail-spool-directory
(user-login-name)))))
(save-excursion
(generate-new-buffer "*popclient*")
(call-process "popclient" nil "*popclient*" nil
"-3"
"-v"
"-u" user-name
"-p" my-passwd
"-o" spool-file
pop-server
))))
Now, my other problem. I emailed the backtrace via gnus-bug (which game a
further error that I had malformed sources in nnmail).
I have a personalized format function for gnus-summary-line-format, which
makes it look more like vm or rmail in display.
(setq gnus-summary-line-format "%U%R%z%[%-16,16n%]: %uX %I`%s`\n")
(defun gnus-user-format-function-X (header) "\
Return a string like MMM DD LLLL from the header."
(let* ((header-lines (mail-header-lines header))
(header-date (mail-header-date header))
(date-vector (timezone-parse-date header-date))
(date-mon (aref date-vector 1))
(date-day (aref date-vector 2))
(string-lines (if (> header-lines 9999)
"????"
(number-to-string header-lines)))
(string-mon (or (capitalize
(car (nth
(1- (string-to-number date-mon))
timezone-months-assoc)))
"???"))
(string-day (or date-day "??")))
(format "%s %2s %4s" string-mon string-day string-lines)))
If I byte-compile this function w/o first loading Gnus, I get an error the
next time I attempt to run Gnus. So I have the change the %uX to %d so
Gnus will load and run, and then re-byte-compile the function, and then
change the %d back to %uX and it runs just fine. Unfortunately I didn't
save the backtrace, but Lars should be seeing a copy of it soon. It has be
completely baffled. Am I not loading a file before byte-compiling? Or is
it another Emacs 19.30.1 bug?
d.
- --
<<I'm sorry Mr. President. I don't dance.>>
~ from clear and present danger
-----BEGIN PGP SIGNATURE-----
Version: 2.6.2
Comment: Processed by Mailcrypt 3.4, an Emacs/PGP interface
iQCVAwUBMPVl44X26urqpgG1AQEVwAQAmBJoy9Nhc9LoSB5CSaegHPvm5D/oxTE+
6bH5ucnWsHtlNLx82frIirhsjmX0X7OnAaS4C/7S7SxPq5gtHDacwFqOBmIryXp2
tGn5cRDZvMi4HacmZIjtJOWpCFMHA9jZvBpwoywsmBoIEiM+GGATqVzb/QvcpZ0y
qUOZdGI5hmk=
=IUTV
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~1996-01-11 19:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-01-07 22:06 gnus-topic and popmail access d. hall
1996-01-08 1:58 ` Jason L Tibbitts III
1996-01-08 2:46 ` d. hall
1996-01-10 18:46 ` Lars Magne Ingebrigtsen
1996-01-10 19:14 ` d. cord hall
1996-01-11 19:35 ` d. hall [this message]
1996-01-08 14:02 ` Jack Vinson
1996-01-08 14:38 ` Kai Grossjohann
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=yv1ent6le3e.fsf_-_@junior.wariat.org \
--to=dhall@apk.net \
/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).