unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: "Eli Zaretskii" <eliz@gnu.org>, "積丹尼 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 08:11:06 -0700 (PDT)	[thread overview]
Message-ID: <ba3e694b-6b01-41fd-971f-f84edecf7b6b@default> (raw)
In-Reply-To: <835zraca0h.fsf@gnu.org>

> They are in *Messages*, aren't they?  Clicking the mouse on the echo
> area displays them.

Maybe, maybe not.  If `dired-log*' isn't used anymore
for such errors then there won't be such messages.

But even if there are equivalent or similar messages,
without seeing the `dired-log' message you likely
won't know that they are there to find.

It seems that we lost the feature of invoking
`dired-log' for most `dired-do-creat-files' errors (?).





  reply	other threads:[~2019-04-19 15:11 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
2019-04-19 15:11                     ` Drew Adams [this message]
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=ba3e694b-6b01-41fd-971f-f84edecf7b6b@default \
    --to=drew.adams@oracle.com \
    --cc=35287@debbugs.gnu.org \
    --cc=eliz@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).