From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Noam Postavsky <npostavs@gmail.com>
Cc: schwab@linux-m68k.org, 31376@debbugs.gnu.org, eller.helmut@gmail.com
Subject: bug#31376: 26.0.50; print-charset-text-property not honored
Date: Fri, 11 May 2018 12:58:11 -0700 (PDT) [thread overview]
Message-ID: <ac16b502-73c4-4066-8245-4c29cc3ef35f@default> (raw)
In-Reply-To: <<837eoani9b.fsf@gnu.org>>
> We should also mention in the doc
> string that any non-nil, non-t value is treated as 'default'.
That doesn't sound great - not very conventional.
Instead of `t' meaning something special and other
non-nil meaning something non-special we usually
have a mnemonic symbol for the special case and
other non-nil for the non-special case.
It's no doubt too late to change this, since the
mistake seems to have been made way back in Emacs 23.
The doc should even point out that this is maybe not
what you might expect. IOW, stress that `t' is a
special case.
next prev parent reply other threads:[~2018-05-11 19:58 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 6:48 bug#31376: 26.0.50; print-charset-text-property not honored Helmut Eller
2018-05-07 7:58 ` Andreas Schwab
2018-05-07 8:38 ` Helmut Eller
2018-05-07 12:57 ` Noam Postavsky
2018-05-07 18:08 ` Helmut Eller
2018-05-11 13:31 ` Eli Zaretskii
2018-05-11 17:44 ` Noam Postavsky
2018-05-11 18:45 ` Eli Zaretskii
2018-05-12 20:02 ` Noam Postavsky
2018-05-13 15:29 ` Eli Zaretskii
2018-05-13 18:29 ` Noam Postavsky
2018-05-13 18:51 ` Eli Zaretskii
2018-05-13 19:42 ` Noam Postavsky
2018-05-14 16:34 ` Eli Zaretskii
2018-05-14 23:15 ` Noam Postavsky
2018-05-15 17:19 ` Eli Zaretskii
2018-05-15 23:37 ` Noam Postavsky
2018-05-23 23:12 ` Noam Postavsky
[not found] ` <<837eoani9b.fsf@gnu.org>
2018-05-11 19:58 ` Drew Adams [this message]
2018-05-12 6:10 ` Eli Zaretskii
[not found] <<m2zi1c6jvo.fsf@caladan>
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=ac16b502-73c4-4066-8245-4c29cc3ef35f@default \
--to=drew.adams@oracle.com \
--cc=31376@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=eller.helmut@gmail.com \
--cc=npostavs@gmail.com \
--cc=schwab@linux-m68k.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.