From: Kaushal Modi <kaushal.modi@gmail.com>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Duplicate bindings? Ref: Ibuffer: Mark buffers by content
Date: Tue, 05 Jul 2016 15:41:12 +0000 [thread overview]
Message-ID: <CAFyQvY35BwTuz23XHCdMwRpwoP+jT35zLvvsqwcDtMk2XwUXpQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1607060009020.2580@calancha-pc>
[-- Attachment #1: Type: text/plain, Size: 1052 bytes --]
On Tue, Jul 5, 2016 at 11:31 AM Tino Calancha <tino.calancha@gmail.com>
wrote:
> If people agree to keep just one binding then i would suggest '%g'.
>
I appreciate the detailed reply. As I would be fine with either binding,
"%g" would work for me. As this is a new command being bound to a new
binding, I believe that should not be much resistance accepting that. But
let's see if people on this mailing list feel otherwise.
I also like the reasoning for using "%g".
> Unfortunatelly, this symmetry Dired-Ibuffer is not perfect:
there are Ibuffer commands with the Dired 'partner' having
a different binding. For instance:
`dired-mark-files-regexp' bound to '%m'
`ibuffer-mark-by-name-regexp' bound to '%n'.
If there are not many bindings that are inconsistent between the two, it
would be nice to sync up the bindings, deprecate the out-of-sync older
bindings, and then at some point in future, remove them. But while that's a
long process, using "%g" would at least get us getting the dired/ibuffer
bindings more in sync.
--
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 2632 bytes --]
next prev parent reply other threads:[~2016-07-05 15:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 15:03 Duplicate bindings? Ref: Ibuffer: Mark buffers by content Kaushal Modi
2016-07-05 15:31 ` Tino Calancha
2016-07-05 15:41 ` Kaushal Modi [this message]
2016-07-06 2:18 ` John Wiegley
2016-07-07 14:49 ` Kaushal Modi
2016-07-07 14:52 ` Tino Calancha
2016-07-07 15:19 ` Kaushal Modi
2016-07-05 16:36 ` Noam Postavsky
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=CAFyQvY35BwTuz23XHCdMwRpwoP+jT35zLvvsqwcDtMk2XwUXpQ@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=tino.calancha@gmail.com \
/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).