all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 25075@debbugs.gnu.org, Kaushal Modi <kaushal.modi@gmail.com>
Subject: bug#25075: 26.0.50; [PATCH] Dired can now dereference symlinks when copying
Date: Tue, 25 Jun 2019 01:17:51 +0200	[thread overview]
Message-ID: <m31rziinds.fsf@gnus.org> (raw)
In-Reply-To: <k0fum8a3fk.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 30 Nov 2016 19:38:55 -0500")

Glenn Morris <rgm@gnu.org> writes:

> Kaushal Modi wrote:
>
>> +(defcustom dired-copy-dereference nil
>> +  "If non-nil, Dired dereferences symlinks when copying them.
>
> I can't imagine anyone needing this as an option they can set for all
> future uses. Surely what someone might need is a way to make one
> specific copy command dereference? As a prefix argument or a separate
> command, or whatever.

Yeah, I'm not very enthusiastic about that option, either.  Sometimes I
want to copy symlinks, and sometimes I want to dereference them, but
setting a variable first isn't very good user experience.

I do agree with Kaushal's assessment that the single-key keymap in dired
is pretty crowded...  but perhaps introduce a new multi-key keymap?  :-/

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      parent reply	other threads:[~2019-06-24 23:17 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-30 18:04 bug#25075: 26.0.50; [PATCH] Dired can now dereference symlinks when copying Kaushal Modi
2016-11-30 18:38 ` Eli Zaretskii
2016-11-30 18:42   ` Kaushal Modi
2016-12-01  0:38 ` Glenn Morris
2016-12-01  3:39   ` Eli Zaretskii
2016-12-01  4:12   ` Kaushal Modi
2016-12-01  6:06     ` Kaushal Modi
2020-08-11 13:17       ` Lars Ingebrigtsen
2019-06-24 23:17   ` Lars Ingebrigtsen [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m31rziinds.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=25075@debbugs.gnu.org \
    --cc=kaushal.modi@gmail.com \
    --cc=rgm@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.