GNU bug report logs - #15934
[Feature request] Highlight full lines

Previous Next

Package: emacs;

Reported by: "Sebastien Vauban" <sva-news <at> mygooglest.com>

Date: Wed, 20 Nov 2013 19:25:01 UTC

Severity: wishlist

Done: Michael Heerdegen <michael_heerdegen <at> web.de>

Bug is archived. No further changes may be made.

Full log

View this message in rfc822 format

From: Michael Heerdegen <michael_heerdegen <at> web.de>
To: Sebastien Vauban <public-sva-news-D0wtAvR13HarG/iDocfnWg <at> plane.gmane.org>
Cc: public-15934-ubl+/3LiMTaZdePnXv/OxA <at> plane.gmane.org
Subject: bug#15934: [Feature request] Highlight full lines
Date: Wed, 11 Dec 2013 02:41:14 +0100

[Message part 1 (text/plain, inline)]
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:


[hi-lock.patch (text/x-diff, inline)]
*** /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

[Message part 3 (text/plain, inline)]
Can we use this?


Regards,

Michael.
This bug report was last modified 5 years and 326 days ago.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.