From: Kaushal Modi <kaushal.modi@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 22107@debbugs.gnu.org, monnier@iro.umontreal.ca,
Dmitry Gutov <dgutov@yandex.ru>
Subject: bug#22107: this-command-keys no longer returns prefix argument
Date: Fri, 13 May 2016 15:00:27 +0000 [thread overview]
Message-ID: <CAFyQvY0X4G2O6eSmhDN5yno9JUiwvffjCT+hOmdA9GMfWZV6-Q@mail.gmail.com> (raw)
In-Reply-To: <83mvnu82wb.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1321 bytes --]
On Fri, May 13, 2016 at 10:11 AM Eli Zaretskii <eliz@gnu.org> wrote:
> If this is a documentation bug, then it's not a documentation bug,
> because it means one of the two variables should be obsoleted.
>
I do not have enough experience with those functions enough to make a call
either way. I am simple trying to reach a closure for this issue. I just
recently stumbled upon this this-command-keys change between 24.5 and 25.x
versions. And I would like to have it fixed the correct way that the
consensus decides and at least have the documentation reflect the current
state of things.
> And I don't think the view that the current behavior is correct is
> shared by everyone.
>
> So I don't see how you can be so sure about this.
>
Looks like there's an unspoken consensus about how this-command-keys
behaves right now, and so this bug thread had been dead since Dec, until I
discovered this issue recently.
If this-single-command-keys has to be obsoleted, or if this-command-keys
has to be reverted, IMO this bug is a strong candidate to be able to delay
the 25.1 release (unlike what Dmitry thought of as a non important enough
blocking bug). So I had to speak up for this one in that emacs-devel thread.
I will willing to help in whatever way to help reach a good closure for
this bug.
--
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 1850 bytes --]
next prev parent reply other threads:[~2016-05-13 15:00 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-07 15:42 bug#22107: 25.1; Wrong docstring for this-single-command-keys Artur Malabarba
2015-12-07 18:10 ` Glenn Morris
2015-12-07 21:46 ` Artur Malabarba
2015-12-07 21:55 ` Glenn Morris
2015-12-07 22:10 ` Artur Malabarba
2015-12-08 1:20 ` Glenn Morris
2015-12-08 12:01 ` Artur Malabarba
2015-12-08 16:59 ` Eli Zaretskii
2015-12-09 3:28 ` Stefan Monnier
[not found] ` <83mvtkb882.fsf@gnu.org>
2015-12-09 4:53 ` Stefan Monnier
[not found] ` <83io47blbq.fsf@gnu.org>
2015-12-10 18:34 ` Stefan Monnier
2015-12-10 18:37 ` Stefan Monnier
2015-12-10 18:50 ` Eli Zaretskii
2015-12-11 4:17 ` Stefan Monnier
[not found] ` <83eget8gos.fsf@gnu.org>
2015-12-11 14:49 ` Stefan Monnier
[not found] ` <83poyd6m1b.fsf@gnu.org>
2015-12-12 3:57 ` Stefan Monnier
2015-12-12 4:28 ` Stefan Monnier
2015-12-12 7:55 ` Eli Zaretskii
2015-12-12 14:25 ` Stefan Monnier
2015-12-12 14:55 ` Eli Zaretskii
2015-12-12 23:34 ` John Wiegley
2015-12-13 4:16 ` Stefan Monnier
2015-12-13 10:12 ` Artur Malabarba
2015-12-13 15:37 ` Eli Zaretskii
2015-12-13 20:53 ` Artur Malabarba
2015-12-14 3:27 ` Eli Zaretskii
2015-12-14 13:52 ` Artur Malabarba
2015-12-13 15:53 ` Stefan Monnier
2015-12-13 17:25 ` Drew Adams
2015-12-13 20:15 ` Stefan Monnier
2020-09-07 15:26 ` Lars Ingebrigtsen
2020-10-07 4:10 ` Lars Ingebrigtsen
2015-12-10 18:49 ` Eli Zaretskii
2015-12-11 4:24 ` Stefan Monnier
[not found] ` <83bn9x8g12.fsf@gnu.org>
2015-12-11 14:47 ` Stefan Monnier
2015-12-11 4:17 ` Stefan Monnier
2015-12-11 13:10 ` Artur Malabarba
2015-12-11 14:44 ` Stefan Monnier
2015-12-11 15:39 ` Artur Malabarba
2015-12-12 4:06 ` Stefan Monnier
2016-05-11 13:33 ` bug#22107: this-command-keys no longer returns prefix argument Kaushal Modi
2016-05-11 14:02 ` Eli Zaretskii
2016-05-11 14:08 ` Kaushal Modi
2016-05-11 14:22 ` Stefan Monnier
2016-05-13 11:52 ` Kaushal Modi
2016-05-13 14:10 ` Eli Zaretskii
2016-05-13 15:00 ` Kaushal Modi [this message]
2016-05-11 14:18 ` Stefan Monnier
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=CAFyQvY0X4G2O6eSmhDN5yno9JUiwvffjCT+hOmdA9GMfWZV6-Q@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=22107@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=eliz@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).