unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu>
Cc: monnier+gnu/emacs@rum.cs.yale.edu,
	Kai.Grossjohann@CS.Uni-Dortmund.DE, emacs-devel@gnu.org
Subject: Re: Tramp: how to handle make-symbolic-link?
Date: Wed, 26 Jun 2002 09:56:59 -0400	[thread overview]
Message-ID: <200206261357.g5QDv0X11882@rum.cs.yale.edu> (raw)
In-Reply-To: E17Mzna-0008SY-00@fencepost.gnu.org

>     > Assuming that symlinks in the remote file system can only point to
>     > that same remote file system, the former request is possible, and the
>     > latter should get an error because there is no way to make a link to
>     > the local machine's disk.
> 
>     make-symbolic-link should not prevent you from creating to a link
>     to a file that doesn't exist.  Especially since you can pretty much
>     never tell whether the file will ever exist or not.
> 
> I agree, but that is not the issue here.  Either way, it will be
> possible to make links to files that don't exist.  The issue is about
> links that would appear to point to another machine.  Symbolic links
> are interpreted by the OS, and it does not understand Emacs remote
> file names.  So a link can only point to a file on the same machine.
> 
> In Emacs, that link target is a remote file name.  It always points
> to a remote file.
> 
> It seems that the consistent scheme is that you specify the link target
> using a remote file on the same remote machine, and the mechanism
> to create the link deletes the remote prefix before really creating
> the link.

I was not arguing about the rewrite when the target is
/sameuser@samehost:/destina/tion an error because there is no way to make a link to
the local machine's disk".

I don't like the rewriting, but I can live with it.  OTOH, raising an
error just because Emacs thinks the operation doesn't make any sense
would just be wrong.  Especially since it's not trivial for elisp code
to transform "/destina/tion" into "/sameuser@samehost:/destina/tion".


	Stefan

  reply	other threads:[~2002-06-26 13:56 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-23 19:51 Tramp: how to handle make-symbolic-link? Kai Großjohann
2002-06-23 20:00 ` Stefan Monnier
2002-06-24 15:48   ` Kai Großjohann
2002-06-23 20:22 ` Kai Großjohann
2002-06-24 19:39 ` Richard Stallman
2002-06-24 20:12   ` Stefan Monnier
2002-06-25 23:32     ` Richard Stallman
2002-06-26 13:56       ` Stefan Monnier [this message]
2002-06-28 17:39         ` Richard Stallman
2002-06-26 14:46   ` Kai Großjohann
2002-07-08 18:20     ` Richard Stallman
2002-07-10 13:25       ` Kai Großjohann
2002-07-11 12:00         ` Richard Stallman
2002-07-11 16:41           ` Stefan Monnier
2002-07-12 17:37             ` Richard Stallman
2002-07-12 18:03               ` Stefan Monnier
2002-07-11 20:28           ` Kai Großjohann
2002-06-26 15:15   ` Andreas Schwab

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=200206261357.g5QDv0X11882@rum.cs.yale.edu \
    --to=monnier+gnu/emacs@rum.cs.yale.edu \
    --cc=Kai.Grossjohann@CS.Uni-Dortmund.DE \
    --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).