From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Change in backup-buffer: how to interpret?
Date: Wed, 01 Jan 2003 11:46:29 -0500 [thread overview]
Message-ID: <E18Tm0j-0002sQ-00@fencepost.gnu.org> (raw)
In-Reply-To: <84znqnqldy.fsf@lucy.cs.uni-dortmund.de> (kai.grossjohann@uni-duisburg.de)
I think that file-modes can return nil. (Ange-FTP always returns
nil.) Then the logand will fail.
So is it a bug in the current code (which should deal with a nil
return value of file-modes), or is it a bug in Ange-FTP (which
returns nil)?
It's a bug in my change. Thanks for reporting it--I will fix it.
prev parent reply other threads:[~2003-01-01 16:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-30 20:53 Change in backup-buffer: how to interpret? Kai Großjohann
2002-12-30 20:58 ` Kai Großjohann
2003-01-01 16:46 ` Richard Stallman [this message]
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=E18Tm0j-0002sQ-00@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).