From: kai.grossjohann@uni-duisburg.de (Kai Großjohann)
Subject: Re: Wanted: Help isolating FTP problem
Date: Wed, 29 Jan 2003 20:52:02 +0100 [thread overview]
Message-ID: <84adhjybrx.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: XSUZ9.83621$Ve4.5998@sccrnsc03
"Siegfried Heintze" <siegfried@heintze.com> writes:
> When I position the cursor on the (DIRED display) www line and hit return, I
> expect it to give me a directory listing of the contents of that directory.
> It does not! Instead it says "no file on this line".
>
> If I use find file, that does not work either, it gets stuck on the www and
> says "no such directory". There is clearly a directory there with lots of
> stuff in it, though.
>
> Here is the display from DIRED:
> /xyz@www.decisionchannel.com:/:
> 01-28-03 03:07PM <DIR> cases
> 01-16-03 07:37PM <DIR> database
> 02-09-02 03:19PM <DIR> logs
> 11-05-02 11:51AM <DIR> MSFTPSVC15
> 10-11-02 03:18PM <DIR> www
This appear to be two completely separate problems. Hm. But maybe
you can kill two flies with one stroke¹ by frobbing the variables
ange-ftp-dumb-unix-host-regexp and/or ange-ftp-dumb-host-types.
The dired problem comes from the strange directory listing format.
Dired uses the variable dired-move-to-filename-regexp to find the
filename, and that expects the date to be right before the filename.
It's unclear to me where the find-file problem comes from. That
would have to be investigated further.
¹ I wonder what the English version of this idiom is?
dict.leo.org... Ah! To kill two birds with one stone. It seems
the English are somewhat more fond of bigger game :-)
--
Ambibibentists unite!
next prev parent reply other threads:[~2003-01-29 19:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 18:15 Wanted: Help isolating FTP problem Siegfried Heintze
2003-01-29 19:52 ` Kai Großjohann [this message]
2003-01-29 20:35 ` Benjamin Riefenstahl
2003-01-29 23:51 ` gebser
2003-01-30 5:06 ` Siegfried Heintze
2003-01-31 7:17 ` Siegfried Heintze
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=84adhjybrx.fsf@lucy.is.informatik.uni-duisburg.de \
--to=kai.grossjohann@uni-duisburg.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.