Sorry, I didn’t read the question carefully enough. And there doesn’t seem to be possible for me to delete my answer.

*.nfo files are detected as MSDOS Style language.

@AngryGamer has submitted fixes for this and a few other issues at github. It looks like they have been accepted and will be included in the next release. Thanks AngryGamer!

@Claudia-Frank You’re right, my mistake…
If anyone has a solution to disable this safety message…
Cheers ;)

Thank you for your answers!

For number 1, I’d just like the ‘find in file’ window to behave like it does when using a simple search (stay open until I close it). I do many consecutive searches into files (for example to count occurrences of a series of words), and I have to reopen the search window every time. It’s quite annoying, it would be useful for me to have an option in settings to disable auto-close.

For number 2, the workaround you suggest (bottom-up editing) works perfectly, I posted this request just for a possible future implementation (actual behaviour is useless because results become invalid after an edit). It’s just a matter of actual behaviour vs expected behaviour.

@Debabrata-Ghosh

I would install xml tools plugin and use pretty print (formatting).

Cheers
Claudia

The number of style is hard coded in scintilla. So we can’t modify it. Sorry.

@Claudia-Frank
To be honest, I was unaware of it as well until I saw this post and went to read tail’s man page to see if it can support it.
My point is that however this feature is implemented we don’t want it to do active polling.
When the file is present I hope that there is a way for a thread to block on it until it is modified.
When there is no file we need a mechanism to find out that it was created.

@Vasile-Caraus

Nothing builtin.
I think you need to have a copy of your original files or use tools like svn, git etc… and do a compare afterwards.

Cheers
Claudia

I totally agree about the first two items on your list - particularly the second one.

Every time I need to search backwards, or perform a case sensitive search (etc), I have to remind myself to turn the switch off again before I perform an unrelated search and get the wrong result! When I am searching for a string, my mind is on the subject matter - not on the quirks of the search box.

Probably the simplest answer would be to add a few extra search buttons with no history - ‘Search forwards’, ‘Search backwards’, ‘Search for whole word’ etc. However anyone who really wants to configure the search box with different defaults, should have to take some special action.

I also wish the search box would echo any shortcut keys it does not explicitly use back to the active window. As it is, when the search box has focus, the shortcuts do not work.

It is a shame the search box is as it is, because otherwise it is so powerful.

David

It works now.
Thank you very much.

@lytmkai

by unchecking the new style save dialog you get the default extension
for the language in question.

Cheers
Claudia

@Gillian-Wallace

could it be that you saved the file as UTF-8 with BOM?
This could explain the additional chars at the beginning.

Cheers
Claudia