From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Making a non-ASCII space character visible
Date: Sun, 17 Jun 2018 08:24:57 +0200 [thread overview]
Message-ID: <87efh6rkue.fsf@web.de> (raw)
In-Reply-To: <83o9gax8hi.fsf@gnu.org> (Eli Zaretskii's message of "Sun, 17 Jun 2018 08:55:21 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> > Seems you tried to insert a printed representation of the character?
> > AFAIK you must insert the character. You can achieve this with M-:
> > (insert ?\x2007) for example. Yes, that's not so nice.
>
> ??? How does that differ from "C-x 8 RET 2007 RET"? The latter is the
> standard way of inserting characters in Emacs.
Sure. With "not so nice" I meant "not so nice that it doesn't just
accept read syntaxes of characters.
> If you did succeed to customize that variable, can you show a step by
> step recipe?
I was wrong, we have a bug here.
The custom interface doesn't even accept the unmodified default value
(just make a change, undo, and try to "Set for current session"). It
seems it has a problem with the value field containing the newline
character - that seems to be read as empty string, and that later fails
the validation test.
Michael.
next prev parent reply other threads:[~2018-06-17 6:24 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-16 20:15 Making a non-ASCII space character visible Will Parsons
2018-06-16 21:37 ` Will Parsons
2018-06-17 4:31 ` Marcin Borkowski
2018-06-17 5:07 ` Michael Heerdegen
2018-06-17 5:55 ` Eli Zaretskii
2018-06-17 6:24 ` Michael Heerdegen [this message]
2018-06-17 6:41 ` Eli Zaretskii
2018-06-17 6:41 ` Michael Heerdegen
[not found] ` <mailman.2115.1529217694.1292.help-gnu-emacs@gnu.org>
2018-06-19 0:45 ` Will Parsons
2018-06-19 1:01 ` Noam Postavsky
[not found] ` <mailman.2220.1529370113.1292.help-gnu-emacs@gnu.org>
2018-06-19 1:26 ` Will Parsons
[not found] ` <mailman.2110.1529214934.1292.help-gnu-emacs@gnu.org>
2018-06-17 18:54 ` Will Parsons
2018-06-17 6:00 ` Eli Zaretskii
[not found] ` <mailman.2111.1529215267.1292.help-gnu-emacs@gnu.org>
2018-06-17 18:38 ` Will Parsons
2018-06-17 18:51 ` Eli Zaretskii
[not found] ` <mailman.2145.1529261474.1292.help-gnu-emacs@gnu.org>
2018-06-17 19:09 ` Will Parsons
2018-06-17 19:31 ` Eli Zaretskii
[not found] ` <mailman.2147.1529263896.1292.help-gnu-emacs@gnu.org>
2018-06-17 20:28 ` Will Parsons
2018-06-18 1:40 ` Nick Helm
[not found] ` <mailman.2154.1529286048.1292.help-gnu-emacs@gnu.org>
2018-06-19 0:12 ` Will Parsons
2018-06-19 2:30 ` Nick Helm
[not found] ` <mailman.2227.1529375463.1292.help-gnu-emacs@gnu.org>
2018-06-20 21:05 ` Will Parsons
[not found] ` <mailman.2107.1529212061.1292.help-gnu-emacs@gnu.org>
2018-06-17 18:45 ` Will Parsons
[not found] <<fol9fvF7uauU1@mid.individual.net>
[not found] ` <<fole90F986vU1@mid.individual.net>
2018-06-17 0:20 ` Drew Adams
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=87efh6rkue.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=eliz@gnu.org \
--cc=help-gnu-emacs@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.
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).