From: goncholden <goncholden@protonmail.com>
To: Emanuel Berg <moasenwood@zoho.eu>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Customisation for Comments
Date: Fri, 11 Feb 2022 21:04:09 +0000 [thread overview]
Message-ID: <-oBSWjHnEPX6Ij-6o8c538OwBiy3O59rplNI6SW-JeNjiF49VEOLb_HwjJZoq-WPdBLtc_KOZzg2-mj4QDkgPW4HtVxM5XANs4JCglO6Khc=@protonmail.com> (raw)
In-Reply-To: <87zgmxrwao.fsf@zoho.eu>
------- Original Message -------
On Friday, February 11th, 2022 at 8:19 PM, Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> wrote:
> goncholden wrote:
>
> > > then start with a function that increases the contrast by CON.
> >
> > I have done all that and introduced them into a minor-mode.
> > There are a number of minor-modes out there that do provide
> > font-lock customization. Extending a major-mode is not
> > simple, eg. a derived mode from prog-mode is used to make
> > a major-mode, like emacs-lisp-mode (which actually derives
> > from lisp-data-mode which derives from prog-mode).
> > This means that if I derive from prog-mode, I would need to
> > setup the syntax for the major-mode before I can change the
> > comment font-locking.
> Why do you need modes at all for that?
I am relatively new to elisp planning and could do with suggestions.
The plan is to make this available to users, and though minor-modes
are the way to do things.
next prev parent reply other threads:[~2022-02-11 21:04 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-09 22:59 Customisation for Comments goncholden via Users list for the GNU Emacs text editor
2022-02-10 23:37 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-02-11 17:26 ` goncholden
2022-02-11 19:00 ` goncholden
2022-02-11 19:19 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-11 19:25 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-02-11 19:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-11 19:51 ` goncholden
2022-02-11 20:05 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-11 20:14 ` goncholden
2022-02-11 20:19 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-11 21:04 ` goncholden [this message]
2022-02-11 22:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-11 22:59 ` goncholden
2022-02-11 23:16 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-02-11 23:21 ` goncholden
2022-02-12 18:04 ` goncholden
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='-oBSWjHnEPX6Ij-6o8c538OwBiy3O59rplNI6SW-JeNjiF49VEOLb_HwjJZoq-WPdBLtc_KOZzg2-mj4QDkgPW4HtVxM5XANs4JCglO6Khc=@protonmail.com' \
--to=goncholden@protonmail.com \
--cc=help-gnu-emacs@gnu.org \
--cc=moasenwood@zoho.eu \
/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).