Refresh for remote files change doesn't work correctly

Hi Martin
I am using WinSCP v5.19.2 on a Centos Stream 8.
I was viewing a directory with WinSCP, and was logged in the same time with PuTTY, using the same (root) account on both.

I had to copy a file using PuTTY, so
I wasn't able to see httpd.conf.002 listed in WinSCP even after clicking a lot on the REFRESH green circular arrow, neither changing directory and coming back here.

Is there maybe a caching problem?

Thank you
Julian

Hi Martin
Today WinSCP refreshes correctly.
The only difference from yesterday was ..the session age: yesterday the session was quite old.
I hope this can help you debugging.

Thank you !
Julian

Let me know, if the problem ever happens again.

Hi Martin!
I'm back to WinSCP this month, and I found also the same problem I told in https://winscp.net/forum/viewtopic.php?t=30352
Right now I am closing and reopening WinSCP very often to bypass these problems.
Environment is Windows 10 1909 with Centos Stream 8.
ByTheWay: is there a setting to make file editing are written immediately on the remote file system ?
Thank you.
GulJul

So do you have steps to reproduce the "WinSCP Editor Window goes to background unexpectedly" problem reliably? Can you reproduce the problem with the debug build I have sent you then?

ByTheWay: is there a setting to make file editing are written immediately on the remote file system ?

Are you asking for WinSCP to save the changes continuously, without you using Save command?

Hi Martin
I am not saying to save continuously the file under editing ...fortunately :-)
I only need to be sure when I chose "save file", it is written to he file system without waiting minutes, or have to check for file timestamp with another tool :-(

Coming back to the other errors: as like at the beginning of the year, it happens very randomly: sometimes after a few minutes I use WinSCP, sometimes after half an hour.
During the last days, I tried to use WinSCP under Windows 2019 instead of Windows 10, and it happens randomly the same way.

About debug version: I remember in January you suggested me another version of WinSCP (and it happened again), but I fear it was not a debug version.

Thank you very much
Julian

Hi Martin.
I have a new detail about editor sinking to background at unsuccessful F3: it is enough to close and reopen the editor to gain normal behaviour. Not necessary to close WinSCP also.

Have a nice sunday
GiulJul

I have sent you an email with a debug version of WinSCP regarding the "WinSCP Editor Window goes to background unexpectedly" issue.

GiulJul wrote:

I only need to be sure when I chose "save file", it is written to he file system without waiting minutes, or have to check for file timestamp with another tool :-(

When you choose Save, the file is saved immediately. If you have different experience, use the debug build too. Also, it would be nice, if you keep the issues separate. This topic is a mess.