From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: schwab@suse.de, 32562@debbugs.gnu.org
Subject: bug#32562: 26; `read-char(-exclusive)' and `characterp'
Date: Mon, 10 Sep 2018 12:48:22 -0700 (PDT) [thread overview]
Message-ID: <4df2c3ce-9dcb-483c-b733-f91f54f33bce@default> (raw)
In-Reply-To: <<83k1ntnu6l.fsf@gnu.org>>
> > > A character with modifiers doesn't satisfy characterp, but it is still a
> > > character (which read-char can return).
> >
> > Yes, well, that's what I found a bit confusing wrt the
> > doc and function names. It wasn't (isn't?) too clear
> > just what we mean by "character", in that case.
>
> I made the documentation say "character event" where it matters.
I imagine that you made it clearer (I don't have the new doc).
But see what I replied to Andreas. It seems like we talk in some
places about reading a character even if what gets read might
not be `characterp'. "Character event" doesn't clarify that, for me.
Seems like the doc (but I don't have time now to search it)
doesn't distinguish "character" meaning something that is
`characterp' from other meanings of it (not sure what those
are, but apparently `read-char' can return such things).
It's not clear to me, at least. Why isn't `chararcterp' necessary
and sufficient for testing whether something is a character?
next prev parent reply other threads:[~2018-09-10 19:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<<3cce8b54-2e85-49a2-84d8-386ded864148@default>
[not found] ` <<<83d0tlpteu.fsf@gnu.org>
[not found] ` <<5f51bd06-84dd-47f5-a7da-b0c5814a274c@default>
[not found] ` <<83r2i1o3dr.fsf@gnu.org>
2018-09-10 14:57 ` bug#32562: 26; `read-char(-exclusive)' and `characterp' Drew Adams
[not found] ` <<mvmtvmxctnm.fsf@suse.de>
[not found] ` <<3d6fb22f-de5a-4cce-bf49-023f2fc8388f@default>
[not found] ` <<83k1ntnu6l.fsf@gnu.org>
2018-09-10 19:48 ` Drew Adams [this message]
2018-09-11 7:57 ` Eli Zaretskii
2018-09-11 15:30 ` Drew Adams
2018-09-11 17:07 ` Eli Zaretskii
[not found] ` <<<5f51bd06-84dd-47f5-a7da-b0c5814a274c@default>
[not found] ` <<<mvmtvmxctnm.fsf@suse.de>
[not found] ` <<<3d6fb22f-de5a-4cce-bf49-023f2fc8388f@default>
[not found] ` <<<83k1ntnu6l.fsf@gnu.org>
[not found] ` <<4df2c3ce-9dcb-483c-b733-f91f54f33bce@default>
[not found] ` <<831sa0o49d.fsf@gnu.org>
[not found] ` <<4d4aa5cd-964c-41c5-ae72-24769afb0bd0@default>
[not found] ` <<83in3cm08g.fsf@gnu.org>
2018-09-11 17:22 ` Drew Adams
2018-09-11 18:34 ` Eli Zaretskii
[not found] <<<<3cce8b54-2e85-49a2-84d8-386ded864148@default>
[not found] ` <<<<83d0tlpteu.fsf@gnu.org>
[not found] ` <<<<5f51bd06-84dd-47f5-a7da-b0c5814a274c@default>
[not found] ` <<<<mvmtvmxctnm.fsf@suse.de>
[not found] ` <<<<3d6fb22f-de5a-4cce-bf49-023f2fc8388f@default>
[not found] ` <<<<83k1ntnu6l.fsf@gnu.org>
[not found] ` <<<4df2c3ce-9dcb-483c-b733-f91f54f33bce@default>
[not found] ` <<<831sa0o49d.fsf@gnu.org>
[not found] ` <<<4d4aa5cd-964c-41c5-ae72-24769afb0bd0@default>
[not found] ` <<<83in3cm08g.fsf@gnu.org>
[not found] ` <<eedf9125-6ece-44cb-a01b-b8da3d707e8c@default>
[not found] ` <<83ftyfnarp.fsf@gnu.org>
2018-09-11 18:58 ` Drew Adams
2018-09-11 19:03 ` Eli Zaretskii
[not found] <<3cce8b54-2e85-49a2-84d8-386ded864148@default>
[not found] ` <<83d0tlpteu.fsf@gnu.org>
2018-09-10 13:43 ` Drew Adams
2018-09-10 14:04 ` Eli Zaretskii
2018-09-10 14:29 ` Andreas Schwab
2018-09-10 15:01 ` Drew Adams
2018-09-10 17:22 ` Eli Zaretskii
2018-08-28 20:39 Drew Adams
2018-08-28 20:51 ` Noam Postavsky
2018-08-28 21:24 ` Drew Adams
2018-08-28 22:27 ` Noam Postavsky
2018-09-10 10:01 ` Eli Zaretskii
2018-09-10 9:56 ` Eli Zaretskii
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=4df2c3ce-9dcb-483c-b733-f91f54f33bce@default \
--to=drew.adams@oracle.com \
--cc=32562@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=schwab@suse.de \
/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).