From: Ted Zlatanov <tzz@lifelogs.com>
To: emacs-devel@gnu.org
Subject: Re: ¬ notation for not? Ref: Add a couple cells to lisp-prettify-symbols-alist
Date: Mon, 11 Jul 2016 09:35:07 -0400 [thread overview]
Message-ID: <87r3b08fhw.fsf@lifelogs.com> (raw)
In-Reply-To: jwvshvhdxar.fsf-monnier+emacs@gnu.org
On Sun, 10 Jul 2016 17:05:04 -0400 Stefan Monnier <monnier@iro.umontreal.ca> wrote:
>> Perhaps doing it how calc manages its units would be satisfactory? The
>> short of it being that `math-standard-units' and user-defined
>> `math-additional-units' are used to build `math-units-table'. Though,
>> for units there isn't a need to blacklist, and it sounds like a good
>> option to have for prettify-symbols.
SM> Whether the customization specifies what to include or what to exclude,
SM> there is still the issue that specific mappings could be complex
SM> (currently it's only (STRING . CHAR), but it'll likely need to be
SM> extended at some point such that you can additionally specify some
SM> predicate to check that the mapping is valid in a given context, or even
SM> to dynamically decide which mapping to use depending on context).
SM> So the mappings themselves should probably be regarded as "code" rather
SM> than customization, and the customization interface should just let the
SM> user select which mappings to (de)activate.
How about tagging each mapping? (STRING CHAR TAG1 TAG2 ...)
Then the user could include or exclude by tag. It's free-form but I
think it would be hard to provide a good general interface to
include/exclude prettifications otherwise.
Ted
next prev parent reply other threads:[~2016-07-11 13:35 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 [this message]
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 ` ¬ notation for not? Ref: Add a couple cells to lisp-prettify-symbols-alist Drew Adams
2016-07-15 14:50 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r3b08fhw.fsf@lifelogs.com \
--to=tzz@lifelogs.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 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.