all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "14925@debbugs.gnu.org" <14925@debbugs.gnu.org>
Subject: bug#14925: [External] : Re: bug#14925: 24.3.50; `image-dired.el' code (minor)
Date: Mon, 6 Sep 2021 21:49:32 +0000	[thread overview]
Message-ID: <SJ0PR10MB548872C50F44EF3DF915B429F3D29@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87mtoqgghc.fsf@gnus.org>

> As for the other two points -- changing the names of all these dired
> commands -- I don't think the gain we get from more regular function
> names in this area outweighs the pain we'd inflict on users that may be
> using the old names.  So I'm closing this bug report.

Renaming and deprecation of the old names is the
right approach, IMO.  There's no reason that
something that's deprecated can't continue to be
supported forever, if you like.

Dired has very consistent command and argument
behaviors, especially when it comes to commands
that act on or are affected by marks.  It's a
pity to keep this wart - in the name of what
exactly?

It's trivial to make the renaming 100% painless
to all users of the old names - they'd just
continue to work, as long as you like. 

And what about changing the behavior of the ARG
argument?  Or if you don't change its behavior
to fit Dired, what about changing its name to
reflect what it does?





      reply	other threads:[~2021-09-06 21:49 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
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   ` 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=SJ0PR10MB548872C50F44EF3DF915B429F3D29@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=14925@debbugs.gnu.org \
    --cc=larsi@gnus.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.