Last Modification in the Editor

[jiembe]

I have to say that I dislike the last modification in the editor or don't understand it :

have spaces in the search expression match multiple spaces and line breaks in the text.

Now when I cut a line including the line break I got an empty line instead as before: no line and the rest of the text moving up.
Is there a way to remove that new behaviour.

[kovidgoyal]

I dont follow, this is search and replace it has nothing to do with cutting and pasting.

[jiembe]

Sorry. English is not my first language.

What I mean is that when I do a search and replace with 'nothing' (as replace) I get blank lines rather than no line at all.
For ex:
a
b
c

searching and replacing b with its line break I got
a

c

instead of
a
c

[kovidgoyal]

I still dont quite follow, how are you searching for b with its line break? Can you post an example search and replace expression

[JSWolf]

Originally Posted by jiembe

Sorry. English is not my first language.

What I mean is that when I do a search and replace with 'nothing' (as replace) I get blank lines rather than no line at all.
For ex:
a
b
c

searching and replacing b with its line break I got
a

c

instead of
a
c

You need to search for b including the line ending and then you will get rid of the line. when you replace with nothing.

[jiembe]

Yes. I forgot to mention it in my second post. My search include the line break.

[kovidgoyal]

Then use regex mode like this

some text$

[jiembe]

You have broken the normal search and replace behavior found in an editor. I think you have tried to help one person but at the expense of others. He's the one who should use regex not all the others.
You should correct it and go back to the normal behaviour.

[JSWolf]

Originally Posted by kovidgoyal

Then use regex mode like this

some text$

I agree. 4.13 has broken normal search/replace

If I have

	a
	b
	c

And I select the b line including the line ending and do a replace all, I end up removing all of the letter b. So yes it is broken. Can you please remove this new broken feature?

I am going to have to go back to 4.12 because I use this sort of search/replace.

[MerlinMama]

I really dislike the new search & replace. I have some double spaces in my text, so I did as usual and searched for 2 spaces, replaced with 1 space. In my entire document, each letter was now separated by a space. There was an extra space between an ellipsis and the next word, I searched for the ellipsis and space to replace with just the ellipsis, and it didn't change anything.

Also: I search for </p> with a space in front of it to remove the space, and it finds all of the </p> even if there are no spaces in front of it

[JSWolf]

Originally Posted by MerlinMama

I really dislike the new search & replace. I have some double spaces in my text, so I did as usual and searched for 2 spaces, replaced with 1 space. In my entire document, each letter was now separated by a space. There was an extra space between an ellipsis and the next word, I searched for the ellipsis and space to replace with just the ellipsis, and it didn't change anything.

Because searching is now broken, I've gone back to 4.12. I'm waiting for the fixed version as this is a serious issue.

[Quoth]

I read the "what's new" and when I read that

Edit book: When searching in normal mode, have spaces in the search expression match multiple spaces and line breaks in the text.

I decided not to install/upgrade. That alone seemed weird. It seemed like totally broken behaviour. If I want to find more than one space, I'll search for that.

If a program is actually doing what I want, I only upgrade if there is a major reason to do so and other people haven't seen a problem. I always read change logs and similar.
It's part of the reason I don't "auto update" anything ever and run Linux Mint and don't apply kernel updates too quickly.

One of the things really good about Calibre (there are many), is that it doesn't autoupdate.

One day the entire Internet and commerce will fail because of increased Cloud dependence for Mobile Billing, Point of Sale, ATMs, Wholesale stock reordering and many other things due to "Elastic Computing" auto-updates on Datacentre /Cloud /ISP Routers and webservers and someone pushing out a badly tested patch on a Friday night.

A fable about it: 'No Silver Lining'

[kovidgoyal]

No worries, I will simply move it off to a separate fuzzy mode for the next release. That can do other things like match curly quotes with straight ones and similar.

[davidfor]

I'm not sure what "fuzzy" search you are going to use, or why it would help. The problem I have with the change to the "normal" search, is that when I use it, I expect it to only find exact matches for the search term. That is how it works in every editor I have ever used. Now, if there is any white space involved, it probably won't be an exact match. Any leading or trailing white space is being removed. And white space in the middle is being reduced to "one or more".

For example, if I search for:

 abc  def

(space at the start and end, two spaces in the middle)

It will match, "xyzabc defghi", which is not the string I am looking for.

The problem in the first post is because the last character in the search term is the line-end character and is removed with the current search. Changing to a regex using a $ to get the end of the line won't help as that doesn't include the line-end character in the match, so it won't get replaced.

[Sirtel]

Originally Posted by JSWolf

Because searching is now broken, I've gone back to 4.12. I'm waiting for the fixed version as this is a serious issue.

I agree and am doing the same. I often search for characters with redundant spaces in the editor, or even spaces only, to remove them. Now I would be unable to do so, if I updated.