all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Kaushal Modi <kaushal.modi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25075@debbugs.gnu.org
Subject: bug#25075: 26.0.50; [PATCH] Dired can now dereference symlinks when copying
Date: Wed, 30 Nov 2016 18:42:02 +0000	[thread overview]
Message-ID: <CAFyQvY0AqS1o4dYO2vHTYrDF0Z-a6owv9MNUGeZrsFeTHYuzmg@mail.gmail.com> (raw)
In-Reply-To: <83shq8q0cg.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 867 bytes --]

Hi Eli,

Thanks, I will work on that next and submit an updated patch. My first
patch was just so that it gets reviewed for functionality.

On Wed, Nov 30, 2016, 1:39 PM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Kaushal Modi <kaushal.modi@gmail.com>
> > Date: Wed, 30 Nov 2016 18:04:17 +0000
> >
> > Can you review and comment on the below patch. I came up with a necessity
> > to copy symlinks from one dired buffer to another dired buffer as a
> > dereferenced copy of that symlink.
> >
> > In terminal, I would use the -L option of the cp command to do the same.
> >
> > The current default behavior is unchanged as the new defcustom
> > dired-copy-dereference is set to nil.
>
> Shouldn't the doc string of dired-do-copy be updated with a reference
> to the new variable?
>
> Likewise the Emacs User manual should be updated.
>
> Thanks.
>
-- 

Kaushal Modi

[-- Attachment #2: Type: text/html, Size: 1723 bytes --]

  reply	other threads:[~2016-11-30 18:42 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 [this message]
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

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=CAFyQvY0AqS1o4dYO2vHTYrDF0Z-a6owv9MNUGeZrsFeTHYuzmg@mail.gmail.com \
    --to=kaushal.modi@gmail.com \
    --cc=25075@debbugs.gnu.org \
    --cc=eliz@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.