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:48:21 +0100	[thread overview]
Message-ID: <trinity-79c7df3d-94f6-4ffe-8ac3-3c0c6d23931c-1612388901691@3c-app-mailcom-bs06> (raw)
In-Reply-To: <bc6326ff83c79a9f4dce@heytings.org>



> Sent: Thursday, February 04, 2021 at 9:41 AM
> From: "Gregory Heytings" <gregory@heytings.org>
> To: pietru@caramail.com
> Cc: help-gnu-emacs@gnu.org
> Subject: Re: Prettify keywords
>
>
> >
> > Have looked at prettify-symbols-mode and it is defined in prog-mode.el.
> > This gets me quite confused
> >
>
> I understand, but it shouldn't confuse you.  It happens to be defined in
> the file prog-mode.el, but it is nonetheless independent from prog-mode.
>
> >
> > as I thought that I can only activate a single major mode at a time on a
> > particular buffer.
> >
>
> That's correct indeed.

But as you have said, one can define an independent minor mode that can
still be defined within an elisp file implementing a minor mode.

My original problem started when I decided to integrate the functionalities
in plain-tex-mode (in tex-mode.el) within texinfo-mode.  Did not realise
the minor mode prettify-mode existed, that is separate from tex-mode.el.




  reply	other threads:[~2021-02-03 21:48 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
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 [this message]
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-79c7df3d-94f6-4ffe-8ac3-3c0c6d23931c-1612388901691@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).