From: Juri Linkov <juri@linkov.net>
To: Manuel Giraud <manuel@ledu-giraud.fr>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
56335@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#56335: 29.0.50; [PATCH] Add more breakpoint chars support to longlines-mode
Date: Wed, 06 Jul 2022 21:49:10 +0300 [thread overview]
Message-ID: <86h73uqdp5.fsf@mail.linkov.net> (raw)
In-Reply-To: <877d4qbl2m.fsf@elite.giraud> (Manuel Giraud's message of "Wed, 06 Jul 2022 12:18:57 +0200")
>>> 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:
>
> Element1|Element2|
> Element3|
>
> Searching for "|Element3|" won't match but I could use
> `search-spaces-regex' to make searching for " Element3 " match. What do
> you think?
After longlines.el was unobsoleted, I checked that its search/replace
functions have correct implementation: longlines-search-function,
longlines-search-forward, longlines-re-search-forward, all looks correct.
Or do you mean that you tried to implement a new feature where
whitespace contains non-whitespace characters? Have you tried
to change the value of search-spaces-regexp to include such
characters?
next prev parent reply other threads:[~2022-07-06 18:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-01 10:35 bug#56335: 29.0.50; [PATCH] Add more breakpoint chars support to longlines-mode Manuel Giraud
2022-07-01 13:33 ` Manuel Giraud
2022-07-02 12:14 ` Lars Ingebrigtsen
2022-07-02 12:23 ` Visuwesh
2022-07-02 12:46 ` Phil Sainty
2022-07-02 12:39 ` Eli Zaretskii
2022-07-02 12:44 ` Lars Ingebrigtsen
2022-07-02 13:03 ` Eli Zaretskii
2022-07-02 15:39 ` Lars Ingebrigtsen
2022-07-02 21:19 ` Manuel Giraud
2022-07-03 5:14 ` Eli Zaretskii
2022-07-04 8:06 ` Manuel Giraud
2022-07-04 11:18 ` Eli Zaretskii
2022-07-05 13:07 ` Manuel Giraud
2022-07-05 16:32 ` Lars Ingebrigtsen
2022-07-06 7:43 ` Manuel Giraud
2022-07-06 11:18 ` Lars Ingebrigtsen
2022-07-06 10:18 ` Manuel Giraud
2022-07-06 11:20 ` Lars Ingebrigtsen
2022-07-06 18:49 ` Juri Linkov [this message]
2022-07-06 20:47 ` Manuel Giraud
2022-07-08 3:32 ` Richard Stallman
2022-07-08 7:14 ` Manuel Giraud
2022-07-08 7:22 ` Eli Zaretskii
2022-07-10 8:58 ` Manuel Giraud
2022-07-10 13:02 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86h73uqdp5.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=56335@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=manuel@ledu-giraud.fr \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.