https://bugs.documentfoundation.org/show_bug.cgi?id=157303
Stéphane Guillou (stragu) changed:
What|Removed |Added
Blocks||102847
Version|24.2.0.0 alpha0+ Master |7.5.0.3 release
Status|UNCONFIRMED |NEW
CC||mikekagan...@hotmail.com,
||stephane.guillou@libreoffic
||e.org
Ever confirmed|0 |1
Summary|Calc Search: add|Calc Search:
|the \n (new line) in|support the \n (new line)
|Replace as regular |in Replace when "Regular
|expression, as in Writer|Expression" is on, as in
||Writer
--- Comment #3 from Stéphane Guillou (stragu)
---
Mike seems to agree that it should be made consistent with Writer:
(In reply to Mike Kaganski from bug 43107 comment #26)
> I would argue that for consistency, exactly because in Calc, the
> newline in a cell inserts *paragraphs* (not only available in the file
> format, but also in the API; and that is not a bug), the \n in the
> replacement box should behave *consistently* with Writer, where it inserts
> paragraphs.
I think it makes sense too. -> New
(or did I misunderstand your point, Mike?)
Let's say this "started" in 7.5 as a follow-up to the documentation fix for bug
43107.
Confirmed that replacing with \n in Calc does not work as one
would expect with "Regular Expressions" on.
Version: 24.2.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: e9a0c97de95688b2f86bbb4dd8c823af5442401c
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded
But in my (rather uninformed?) opinion, the whole thing should be made
consistent across components with the wider-ranging change of:
- making $ work in both search and replace for paragraph breaks
- making \n work in both search and replace for line breaks
... and the distinction between the two would only matter in Writer (where both
and exist)
Would solve many headaches in my opinion.
Referenced Bugs:
https://bugs.documentfoundation.org/show_bug.cgi?id=102847
[Bug 102847] [META] Quick Find, Search and Replace
--
You are receiving this mail because:
You are the assignee for the bug.