unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: file-symlink-p for remote files?
Date: Wed, 09 Apr 2003 14:56:16 +0200	[thread overview]
Message-ID: <84k7e3rfrj.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: E1934rZ-000537-00@fencepost.gnu.org

Richard Stallman <rms@gnu.org> writes:

> file-symlink-p should return the exact link target.  (When the target
> is relative, file-symlink-p returns the relative name.)

I confess that I'm rather surprised by this decision.  It appears to
be inconsistent with another decision on make-symbolic-link that you
took some months ago.

It seems to me that the target of a symlink should either be
interpreted as a string by both functions, or it should be
interpreted as a filename by both functions.

So much for my opinion.  Some observations:

Previously, you decided that the target of the symlink (the first arg
FILENAME) should be interpreted as a filename for make-symbolic-link.

Another issue that might play a role is backward compatibility.  In
the past, Ange-FTP has interpreted the symlink target as a filename
in file-symlink-p.  Ange-FTP does not implement make-symbolic-link.


What do you think?
-- 
A preposition is not a good thing to end a sentence with.

  reply	other threads:[~2003-04-09 12:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-08 15:24 file-symlink-p for remote files? Kai Großjohann
2003-04-08 18:31 ` Stefan Monnier
2003-04-08 18:49   ` Kai Großjohann
2003-04-08 19:03     ` Stefan Monnier
2003-04-08 19:10       ` Kai Großjohann
2003-04-08 19:14         ` Stefan Monnier
2003-04-09  5:39     ` Richard Stallman
2003-04-09  1:58 ` Richard Stallman
2003-04-09 12:56   ` Kai Großjohann [this message]
2003-04-09 19:29     ` Kai Großjohann
2003-04-10  6:22     ` Richard Stallman
2003-04-09 19:57 ` Kai Großjohann
2003-04-10 22:47   ` Richard Stallman

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=84k7e3rfrj.fsf@lucy.is.informatik.uni-duisburg.de \
    --to=kai.grossjohann@gmx.net \
    /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).