From: "Drew Adams" <drew.adams@oracle.com>
To: "'Chong Yidong'" <cyd@gnu.org>
Cc: 9361@debbugs.gnu.org
Subject: bug#9361: 24.0.50; default value of `dired-do-chmod'
Date: Fri, 27 Jan 2012 07:42:52 -0800 [thread overview]
Message-ID: <E91786ACA2AA4D5AA44F99152FEAFA46@us.oracle.com> (raw)
In-Reply-To: <87obtpd2uv.fsf@gnu.org>
> > This bug has not at all been fixed - AFAICT, everything I
> > reported is still a problem. It should not have been closed.
> > You apparently fixed your own choice of a problem, which
> > was not the problem that was reported.
> >
> > The default value of `dired-do-chmod' is still the same,
> > inappropriate value. There is no reason to pick up the
> > permissions from the _first_ of the marked files - makes
> > no sense at all. And it is still not made clear to users
> > which file the permissions are being copied from. Please
> > read the bug report, and the followup passage cited below.
>
> Your suggestion in the original post was
>
> >> The best approach is not to provide any default value here.
You read what you want to read, apparently. Which part of the above text about
our currently having an unclear, inappropriate default value did you not
understand?
Nothing has changed wrt the default value, except the treatment of empty input.
> As Juri noted, if you don't want the suggested value, just don't type
> M-n. Since this command no longer accepts empty input as a
> permission, there is nothing else to fix.
See above - there is plenty to fix. We should either provide no default value
or provide one that makes sense. That's the bug that was reported.
I made pretty clear what the problem was, even quoting the description more than
once. Here goes again:
>>> The point is that if we are going to copy settings from a
>>> particular file in order to make them available for,
>>> essentially, pasting operations to other files, then the
>>> target file being copied from should be clear. The copy
>>> operation should be an explicit user choice, not something
>>> implicit, based only on the first marked file (why not the
>>> last? or the 23rd?).
> > Do I need to open a new bug and copy the 9361 report to it,
> > i.e., to start over?
Apparently so. #10624
prev parent reply other threads:[~2012-01-27 15:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-24 16:10 bug#9361: 24.0.50; default value of `dired-do-chmod' Drew Adams
2011-08-24 18:45 ` Juri Linkov
2011-09-11 2:23 ` Lars Magne Ingebrigtsen
2011-09-11 15:00 ` Drew Adams
2011-09-11 21:41 ` Chong Yidong
2011-09-12 11:49 ` Juri Linkov
2011-09-12 20:47 ` Chong Yidong
2011-09-14 11:20 ` Juri Linkov
2011-09-14 15:07 ` Chong Yidong
2011-09-14 15:54 ` Juri Linkov
2011-09-12 11:39 ` Juri Linkov
2011-09-12 14:45 ` Drew Adams
2012-01-26 16:27 ` Drew Adams
2012-01-27 1:38 ` Juri Linkov
2012-01-27 3:04 ` Drew Adams
2012-01-27 7:24 ` Chong Yidong
2012-01-27 12:09 ` Juri Linkov
2012-01-27 16:58 ` Drew Adams
2012-01-27 15:42 ` Drew Adams [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=E91786ACA2AA4D5AA44F99152FEAFA46@us.oracle.com \
--to=drew.adams@oracle.com \
--cc=9361@debbugs.gnu.org \
--cc=cyd@gnu.org \
/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.