all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Boruch Baum <boruch_baum@gmx.com>
Cc: 44023@debbugs.gnu.org
Subject: bug#44023: dired-allow-duplicate-buffers
Date: Sun, 08 Nov 2020 08:50:01 -0500	[thread overview]
Message-ID: <jwvv9eg55mg.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20201108095017.noh5qlvtn2r2ko6s@E15-2016.optimum.net> (Boruch Baum's message of "Sun, 8 Nov 2020 04:51:25 -0500")

>> 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.

That's the point I was asking: is it a user-preference, so the users
will either always want one or always want the other, or is it
a behavior that users will want in some cases and will not want in other
cases.  E.g. imagine users that use both "plain dired" sometimes and
diredc at other times: would they want to allow "duplicate dired" when
using "plain dired", or is it only desirable when used from diredc?

So maybe, the users should not even need to set the option a single time
and the behavior will simply depend on whether dired is invoked directly
or from diredc.

> Another way of saying 'more work that isn't really necessary at all'?

OK.  I'm not arguing either way, I was just raising the question because
my poor intuition got the impression that users might prefer not to set
any option at all and that the right behavior could be inferred
from context.


        Stefan






      reply	other threads:[~2020-11-08 13:50 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
2020-11-08 13:50         ` Stefan Monnier [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=jwvv9eg55mg.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=44023@debbugs.gnu.org \
    --cc=boruch_baum@gmx.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 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.