unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Andreas Röhler" <andreas.roehler@online.de>
To: emacs-devel@gnu.org
Subject: Re: ¬ notation for not? Ref: Add a couple cells to lisp-prettify-symbols-alist
Date: Sun, 10 Jul 2016 15:31:56 +0200	[thread overview]
Message-ID: <52190d8b-e3b2-55cd-f8ef-eba847bba707@online.de> (raw)
In-Reply-To: <20160710054725.GA29331@holos.localdomain>

Hi Mark,

while your initiative is appreciated, AFAIK these symbols are not that 
canonic.

Implementing in core might draw subsequent requests suggesting the one 
or the other symbols instead, IMO keeping the pretty-print stuff in 
specialized packages is recommendable.

Cheers,

Andreas

On 10.07.2016 07:47, Mark Oteiza wrote:
> On 10/07/16 at 01:24am, Mark Oteiza wrote:
>> One thing I just thought
>> of is making a mode's foo-prettify-symbols-alist a defcustom--perhaps
>> that will be nicer.
> Not pretty, but an example:
>
>    (defcustom my-prettify-symbols-alist
>      '(("lambda" . ?λ)
>        ("sqrt" . ?√)
>        ("not" . ?¬)
>        ("*" . ?×)
>        ("/" . ?÷))
>      "foobar"
>      :group 'prettify-symbols
>      :type '(alist :key-type string :value-type character)
>      :options '("and" "or" "/="
>                 ("<=" (const :tag "≤" ?≤))
>                 (">=" (const :tag "≥" ?≥))))
>




  reply	other threads:[~2016-07-10 13:31 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 [this message]
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             ` ¬ 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

  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=52190d8b-e3b2-55cd-f8ef-eba847bba707@online.de \
    --to=andreas.roehler@online.de \
    --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).