unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
To: "'Juri Linkov'" <juri@jurta.org>
Cc: 10624@debbugs.gnu.org
Subject: bug#10624: Dired-marking all files in the region
Date: Fri, 23 Nov 2012 09:12:06 -0800	[thread overview]
Message-ID: <089809C342424A529E4FEAA49440F205@us.oracle.com> (raw)
In-Reply-To: <87ehjkg404.fsf@mail.jurta.org>

> > IOW, why change the behavior for Dired generally (i.e., 
> > including outside WDired mode), for a problem that you
> > found only inside WDired?
> 
> This problem is not WDired specific.

I have not seen a description of "this" problem, other than a description of a
problem for WDired.  Can you characterize "this problem" for Dired generally?

This is the only description I've seen, and it seems quite WDired-specific:

>> when the region is active before typing `C-c C-c'
>> in WDired it marks renamed files with the same marker,
   ^^^^^^^^^
>> because currently WDired uses `dired-add-entry'
           ^^^^^^^^^^^^^^^^
>> that calls `dired-mark'.

How is "this problem" manifested for Dired, other than for WDired?

And I don't understand this:

> It is better to opt-in this functionality by setting the
> `interactive' arg than to opt-out it in specific packages
> because this feature makes sense only for interactive use in Dired.

What is the argument as to why this makes sense only for interactive use in
Dired?  Or that it makes sense always for interactive use in Dired?

Sorry, but this is not yet clear to me.  Seems like maybe some steps are missing
from your argument.  They are no doubt obvious to you, but not yet to me.  Could
you please fill in the blanks a bit?  Again, excuse me for not grasping this
quickly.






  reply	other threads:[~2012-11-23 17:12 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-27 15:35 bug#10624: 24.0.92; default value of `dired-do-ch*' Drew Adams
2012-01-27 16:23 ` Drew Adams
2012-09-14 23:47   ` Juri Linkov
2012-09-15  0:37     ` Drew Adams
2012-09-15 22:50       ` Juri Linkov
2012-09-16  4:47         ` Drew Adams
2012-09-16 23:48           ` Juri Linkov
2012-09-17  0:39             ` Drew Adams
2012-09-18 23:22             ` Juri Linkov
2012-09-15 22:54       ` Juri Linkov
2012-09-16  4:47         ` Drew Adams
2012-09-16 23:45           ` bug#10624: Dired-marking all files in the region Juri Linkov
2012-11-22  9:49             ` Juri Linkov
2012-11-22 15:27               ` Drew Adams
2012-11-23  7:51                 ` Juri Linkov
2012-11-23 17:12                   ` Drew Adams [this message]
2012-11-25  9:16                     ` Juri Linkov
2012-11-25 15:49                       ` Drew Adams
2012-11-25 16:12                         ` Juri Linkov
2012-11-25 17:02                           ` Drew Adams
2012-11-22 15:40               ` Stefan Monnier
2012-11-23  7:59                 ` 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=089809C342424A529E4FEAA49440F205@us.oracle.com \
    --to=drew.adams@oracle.com \
    --cc=10624@debbugs.gnu.org \
    --cc=juri@jurta.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 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).