From: Drew Adams <drew.adams@oracle.com>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 35287@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#35287: dired-do-copy English beef-up
Date: Thu, 18 Apr 2019 21:33:34 -0700 (PDT) [thread overview]
Message-ID: <90ae63da-c112-4078-ab8c-653db60aed4e@default> (raw)
In-Reply-To: <87r29yeoh0.8.fsf@jidanni.org>
> DA> What about the current existing messages when
> DA> there are failures, telling you to use `?' to
> DA> see the details (the `dired-log' output)?
>
> You know even though the "?" works, but I never thought it is a good
> idea.
>
> The user is probably typing fast into a 1000 different windows and there
> probably will be a lot of extraneous characters sent by him first to the
> thing that is expecting the question mark, before he notices he is being
> asked something.
>
> So I would have the whole error message presented to him, with an 'Got
> that, Holmes? (type a full "yes" to acknowledge)' style showstopper,
> before letting him proceed, as failed copies are a serious matter.
The user is _not_ being asked anything. She can type
`?' if/when she wants, to see the details - or not.
The `dired-do-*' operations are synchronous. The user
cannot be typing fast into 1000 different windows while
it is working. When it is done the user gets a message
about the possibility of using `?' to see details. She
is not locked into any modal dialog - that message can
be ignored if she wants. If she doesn't notice the
message it's not a big deal - like any other `message'
call. The message is in `*Messages*' and it can be
acted on anytime - or not.
Consider that `dired-do-*' works for 1 or 2 files but
also for 1000 files. `dired-log' is important in
providing details, but it is not critical - there is
no reason to force the user to stop and pay attention
(e.g. requiring some acknowledgement that she's seen
the message).
An alternative could be to always pop up the log buffer
(unless it is empty). I think the existing behavior is
preferable, but that alternative could be an option.
I really don't think it's a big deal. The info in the
log is not critical. If it were then the dialog would
be handled differently.
next prev parent reply other threads:[~2019-04-19 4:33 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 11:49 bug#35287: dired-do-copy English beef-up 積丹尼 Dan Jacobson
2019-04-16 20:35 ` Juri Linkov
2019-04-16 21:57 ` Drew Adams
2019-04-17 19:04 ` 積丹尼 Dan Jacobson
2019-04-17 19:58 ` Juri Linkov
2019-04-17 22:53 ` Drew Adams
2019-04-18 10:28 ` 積丹尼 Dan Jacobson
2019-04-18 20:59 ` Juri Linkov
2019-04-18 21:10 ` Drew Adams
2019-04-19 2:08 ` 積丹尼 Dan Jacobson
2019-04-19 4:33 ` Drew Adams [this message]
2019-04-19 13:48 ` 積丹尼 Dan Jacobson
2019-04-19 14:28 ` Drew Adams
2019-04-19 15:03 ` Eli Zaretskii
2019-04-19 15:11 ` Drew Adams
2019-04-19 15:14 ` 積丹尼 Dan Jacobson
2019-04-24 20:15 ` Juri Linkov
2019-05-05 19:43 ` Juri Linkov
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=90ae63da-c112-4078-ab8c-653db60aed4e@default \
--to=drew.adams@oracle.com \
--cc=35287@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=juri@linkov.net \
/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).