unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: pietru@caramail.com
To: Gregory Heytings <gregory@heytings.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Prettify keywords
Date: Wed, 3 Feb 2021 22:42:35 +0100	[thread overview]
Message-ID: <trinity-d7d83478-2f70-4518-b0a3-8d01e68c2830-1612388555960@3c-app-mailcom-bs06> (raw)
In-Reply-To: <bc6326ff835eb735615f@heytings.org>

Equipped with this information my task would not be too difficult to
implement.  I thought of giving up on it.

Would it be possible to include the code in a minor mode that I am writing
for texinfo?  The minor mode is called crucible.  So I can have 

(defun pretty ()
  (push '("\\alpha" . ?α) prettify-symbols-alist)
  (push '("\\beta" . ?β) prettify-symbols-alist)
  (prettify-symbols-mode))

(add-hook 'texinfo-mode-hook #'pretty)




> Sent: Thursday, February 04, 2021 at 9:37 AM
> From: "Gregory Heytings" <gregory@heytings.org>
> To: pietru@caramail.com
> Cc: help-gnu-emacs@gnu.org
> Subject: Re: Prettify keywords
>
> 
> >
> > I can see a bit what you mean.  prettify-symbols-mode is then a minor 
> > mode that I can use with the texinfo major mode.  Correct me if I am 
> > wrong please.
> >
> 
> Yes, that's correct.  As you see in the code: "(define-minor-mode 
> prettify-symbols-mode ...".  It is a minor mode which, as any other minor 
> mode, you can use with any major mode.
>



  reply	other threads:[~2021-02-03 21:42 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-03 13:19 Prettify keywords pietru
2021-02-03 16:23 ` Stefan Monnier
2021-02-03 17:07   ` pietru
2021-02-03 17:40     ` Stefan Monnier
2021-02-03 17:45       ` pietru
2021-02-03 19:57         ` Stefan Monnier
2021-02-03 19:58           ` pietru
2021-02-03 20:27             ` Stefan Monnier
2021-02-03 20:36               ` pietru
2021-02-03 20:39                 ` Gregory Heytings
2021-02-03 20:56                   ` pietru
2021-02-03 21:13                     ` Gregory Heytings
2021-02-03 21:21                       ` pietru
2021-02-03 21:27                         ` Gregory Heytings
2021-02-03 21:31                           ` pietru
2021-02-03 21:37                             ` Gregory Heytings
2021-02-03 21:42                               ` pietru [this message]
2021-02-03 22:05                                 ` Gregory Heytings
2021-02-03 22:12                                   ` pietru
2021-02-03 22:16                               ` Stefan Monnier
2021-02-03 22:33                                 ` Gregory Heytings
2021-02-03 21:37                           ` pietru
2021-02-03 21:41                             ` Gregory Heytings
2021-02-03 21:48                               ` pietru
2021-02-03 22:26                               ` pietru
2021-02-03 21:26                       ` pietru
2021-02-03 22:11                 ` Stefan Monnier
2021-02-03 22:17                   ` pietru

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=trinity-d7d83478-2f70-4518-b0a3-8d01e68c2830-1612388555960@3c-app-mailcom-bs06 \
    --to=pietru@caramail.com \
    --cc=gregory@heytings.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).