From: Boruch Baum <boruch_baum@gmx.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 44023@debbugs.gnu.org
Subject: bug#44023: dired-allow-duplicate-buffers
Date: Sun, 8 Nov 2020 04:51:25 -0500 [thread overview]
Message-ID: <20201108095017.noh5qlvtn2r2ko6s@E15-2016.optimum.net> (raw)
In-Reply-To: <jwvh7q2ftv2.fsf-monnier+emacs@gnu.org>
On 2020-11-06 09:29, Stefan Monnier wrote:
> >> E.g. I suspect that diredc wants/needs this feature, but it's not
> >> diredc's job to set user options, so for diredc it would probably make
> >> more sense to pass that as an argument.
> >> WDYT?
> >
> > I prefer the defcustom route because I like giving a user choices (it's
> > also more emacs-y).
>
> I don't see this as a question of "choice vs no-choice" but a question
> is: should this be decided globally over the whole Emacs session,
Yes, yes.
> or should it be decided one a case-by-case basis
If you mean buffer-by-buffer, no, no, no. Think of how tedious that
would be to need to manually set that for each navigation. Once a person
sets a preference, it should become the default until changed.
> > Less subjectively, adding an argument creates a mess
> > because the modified function is a generic internal function
>
> Which is why I then suggested a separate function/command (which will
> require a bit of refactoring to share the common code, of course, but
> that's an implementation detail).
Another way of saying 'more work that isn't really necessary at all'? If
you're asking to choose between: 1] a clean single line change and
boolean defcustom, and; 2] "a separate function/command (which will
require a bit of refactoring to share the common code, of course" ... uh
... I think I choose ... uh ... uh ...
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
next prev parent reply other threads:[~2020-11-08 9:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 19:22 bug#44023: dired-allow-duplicate-buffers Boruch Baum
2020-10-16 5:32 ` Lars Ingebrigtsen
2020-10-16 6:46 ` Boruch Baum
2020-10-16 16:25 ` Lars Ingebrigtsen
2020-10-18 5:45 ` Boruch Baum
2020-10-19 8:11 ` Lars Ingebrigtsen
2020-10-19 8:38 ` Boruch Baum
2020-11-05 15:38 ` Stefan Monnier
2020-11-05 16:06 ` Stefan Monnier
2020-11-06 10:01 ` Boruch Baum
2020-11-06 14:29 ` Stefan Monnier
2020-11-08 9:51 ` Boruch Baum [this message]
2020-11-08 13:50 ` Stefan Monnier
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=20201108095017.noh5qlvtn2r2ko6s@E15-2016.optimum.net \
--to=boruch_baum@gmx.com \
--cc=44023@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.