unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: lee <lee@yun.yagibdah.de>
Cc: koppel@ece.lsu.edu, 17021@debbugs.gnu.org
Subject: bug#17021: 24.3.50; extension to hi-lock.el
Date: Thu, 13 Aug 2020 12:32:48 +0200	[thread overview]
Message-ID: <877du2g7jj.fsf@gnus.org> (raw)
In-Reply-To: <87mwgp1mq4.fsf@yun.yagibdah.de> (lee@yun.yagibdah.de's message of "Mon, 17 Mar 2014 05:18:59 +0100")

lee <lee@yun.yagibdah.de> writes:

> | This is an extension to hi-lock mode (of bzr revno 116727):
> | 
> | You can use the buffer-local variable `hi-lock-patterns-file' to
> | specify a file to write the higlighting-patterns to.  When this
> | variable is set, the highlighting-patterns will be kept in a dedicated
> | buffer instead of being written into the very file you`re editing.

This patch unfortunately got no attention when it was posted seven years
ago, and it no longer applies to Emacs 28.

I am not a hi-lock user myself -- are there anybody else on the bugs
mailing list here that can comment on whether this is something we'd
want to add?  It does sound useful to me, but I'm not really familiar
with how hi-lock works.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  parent reply	other threads:[~2020-08-13 10:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-17  4:18 bug#17021: 24.3.50; extension to hi-lock.el lee
2014-03-17  8:21 ` lee
2014-03-17 10:53   ` lee
2014-03-24  4:54 ` bug#17021: updated patch lee
2020-08-13 10:32 ` Lars Ingebrigtsen [this message]
2020-08-13 18:43   ` bug#17021: 24.3.50; extension to hi-lock.el David Koppelman
2020-08-13 19:50     ` Stefan Kangas
2020-08-13 21:46       ` David Koppelman
2020-08-16 17:49         ` hw
2020-08-17  0:32           ` Juri Linkov
2020-09-14 15:07             ` Lars Ingebrigtsen

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=877du2g7jj.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=17021@debbugs.gnu.org \
    --cc=koppel@ece.lsu.edu \
    --cc=lee@yun.yagibdah.de \
    /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).