From: pietru@caramail.com
To: pietru@caramail.com
Cc: help-gnu-emacs@gnu.org
Subject: Re: Changing into greek glyphs in texinfo-mode
Date: Tue, 2 Feb 2021 13:56:21 +0100 [thread overview]
Message-ID: <trinity-d7bbebd9-8343-4355-8ee1-3626943c1647-1612270581237@3c-app-mailcom-bs13> (raw)
In-Reply-To: <trinity-7d54de29-3219-4a08-8631-bb7d20afd664-1612242273437@3c-app-mailcom-bs13>
I can see that dafny-mode ts relying on "prog-mode.el". Same
prettify functionality is also being provided by "tex-mode.el".
But I don't see how tex-mode.el uses prog-mode.el
> Sent: Tuesday, February 02, 2021 at 5:04 PM
> From: pietru@caramail.com
> To: moasenwood@zoho.eu
> Cc: help-gnu-emacs@gnu.org
> Subject: Re: Changing into greek glyphs in texinfo-mode
>
> It is calling prog-mode.el, which is part of emacs. I am trying to
> make a minor mode with all functionality in my minor mode though.
>
> What function would I need to copy over?
>
>
>
> > Sent: Tuesday, February 02, 2021 at 4:10 PM
> > From: "moasenwood--- via Users list for the GNU Emacs text editor" <help-gnu-emacs@gnu.org>
> > To: help-gnu-emacs@gnu.org
> > Subject: Re: Changing into greek glyphs in texinfo-mode
> >
> > pietru wrote:
> >
> > > I am having a problem with dafny-font-lock-keywords, as
> > > I cannot see where the functionality for replacing the
> > > "forall" keyword is being called and set up.
> >
> > If it is/uses font-lock then this is handled outside of the
> > mode, the mode just sets it up, that way not every mode has to
> > have the horsepower to also execute it.
> >
> > Keep on using the source, Luke! Line 198 looks suspicious, as
> > do 509...
> >
> > --
> > underground experts united
> > http://user.it.uu.se/~embe8573
> > https://dataswamp.org/~incal
> >
> >
> >
>
>
next prev parent reply other threads:[~2021-02-02 12:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-31 13:18 Changing into greek glyphs in texinfo-mode pietru
2021-01-31 21:03 ` pietru
2021-01-31 22:08 ` Stefan Monnier
2021-01-31 22:17 ` pietru
2021-02-01 13:35 ` pietru
2021-02-01 13:51 ` Gregory Heytings
2021-02-01 14:02 ` pietru
2021-02-01 14:01 ` moasenwood--- via Users list for the GNU Emacs text editor
2021-02-01 14:59 ` pietru
2021-02-01 17:30 ` pietru
2021-02-02 4:10 ` moasenwood--- via Users list for the GNU Emacs text editor
2021-02-02 5:04 ` pietru
2021-02-02 12:56 ` pietru [this message]
2021-02-02 13:26 ` 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-d7bbebd9-8343-4355-8ee1-3626943c1647-1612270581237@3c-app-mailcom-bs13 \
--to=pietru@caramail.com \
--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).