unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
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: Fri, 28 Jun 2002 11:39:37 -0600 (MDT)	[thread overview]
Message-ID: <200206281739.g5SHdbA04130@santafe.santafe.edu> (raw)
In-Reply-To: <200206261357.g5QDv0X11882@rum.cs.yale.edu> (monnier+gnu/emacs@rum.cs.yale.edu)

    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".

What is your complete proposal?

    Even Emacs uses symlink targets as non-files, for lock files.

Yes it does, and it never tries to open those.
This happens to work, but is not what symlinks are for.
The main purpose of symlinks is to refer to another file.
That is what defines their meaning.

  reply	other threads:[~2002-06-28 17:39 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
2002-06-28 17:39         ` Richard Stallman [this message]
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=200206281739.g5SHdbA04130@santafe.santafe.edu \
    --to=rms@gnu.org \
    --cc=Kai.Grossjohann@CS.Uni-Dortmund.DE \
    --cc=emacs-devel@gnu.org \
    --cc=monnier+gnu/emacs@rum.cs.yale.edu \
    /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).