unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Glenn Morris <rgm@gnu.org>
Cc: 1817@emacsbugs.donarmstrong.com
Subject: bug#1817: 23.0.60; C-x RET c RET RET signals an error
Date: Wed, 07 Jan 2009 21:27:27 +0200	[thread overview]
Message-ID: <87ljtmncnl.fsf@jurta.org> (raw)
In-Reply-To: <oqfxjv0xcv.fsf@fencepost.gnu.org> (Glenn Morris's message of "Wed, 07 Jan 2009 13:44:48 -0500")

>> In response to the closed and archived bug#1205:
>
> You can unarchive it, as I did prior to this.

Thanks, I missed the `unarchive' command.

>>> +     (if (char-equal last-input-char ?\C-g)
>>> +     (keyboard-quit))
>>
>> I just noticed that this fix in `universal-coding-system-argument'
>> causes another bug.  It fails with the key sequence `C-x RET c RET RET'
>> that signals an error:
>>
>> Debugger entered--Lisp error: (wrong-type-argument characterp return)
>>   char-equal(return 7)
>
> It's suprising (to me) that last-input-char might not be a character,
> but just change `char-equal' to `equal'.

The variable name `last-input-char' is confusing.
It holds an input event, not just a character.
But as I see, its alias is `last-input-event'.
And (info "(elisp) Event Input Misc") says:

     The alias `last-input-char' exists for compatibility
     with Emacs version 18.

So I perhaps the doc string of `last-input-char' should say
that it is an alias for `last-input-event'?

-- 
Juri Linkov
http://www.jurta.org/emacs/






  reply	other threads:[~2009-01-07 19:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <0fskntb1h2.fsf@fencepost.gnu.org>
2009-01-07 17:54 ` bug#1817: 23.0.60; C-x RET c RET RET signals an error Juri Linkov
2009-01-07 18:44   ` Glenn Morris
2009-01-07 19:27     ` Juri Linkov [this message]
2009-01-07 20:00       ` Glenn Morris
2009-01-08 17:00         ` Stefan Monnier
2009-01-09  3:40   ` bug#1817: marked as done (last-input-char) Emacs bug Tracking System

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=87ljtmncnl.fsf@jurta.org \
    --to=juri@jurta.org \
    --cc=1817@emacsbugs.donarmstrong.com \
    --cc=rgm@gnu.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).