all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: tino.calancha@gmail.com, 24518@debbugs.gnu.org
Subject: bug#24518: 25.2.50; dired-mark-extension with prefix arg fails
Date: Sat, 24 Sep 2016 16:51:31 +0300	[thread overview]
Message-ID: <83y42hbe3g.fsf@gnu.org> (raw)
In-Reply-To: <874m554ey2.fsf@linux-m68k.org> (message from Andreas Schwab on Sat, 24 Sep 2016 15:15:01 +0200)

> From: Andreas Schwab <schwab@linux-m68k.org>
> Cc: Tino Calancha <tino.calancha@gmail.com>,  24518@debbugs.gnu.org
> Date: Sat, 24 Sep 2016 15:15:01 +0200
> 
> Does it actually make sense to have to specify the character by its
> code?

Like I said: it looks a kludge, but it definitely isn't an accident.
I suggested to replace 'P' with 'c' in the interactive spec, to make
it less kludgey.

> That doesn't look like this was an intented feature (being
> undocumented).

It's documented, see the doc string.





  reply	other threads:[~2016-09-24 13:51 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-23 14:13 bug#24518: 25.2.50; dired-mark-extension with prefix arg fails Tino Calancha
2016-09-24 11:52 ` Eli Zaretskii
2016-09-24 12:30   ` Tino Calancha
2016-09-24 12:53     ` Eli Zaretskii
2016-09-24 13:02       ` Tino Calancha
2016-09-24 13:49         ` Eli Zaretskii
2016-09-24 13:15       ` Andreas Schwab
2016-09-24 13:51         ` Eli Zaretskii [this message]
2016-09-24 14:06           ` Tino Calancha
2016-09-24 15:11             ` Eli Zaretskii
2016-09-24 16:48           ` Andreas Schwab
2016-09-24 16:58             ` Eli Zaretskii
2016-09-24 17:14               ` Tino Calancha
2016-09-24 17:39                 ` Eli Zaretskii
2016-09-24 17:49                   ` Tino Calancha
2016-09-24 19:23                   ` Andreas Schwab
2016-09-24 19:13               ` Andreas Schwab
2016-09-24 19:29                 ` Eli Zaretskii
2016-09-24 19:41                   ` Andreas Schwab
2016-09-25 18:34                     ` John Wiegley

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=83y42hbe3g.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24518@debbugs.gnu.org \
    --cc=schwab@linux-m68k.org \
    --cc=tino.calancha@gmail.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 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.