dynamic highlighting bugged

[main Alexey]

> It could have separate options for read and write

we have too many options, better no.

> not repeat "save" in log if no change or before x minutes.

we have the option "ui_session_save_interval", it is better to use.

[phi]

Log could, more generally, allow a module to change/update the last line of log rather than writing a new one.

I see no reason to set ui_session_save_interval at more than 1s except for the clogged log. Then, this log line is useful not to know when but where the session is saved, when several settings are used.

[main Alexey]

I don't understand what change you suggest?

[phi]

As you ask for it, here's a suggestion:

Let's call the function logprint(str) that prints str in the log window.
If str1 has a header like in "[header]message1" then if a subsequent call logprint(str2) with str2= "[header]message2" will replace str1 in the log window instead of being appended to it.

Thus,
logprint("[Saved session]: "default.cuda-session 15 files at 12:03")
logprint("[Saved session]: "default.cuda-session 16 files at 12:04")
would only display the last line, avoiding the cluttering od the log.

[main Alexey]

hmm, it can be done, even for the log lines w/o [ ] brackets, but not sure it is ok. log lines are not written in such way in other programs.
also some plugins can do 'print' to Console and their log will be affected by this change, bad.
what you did - disabled option "log_sessions" - is simpler.