unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Pankaj Jangid <pankaj@codeisgreat.org>,
	"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: RE: [External] : Re: Dired C idea
Date: Wed, 4 Aug 2021 14:31:21 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488B70B48F3094D54F7A096F3F19@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <m2eeb97is9.fsf@codeisgreat.org>

 
> > As an ignoramus in this area, this reaffirms my guess
> > that we should offer both, and `C' in Dired should be
> > kept for ordinary copy, with possibly a new Dired key
> > being given to rsync.
> 
> Or may be that we provide just a new function, similar to the case of
> (list-buffers). Now people have a choice to re-bind ‘C-x C-b’ to
> (ibuffer) family of functions.

Yes, that would be my (ignorant) preference, as
I think I mentioned in the beginning.  But _if_
it's decided to give the new command a key binding
right away, I'm suggesting that it not take over
`C' from `dired-do-copy' as a default binding.


  reply	other threads:[~2021-08-04 14:31 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-31  1:34 Dired C idea Richard Stallman
2021-07-31  2:29 ` Alexandre Garreau
2021-07-31  3:35 ` Tim Cross
2021-07-31  6:23   ` Eli Zaretskii
2021-07-31 16:03     ` Arthur Miller
2021-07-31 16:07       ` Eli Zaretskii
2021-07-31 17:03         ` Arthur Miller
2021-07-31 20:56   ` [External] : " Drew Adams
2021-08-02  1:08     ` Richard Stallman
2021-08-02  1:37       ` Drew Adams
2021-08-05 14:12         ` Richard Stallman
2021-08-05 14:56           ` Drew Adams
2021-08-05 19:43           ` Fabrice Bauzac-Stehly
2021-08-07  3:04             ` Richard Stallman
2021-08-07  8:56               ` Fabrice Bauzac-Stehly
2021-08-08  7:08                 ` Fabrice Bauzac-Stehly
2021-08-09  2:26                 ` Richard Stallman
2021-08-10 19:49                   ` Fabrice Bauzac-Stehly
2021-07-31 13:35 ` Michael Albinus
2021-08-01  0:47   ` Richard Stallman
2021-08-01  7:48     ` Michael Albinus
2021-08-02  1:10       ` Richard Stallman
2021-08-02  1:41         ` [External] : " Drew Adams
2021-08-02 15:58         ` Michael Albinus
2021-08-03 11:43           ` Michael Albinus
2021-08-03 20:31             ` Gregory Heytings
2021-08-03 21:02               ` [External] : " Drew Adams
2021-08-04  7:47                 ` Pankaj Jangid
2021-08-04 14:31                   ` Drew Adams [this message]
2021-08-03 21:34               ` Arthur Miller
2021-08-03 22:27                 ` Gregory Heytings
2021-08-03 22:56                   ` Stefan Monnier
2021-08-04  7:48                   ` Andreas Schwab
2021-08-04  8:44                   ` Arthur Miller
2021-08-03 21:30             ` Fabrice Bauzac-Stehly
2021-08-03 21:35               ` Eric Abrahamsen
2021-08-04  8:50                 ` Arthur Miller
2021-08-05 14:12             ` Richard Stallman

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=SJ0PR10MB5488B70B48F3094D54F7A096F3F19@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --cc=pankaj@codeisgreat.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).