From: Drew Adams <drew.adams@oracle.com>
To: emacs-devel@gnu.org
Subject: ¬ notation for not? Ref: Add a couple cells to lisp-prettify-symbols-alist
Date: Fri, 15 Jul 2016 09:14:13 -0700 (PDT) [thread overview]
Message-ID: <e13ac206-b7e0-47e8-9a75-21d581328c11@default> (raw)
In-Reply-To: <87zipjszm7.fsf_-_@lifelogs.com>
> DA> E.g., ensure that "¬" does not name a symbol that has a
> DA> function or variable value. If `¬' is already bound to some
> DA> function or variable then you probably do not want to alias
> DA> function `not' to it.
>
> That's not really related to my question about customizations,
Irrelevant.
This is a thread about showing "¬ notation for not?" (and similar),
a thread started by that question from Clément. My comment is about
one consideration for such a proposed feature.
My point is separate from _your_ question, but there is no reason
to fork discussion off my point off from Clément's proposed feature,
with which it is concerned. I restored the Subject line.
> and there is no aliasing going on in any case. The user will see ¬
> in both cases, but they will be different underneath.
Yes, of course. It is not aliasing of symbol values (function or
variable). It is, as you say, a "visual clobbering". Visual name
capture.
> DA> Emacs allows most characters in function and variable names.
> DA> Just because `prettify-symbols-alist' might have an entry for
> DA> a given string, that does not mean that the user wants to
> DA> clobber any existing function or variable that has that name.
>
> It's a visual clobbering, but yeah, I know what you mean. Typically
> users will not have such functions or variables, but it would be good to
> distinguish them in a way that makes their ephemeral nature clear. Right
> now they aren't.
There is nothing inherently ephemeral in the nature of such functions
or variables.
This is not limited to any particular function or variable (e.g. `not').
Any function or variable could appear in `lisp-prettify-symbols-alist',
and it could be associated with any prettifying string.
The possibility of a visual name capture needs to be considered before
this feature is rolled out.
next prev parent reply other threads:[~2016-07-15 16:14 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-10 4:44 ¬ notation for not? Ref: Add a couple cells to lisp-prettify-symbols-alist Kaushal Modi
2016-07-10 5:24 ` Mark Oteiza
2016-07-10 5:47 ` Mark Oteiza
2016-07-10 13:31 ` Andreas Röhler
2016-07-10 14:57 ` Eli Zaretskii
2016-07-10 14:35 ` Clément Pit--Claudel
2016-07-10 15:05 ` Stefan Monnier
2016-07-10 14:44 ` Stefan Monnier
2016-07-10 14:57 ` Clément Pit--Claudel
2016-07-10 15:04 ` Drew Adams
2016-07-10 15:20 ` Mark Oteiza
2016-07-10 21:05 ` Stefan Monnier
2016-07-11 13:35 ` Ted Zlatanov
2016-07-11 14:01 ` Stefan Monnier
2016-07-14 21:18 ` Clément Pit--Claudel
2016-07-14 21:32 ` John Wiegley
2016-07-14 22:31 ` Mark Oteiza
2016-07-14 22:36 ` Kaushal Modi
2016-07-15 0:20 ` Stefan Monnier
2016-07-15 14:12 ` Ted Zlatanov
2016-07-15 14:46 ` Drew Adams
2016-07-15 15:13 ` visual distinction for prettified symbols (was: ¬ notation for not? Ref: Add a couple cells to lisp-prettify-symbols-alist) Ted Zlatanov
2016-07-15 16:14 ` Drew Adams [this message]
2016-07-15 14:50 ` ¬ notation for not? Ref: Add a couple cells to lisp-prettify-symbols-alist Stefan Monnier
2016-07-15 15:03 ` Ted Zlatanov
2016-07-15 15:17 ` Stefan Monnier
2016-07-15 15:35 ` Ted Zlatanov
2016-07-17 18:31 ` Stefan Monnier
2016-07-18 14:12 ` Ted Zlatanov
2016-07-18 15:07 ` Stefan Monnier
2016-07-18 16:49 ` Ted Zlatanov
2016-07-15 15:26 ` Ted Zlatanov
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=e13ac206-b7e0-47e8-9a75-21d581328c11@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@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).