unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Unknown <unknown@unknown.invalid>
To: help-gnu-emacs@gnu.org
Subject: Re: EMACS Problem: File exists but cannot be read
Date: Mon, 24 Sep 2007 11:15:21 +0200	[thread overview]
Message-ID: <fd7o8f$6qu$00$1@news.t-online.com> (raw)
In-Reply-To: <mailman.1199.1190583737.18990.help-gnu-emacs@gnu.org>

Peter Dyballa wrote:

> Probably this is not an ETCH problem – the same happens to me when I try 
> to read some other user's files I am not allowed to (UNIX file 
> permissions set to 640 or -rw-r-----). This also works when the 
> directory with the file is 'read protected' (UNIX file permissions set 
> to 751 or drwxr-x--x – I can search and even cd, but not read).

Of cause, it is'nt an Etch problem, but this problem comes with an 
Upgrade to Etch from Suse 9.0.

But: It isn't a problem of the file system permission.
1. the file systems owner/user/chmod are correct.
2. this problem occurs only sometimes.

If I open the the file again and again, after two to 5 times it works, 
but then I have to check, if the complete(!) file is read, cause, 
sometimes not the whole file will be read, only the half or more 
without any notice.

The complete problem disappears, if I start a new emacs an read the 
desired file.

This only happens while reading the files with the ftp client in emacs.

Thanks...

Best regards
Anne

  parent reply	other threads:[~2007-09-24  9:15 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 [this message]
2007-09-24 11:20       ` Peter Dyballa
     [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='fd7o8f$6qu$00$1@news.t-online.com' \
    --to=unknown@unknown.invalid \
    --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).