From: Daniel Simms <dsimms@dsimms.com>
Cc: ding@ifi.uio.no
Subject: Re: pop mailboxes
Date: 04 Feb 1997 15:00:37 -0800 [thread overview]
Message-ID: <x56808uqga.fsf@ba.alink.net> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 04 Feb 1997 20:41:00 +0100
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 2574 bytes --]
>>>>> "LMI" == Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:
LMI> I don't see why ange-ftp should meddle with file names that
LMI> start with "po:".
Well it's *almost* how you specify remote files, ie /host:file (or
/user@host:file), no?
LMI> What effects are you seeing?
ange-ftp tries to open an ftp session to "po", which is non-existant,
(and even if it was, wouldn't have my mail on it :) Here's a trace
from the call in question. (And before you freak out, the function I
use for nnmail-movemail-program does grok the ":" delimited pop
maildrop.)
;Signaling: (ftp-error "FTP Error: OPEN request failed: ftp: po: unknown host")
; signal(ftp-error ("FTP Error: OPEN request failed: ftp: po: unknown host"))
; ange-ftp-error("po" "dsimms" "OPEN request failed: ftp: po: unknown host")
; ange-ftp-normal-login("po" "dsimms" "" "" #<process *ftp dsimms@po*>)
; ange-ftp-get-process("po" "dsimms")
; ange-ftp-host-type("po" "dsimms")
; ange-ftp-expand-dir("po" "dsimms" "~")
; ange-ftp-canonize-filename("/po:pop.alink.net:110:apop:n:dsimms%alink.net:*")
; ange-ftp-expand-file-name("/po:pop.alink.net:110:apop:n:dsimms%alink.net:*" nil)
; apply(ange-ftp-expand-file-name ("/po:pop.alink.net:110:apop:n:dsimms%alink.net:*" nil))
; ange-ftp-hook-function(expand-file-name "/po:pop.alink.net:110:apop:n:dsimms%alink.net:*" nil)
; expand-file-name("/po:pop.alink.net:110:apop:n:dsimms%alink.net:*")
; ange-ftp-file-directory-p("/po:pop.alink.net:110:apop:n:dsimms%alink.net:*")
; apply(ange-ftp-file-directory-p "/po:pop.alink.net:110:apop:n:dsimms%alink.net:*")
; ange-ftp-hook-function(file-directory-p "/po:pop.alink.net:110:apop:n:dsimms%alink.net:*")
; file-directory-p("po:pop.alink.net:110:apop:n:dsimms%alink.net:*")
; #[(file) "À !ƒ\n
; mapcar(#[(file) "À !ƒ\n
; nnmail-get-spool-files(nil)
; nnmail-get-new-mail(nnmh nil "~/Mail/" nil)
; nnmh-request-scan(nil "")
; gnus-request-scan(nil (nnmh ""))
; gnus-read-active-file()
; gnus-group-get-new-news(nil)
;* call-interactively(gnus-group-get-new-news)
Like I said, I have no real idea why file-directory-p is hooked
differently by ange-ftp post-startup.
LMI> If you have the mail backend as a secondary server, `F' will
LMI> subscribe you to all new groups.
coolness. Well, hopefully I won't ever have to switch to gnus again,
y'know? :)
--
Daniel Simms "The best of all ways to lengthen our days
dsimms@dsimms.com is to steal a few hours from the night."
(415) 269-7891 -Thomas Moore
next prev parent reply other threads:[~1997-02-04 23:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1997-02-03 23:32 Daniel Simms
1997-02-04 19:41 ` Lars Magne Ingebrigtsen
1997-02-04 23:00 ` Daniel Simms [this message]
1997-02-04 23:13 ` Lars Magne Ingebrigtsen
1997-02-04 23:55 ` Daniel Simms
1997-02-05 1:41 ` Lars Magne Ingebrigtsen
1997-02-05 5:03 ` Paul Franklin
1997-02-05 9:01 ` Daniel Simms
1997-02-05 3:08 ` Rich Pieri
1997-02-05 8:35 ` Daniel Simms
1997-02-05 16:13 ` Rich Pieri
1997-02-05 4:50 ` Paul Franklin
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=x56808uqga.fsf@ba.alink.net \
--to=dsimms@dsimms.com \
--cc=ding@ifi.uio.no \
/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).