From: Peter Dyballa <Peter_Dyballa@Web.DE>
To: emacs list <help-gnu-emacs@gnu.org>
Subject: Re: EMACS Problem: File exists but cannot be read
Date: Mon, 24 Sep 2007 13:20:45 +0200 [thread overview]
Message-ID: <E029B62F-CF1C-459A-8424-336210546AA5@Web.DE> (raw)
In-Reply-To: <fd7o8f$6qu$00$1@news.t-online.com>
Am 24.09.2007 um 11:15 schrieb Anne Kaeppes:
> This only happens while reading the files with the ftp client in
> emacs.
So it can be the FTP server, too!
Can you provide an FTP address of the file and also mention how you
try to access that file? What do you input to GNU Emacs? C-h f ... or
C-x d ... ? And these ... need to filled with text ...
--
Greetings
Pete (:
_ / __ - -
_/ \__/_/ - -
(´`) (´`) - -
`´ `´
next prev parent reply other threads:[~2007-09-24 11:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-07 23:59 EMACS Problem: File exists but cannot be read Unknown
2007-09-23 18:17 ` Unknown
2007-09-23 21:42 ` Peter Dyballa
[not found] ` <mailman.1199.1190583737.18990.help-gnu-emacs@gnu.org>
2007-09-24 9:15 ` Unknown
2007-09-24 11:20 ` Peter Dyballa [this message]
[not found] ` <mailman.1217.1190632859.18990.help-gnu-emacs@gnu.org>
2007-09-27 1:30 ` Unknown
2007-09-27 9:02 ` Peter Dyballa
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E029B62F-CF1C-459A-8424-336210546AA5@Web.DE \
--to=peter_dyballa@web.de \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).