From: Michael Heerdegen <michael_heerdegen@web.de>
To: Sebastien Vauban
<public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.org>
Cc: public-15934-ubl+/3LiMTaZdePnXv/OxA@plane.gmane.org
Subject: bug#15934: [Feature request] Highlight full lines
Date: Wed, 11 Dec 2013 02:41:14 +0100 [thread overview]
Message-ID: <8738m088qt.fsf@web.de> (raw)
In-Reply-To: <86pppuvpv2.fsf@somewhere.org> (Sebastien Vauban's message of "Wed, 20 Nov 2013 20:24:01 +0100")
[-- Attachment #1: Type: text/plain, Size: 249 bytes --]
Hi Sebastien,
> I think it'd be nicer to highlight full lines (vs up to the last character)
> when using C-x w l (highlight-lines-matching-regexp).
I too think that this would be more appropriate. Something like
the following should do the job:
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: hi-lock.patch --]
[-- Type: text/x-diff, Size: 691 bytes --]
*** /home/micha/software/emacs/lisp/hi-lock.el 2013-10-26 18:26:42.117620602 +0200
--- /home/micha/today/hi-lock.el 2013-12-11 02:31:03.251432385 +0100
***************
*** 448,454 ****
(hi-lock-set-pattern
;; The \\(?:...\\) grouping construct ensures that a leading ^, +, * or ?
;; or a trailing $ in REGEXP will be interpreted correctly.
! (concat "^.*\\(?:" regexp "\\).*$") face))
;;;###autoload
--- 448,454 ----
(hi-lock-set-pattern
;; The \\(?:...\\) grouping construct ensures that a leading ^, +, * or ?
;; or a trailing $ in REGEXP will be interpreted correctly.
! (concat "^.*\\(?:" regexp "\\).*\\($\\)\n?") face))
;;;###autoload
[-- Attachment #3: Type: text/plain, Size: 39 bytes --]
Can we use this?
Regards,
Michael.
next prev parent reply other threads:[~2013-12-11 1:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 19:24 bug#15934: [Feature request] Highlight full lines Sebastien Vauban
2013-12-11 1:41 ` Michael Heerdegen [this message]
[not found] ` <8738m088qt.fsf-S0/GAf8tV78@public.gmane.org>
2013-12-11 12:40 ` Sebastien Vauban
2019-08-18 17:52 ` Stefan Kangas
2019-08-19 13:58 ` Michael Heerdegen
2019-08-23 12:00 ` Michael Heerdegen
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=8738m088qt.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=public-15934-ubl+/3LiMTaZdePnXv/OxA@plane.gmane.org \
--cc=public-sva-news-D0wtAvR13HarG/iDocfnWg@plane.gmane.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.
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).