From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Drew Adams <drew.adams@oracle.com>
Cc: 14925@debbugs.gnu.org
Subject: bug#14925: 24.3.50; `image-dired.el' code (minor)
Date: Thu, 25 Jul 2013 15:13:00 -0400 [thread overview]
Message-ID: <jwva9lao3p6.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <6a9c11fa-71ad-44f9-9771-35626a56ee01@default> (Drew Adams's message of "Sun, 21 Jul 2013 12:37:24 -0700 (PDT)")
> 1. `image-dired-dired-file-marked-p' uses regexp "^ .*$", which I think
> is the same as "^ " (which is simpler).
It's similar, except for (match-end 0) and the position of point after
re-search-forward. I haven't looked at the code to see if the
difference matters.
> I also wonder why it does not just use `dired-re-mark'.
No idea.
> 2. Commands that act on the marked files should perhaps follow the
> naming convention used in dired.el, dired-aux.el, and dired-x.el:
> `*-do-*'. Thus perhaps rename `image-dired-dired-comment-files',
> `image-dired-tag-files', `image-dired-delete-tag',
> `image-dired-display-thumbs', `image-dired-copy-with-exif-file-name',
> `image-dired-dired-edit-comment-and-tags', and
> `image-dired-create-thumbs'.
> The equivalent Dired command that acts on the current file only, when
> available, is named similarly, but without the `*-do-*' part.
> 3. Those commands do not treat parameter ARG the same way as do the
> Dired `*-do-*' commands. For the image-dired commands, ARG is
> essentially boolean (and should thus have a name that reflects that).
> Wouldn't it be better for it to be the `prefix-numeric-value' and let
> you act on the next ARG files? That would give users more flexibility
> and provide a more consistent UI. Is there a downside I am missing?
2 and 3 sound like good ideas.
Stefan
next prev parent reply other threads:[~2013-07-25 19:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-21 19:37 bug#14925: 24.3.50; `image-dired.el' code (minor) Drew Adams
2013-07-21 19:54 ` Drew Adams
2013-07-25 19:13 ` Stefan Monnier [this message]
2013-07-26 1:02 ` Drew Adams
2013-07-26 5:31 ` Drew Adams
2021-09-06 10:12 ` Lars Ingebrigtsen
2021-09-06 21:49 ` bug#14925: [External] : " Drew Adams
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=jwva9lao3p6.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=14925@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
/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).