GNU bug report logs - #56335
29.0.50; [PATCH] Add more breakpoint chars support to longlines-mode

Previous Next

Package: emacs;

Reported by: Manuel Giraud <manuel <at> ledu-giraud.fr>

Date: Fri, 1 Jul 2022 10:36:01 UTC

Severity: wishlist

Tags: patch

Found in version 29.0.50

Fixed in version 29.1

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Manuel Giraud <manuel <at> ledu-giraud.fr>
To: Lars Ingebrigtsen <larsi <at> gnus.org>
Cc: Eli Zaretskii <eliz <at> gnu.org>, 56335 <at> debbugs.gnu.org, Manuel Giraud <manuel <at> ledu-giraud.fr>
Subject: bug#56335: 29.0.50; [PATCH] Add more breakpoint chars support to longlines-mode
Date: Wed, 06 Jul 2022 12:18:57 +0200
Lars Ingebrigtsen <larsi <at> gnus.org> writes:

[...]

>> I'm now trying to update the search/query-replace but I don't understand
>> how 'search-spaces-regex' works. It seems that with it I should be able
>> to jump above soft newlines during search, but how ?
>
> Hm, not sure either...

Ok. As far as I understand, a search will use `search-spaces-regex' in
place of an explicit space entered by the user at prompt.

So I could use this to match separators (and newline) when a space is
entered but it won't automatically «jump» soft newlines as I wanted.

Example with this longlines-mode content:
--8<---------------cut here---------------start------------->8---
Element1|Element2|
Element3|
--8<---------------cut here---------------end--------------->8---

Searching for "|Element3|" won't match but I could use
`search-spaces-regex' to make searching for " Element3 " match. What do
you think?
-- 
Manuel Giraud




This bug report was last modified 3 years and 7 days ago.

Previous Next


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