From: Eli Zaretskii <eliz@gnu.org>
To: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
Cc: 35287@debbugs.gnu.org, juri@linkov.net
Subject: bug#35287: dired-do-copy English beef-up
Date: Fri, 19 Apr 2019 18:03:42 +0300 [thread overview]
Message-ID: <835zraca0h.fsf@gnu.org> (raw)
In-Reply-To: <87pnpiumvj.8.fsf@jidanni.org>
> From: 積丹尼 Dan Jacobson
> <jidanni@jidanni.org>
> Date: Fri, 19 Apr 2019 21:48:32 +0800
> Cc: 35287@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
>
> Error messages like
> Copy ‘/tmp/.X0-lock’ to ‘/.X0-lock’ failed:
> (file-error Opening output file Permission denied /.X0-lock)
> I guess were too short to trigger the "?" perhaps,
> but anyway, by the time the user types the next SPC any hint of an error
> is swept away. Just like I suppose the "type '?' to see more" note would
> be.
>
> One might say "well on the shell command line if you don't look up to see
> the cp error messages, it is your own fault too."
>
> But at least they will still be sitting on the screen when you finally
> look up.
They are in *Messages*, aren't they? Clicking the mouse on the echo
area displays them.
next prev parent reply other threads:[~2019-04-19 15:03 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
2019-04-19 13:48 ` 積丹尼 Dan Jacobson
2019-04-19 14:28 ` Drew Adams
2019-04-19 15:03 ` Eli Zaretskii [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=835zraca0h.fsf@gnu.org \
--to=eliz@gnu.org \
--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 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.