no settings for Find file: remember state (empty or not) of Content field.

[mckaygerhard]

i search a single string over bunch of files to start to edit using F4 but each time i do this i must put again the string.. cos the new behaviour of the patch [953b7e9f23bd2711115b231c53ecf7e0f8d9e510] from #3924 assumes that i must input each time in same file the string (if are thousand of times i must re input thousand of times)

What version of Midnight Commander is used?

1.2.26 also 1.2.24

What steps will reproduce the problem?

1 open mc
2 edit a file with almos 30000 lines
3 search for a string that are almost 1000 times
4 on each sear4ch i must put again that large string púfff

ALso in the panel views when i try to search

What is the expected output?

almost at least a configuration part where i can put content_is_empty=false

What do you see instead?

empty test that i understand its pretty great if we must to search many different strings but for same string its pretty tired

PD please if there any posibility to backport also to those versions

[andrew_b]

Replying to mckaygerhard:

What version of Midnight Commander is used?

1.2.26 also 1.2.24

What?

What steps will reproduce the problem?

1 open mc
2 edit a file with almos 30000 lines
3 search for a string that are almost 1000 times
4 on each sear4ch i must put again that large string púfff

Don't understand.

Probably, you should use search history.

[mckaygerhard]

Replying to andrew_b:

Don't understand.

Probably, you should use search history.

the description was clear i must input each time in same file the string (if are thousand of times i must re input thousand of times) that its insane

are you dump that already understand the description to provide better one?

the editor of mc becomes crap since that for search and replace

[ossi]

are you dump that already understand the description to provide better one?

even your attempt at insulting andrew is so garbled that one has to guess what you might mean. your command of english really isn't as good as you apparently think it is.

i played around a bit and found one case where the search field is cleared: when one does "find file" with no content string and then views/edits the found files, the first search does indeed start out with an empty search field. as andrew hinted, alt-h easily gets you the last search, but i suppose one might still find this mildly annoying under certain circumstances.

[mckaygerhard]

Replying to ossi:

i played around a bit and found one case where the search field is cleared: when one does "find file" with no content string and then views/edits the found files, the first search does indeed start out with an empty search field. as andrew hinted, alt-h easily gets you the last search, but i suppose one might still find this mildly annoying under certain circumstances.

your response was much much better and demostrates that the problem is understandable its obviously you take the time to investigate, event just put "wont fix" ..

It is very clear that the complicated bug reporting mechanism, the requirement to register and the forcing of perfect English means that only geeks report cases like this, suggesting that "no one is presented with the reported case" but the reallity is the contrary (like was happened with the terminal dump returned in 1.2.22 when we do CRTL+O)

Replying to ossi:

are you dump that already understand the description to provide better one?

even your attempt at insulting andrew is so garbled that one has to guess what you might mean. your command of english really isn't as good as you apparently think it is.

sadly today there are so many people who hate english that i learned just enough to post things...just like in the same way that Andrew wastes no time implementing the requested problem, a sarcastic irony i imagine