unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Albinus <michael.albinus@gmx.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: emacs-devel@gnu.org
Subject: Re: master 9d626df: Add 'nofollow' flag to set-file-modes etc.
Date: Tue, 25 Feb 2020 10:15:56 +0100	[thread overview]
Message-ID: <87k14bni2b.fsf@detlef.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <f35c0721-4b15-36f0-d53f-5b872b5f5729@cs.ucla.edu> (Paul Eggert's message of "Mon, 24 Feb 2020 16:25:51 -0800")

Paul Eggert <eggert@cs.ucla.edu> writes:

Hi Paul,

>> But what shall I do if the target system runs GNU/Linux? chmod(1)
>> does not offer any comparable argument. Shall I simply ignore
>> nofollow there?
>
> How about something like this?
>
> if (chmod -h works); then
>   chmod -h MODE FILE
> elif (test -h works); then
>   test -h FILE && chmod MODE FILE
> else
>   chmod MODE FILE
> fi

Hmm. In the Elisp manual, you have added to `set-file-modes':

--8<---------------cut here---------------start------------->8---
On platforms that do not support changing mode bits on a symbolic link,
this function signals an error when FILENAME is a symbolic link and FLAG
is ‘nofollow’.
--8<---------------cut here---------------end--------------->8---

Shouldn't Tramp behave similar, and raise an error if "chmod -h" or
something similar does not work? "Equal rights for all" :-)

Best regards, Michael.



  reply	other threads:[~2020-02-25  9:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20200224004617.19362.5846@vcs0.savannah.gnu.org>
     [not found] ` <20200224004619.58020206ED@vcs0.savannah.gnu.org>
2020-02-24 13:52   ` master 9d626df: Add 'nofollow' flag to set-file-modes etc Michael Albinus
2020-02-25  0:25     ` Paul Eggert
2020-02-25  9:15       ` Michael Albinus [this message]
2020-02-25 23:02         ` Paul Eggert
2020-02-26  0:29           ` Michael Albinus
2020-02-25  9:23       ` 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=87k14bni2b.fsf@detlef.i-did-not-set--mail-host-address--so-tickle-me \
    --to=michael.albinus@gmx.de \
    --cc=eggert@cs.ucla.edu \
    --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).