GNU bug report logs -
#15934
[Feature request] Highlight full lines
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 15934 in the body.
You can then email your comments to 15934 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#15934
; Package
emacs
.
(Wed, 20 Nov 2013 19:25:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
"Sebastien Vauban" <sva-news <at> mygooglest.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Wed, 20 Nov 2013 19:25:03 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
Hello,
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).
Best regards,
Seb
--
Sebastien Vauban
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#15934
; Package
emacs
.
(Wed, 11 Dec 2013 01:42:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 15934 <at> debbugs.gnu.org (full text, mbox):
[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.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#15934
; Package
emacs
.
(Wed, 11 Dec 2013 12:42:02 GMT)
Full text and
rfc822 format available.
Message #11 received at 15934 <at> debbugs.gnu.org (full text, mbox):
Hello Michael,
Michael Heerdegen wrote:
>> 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:
>
>
> *** /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
>
>
> Can we use this?
I've tested it. It does what I wish it should do!
Thanks...
Best regards,
Seb
--
Sebastien Vauban
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#15934
; Package
emacs
.
(Sun, 18 Aug 2019 17:54:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 15934 <at> debbugs.gnu.org (full text, mbox):
Michael Heerdegen <michael_heerdegen <at> web.de> writes:
> 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:
>
> *** /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
>
>
> Can we use this?
>
>
> Regards,
>
> Michael.
The suggested change works here, and I think the new behaviour makes
more sense. The user would want this to stand out, and it can be hard
to spot short lines.
Are there any objections to making this change? If there are none,
could you Michael please consider committing this to master?
Thanks,
Stefan Kangas
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#15934
; Package
emacs
.
(Mon, 19 Aug 2019 13:59:01 GMT)
Full text and
rfc822 format available.
Message #17 received at 15934 <at> debbugs.gnu.org (full text, mbox):
Stefan Kangas <stefan <at> marxist.se> writes:
> Are there any objections to making this change? If there are none,
> could you Michael please consider committing this to master?
I'll install the suggested patch in a couple of days if no one objects.
Thanks,
Michael.
Reply sent
to
Michael Heerdegen <michael_heerdegen <at> web.de>
:
You have taken responsibility.
(Fri, 23 Aug 2019 12:02:02 GMT)
Full text and
rfc822 format available.
Notification sent
to
"Sebastien Vauban" <sva-news <at> mygooglest.com>
:
bug acknowledged by developer.
(Fri, 23 Aug 2019 12:02:02 GMT)
Full text and
rfc822 format available.
Message #22 received at 15934-done <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Michael Heerdegen <michael_heerdegen <at> web.de> writes:
> I'll install the suggested patch in a couple of days if no one objects.
Done, with a minor correction:
[0001-Hi-lock-lines-up-to-right-margin-Bug-15934.patch (text/x-diff, inline)]
From d534687c43a1517e291b8de31e3ce23c2e6e4603 Mon Sep 17 00:00:00 2001
From: Michael Heerdegen <michael_heerdegen <at> web.de>
Date: Wed, 21 Aug 2019 15:51:13 +0200
Subject: [PATCH] Hi-lock lines up to right margin (Bug#15934)
* lisp/hi-lock.el (hi-lock-line-face-buffer): Change used regexp so
that a line terminating newline character is included in the match.
---
lisp/hi-lock.el | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/lisp/hi-lock.el b/lisp/hi-lock.el
index 65465d3b4c..b6b0e2a736 100644
--- a/lisp/hi-lock.el
+++ b/lisp/hi-lock.el
@@ -447,7 +447,7 @@ hi-lock-line-face-buffer
(hi-lock-set-pattern
;; The \\(?:...\\) grouping construct ensures that a leading ^, +, * or ?
;; or a trailing $ in REGEXP will be interpreted correctly.
- (concat "^.*\\(?:" regexp "\\).*$") face))
+ (concat "^.*\\(?:" regexp "\\).*\\(?:$\\)\n?") face))
;;;###autoload
--
2.23.0.rc1
[Message part 3 (text/plain, inline)]
The installed patch uses a shy group to wrap the $ operator. Doesn't
change the behavior but should be more correct.
Thanks,
Michael.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Sat, 21 Sep 2019 11:24:05 GMT)
Full text and
rfc822 format available.
This bug report was last modified 5 years and 324 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.