Don't change existing files' permissions

1.: If I upload a remotely existing file WinSCP seems to remove the existing file first instead of overwriting it. The result is that all uploaded files get the default file attributes. This behavior drove me crazy, so I stopped using WinSCP (which I like very much in all other aspects) most of the time and went back to WS-FTP (and using its sftp feature). Just checked out your new build and see that you added some nice options (f.i. removing the overwrite confirmation). Unfortunately, WinSCP still changes the file permissions. Is this a scp problem or can you change this on your end? I'd very much crave to stop this nasty behavior. Thanks.
2.: WS-FTP shows a symbol for the ".." to double-click and go up one directory. From my experience that's much faster than looking for the tiny "Parent Directory" in the tool bar. Can you add that symbol or a ".." in the file list which would go up one directory on double-click?
3.: I would like to see configurable options for bolding/coloring files depending on the permissions etc. F.i. making executable files bold as in the shell or blue or so. Or use a different color for dot files (the currently used grey isn't that easy to read for my taste).
4.: Can you also remove the delete confirmation?

Thanks for considering!

KaiS wrote:

1.: If I upload a remotely existing file WinSCP seems to remove the existing file first instead of overwriting it. The result is that all uploaded files get the default file attributes.

It is mentioned many times in the forum already, but once again: uncheck "Set permissions" option on Copy confirmation dialog.

KaiS wrote:

Can you add that symbol or a ".." in the file list which would go up one directory on double-click?

It is there, you don't have it? (it is only in Commander style interface)

KaiS wrote:

3.: I would like to see configurable options for bolding/coloring files depending on the permissions etc. F.i. making executable files bold as in the shell or blue or so. Or use a different color for dot files (the currently used grey isn't that easy to read for my taste).

OK, I'll think about that :)

KaiS wrote:

4.: Can you also remove the delete confirmation?

I can.

Hi Martin,

thanks for your answer and for providing the new build (I've yet to download).

martin wrote:

It is mentioned many times in the forum already, but once again: uncheck "Set permissions" option on Copy confirmation dialog.

I've never seen this dialog, it's possibly only appearing in Commander mode? I read the other feature requests but not the other fora. I go and see if they provide any clue to this.

martin wrote:

It is there, you don't have it? (it is only in Commander style interface)?

I don't use Commander mode. A while ago, when starting to use FTP (7 years ago) I used WS-FTP because of its "classic" interface and found it quite nice and it kept it this way after they introduced the Explorer integration. But I switched to the Explorer mode some months ago, because I found that most of the time the window on the left would not be the window I need, so it just takes valuable screen real estate. It doesn't fit my working style anymore. So I immediately turned to the Explorer interface when I discovered WinSCP some months ago. I can see why the "t" isn't there in the Explorer interface and won't nag you about it :roll:

[coloring of files]
Maybe you could just grab this from the PuTTY settings?

martin wrote:

I can.

Thanks! Now just for a better "Copy confirmation dialog" appearance. Shouldn't it be among the "Preferences"?

BTW: Did you notice that the "Preferences" dialog seems to be too small for some of the property sheets if launched from Icon or View/Preferences? If I launch it from Interface/Preferences it's big enough, but if I launch it from View/Preferences it's got two lines of tabs and so the space is smaller and some stuff is cut at the bottom.

I've never seen this dialog, it's possibly only appearing in Commander mode? I read the other feature requests but not the other fora. I go and see if they provide any clue to this.

It is even in explorer mode. You must press "More" button on windows that pops up just before file transfer. It is also possible that you turned off file transfer confirmation for Drag&drop (see Preferences)

Now just for a better "Copy confirmation dialog" appearance. Shouldn't it be among the "Preferences"?

It may be there too, but I wanted to simply enable user to change copy settings for each transfer individually. This is necessary for example when user doesn't trust the automatic file transfer type detection and he/she wants to select ascii/binary for each transfer individually.

BTW: Did you notice that the "Preferences" dialog seems to be too small for some of the property sheets if launched from Icon or View/Preferences? If I launch it from Interface/Preferences it's big enough, but if I launch it from View/Preferences it's got two lines of tabs and so the space is smaller and some stuff is cut at the bottom.

No I haven't noticed. It looks fine for me. Both in Win2000 and WinXP. Which OS are you using? Are you using big fonts or something other, that might influence window design?

I find the qoting method somewhat painful, so I stop quoting.

1. Yes, I switched off that dialog, of course. I couldn't find it after switching on either. But I possibly overlooked that "more". I changed it now in the ini file. Please keep this as alternative. It's easier to transfer on other machines and proves easier for configuration as well. I now have:
PreserveRights=0
which seems to be "yes".I think you should have this at "0" as a default. I've not seen any other product which changes existing permissions each time you overwrite a file, so doing this as default is not what people expect. And as you see one may never find that dialog during normal operation. I also had problems with text files always getting transferred binary, that was the other reason I switched back to WS-FTP. That option is also on this "dreaded" dialog. I suggest you add .pl and .sh files to the list, because these also need to be transferred in text mode usually.
Can you tell what "PreserveReadOnly=1" is for? Is this "Add X to directories" = No?
It would be nice to have a second file extension list which triggers adding the executable bit, so that f.i. .pl files get first transferred in text mode and then made executable. Also useful would be an option that applies a different mask depending on the fact if the file is placed in my home directory or outside. F.i. working as root I most often want that the files I place in my home directory are not even readable by others while I usually may want files outside to be readable/executable by others. But I fear there's no really satisfactory way to add this.

2. Yes, it may be useful being able to switch transfer mode etc. from transfer to transfer. But the need to confirm each time is a nuisance. Couldn't you add a toggle button or a button which launches the "Copy confirmation" dialog (or both), so one can change this any time at will?

3. I noticed a new small layout problem. The frame which appears around the file when I want to rename looks now quite different, it's "bolder". This may be a result of using a new characterset for display in WinSCP, but shouldn't. Can you see this?

4. As for the Preferences dialog, I add a screenshot below. The only difference to a normal screen setup I have is the dual screen which I doubt is responsible for this. Can you repro it now?

Anonymous wrote:

1. Yes, I switched off that dialog, of course. I couldn't find it after switching on either. But I possibly overlooked that "more".

You must enable Copy confirmation dialog first:
Preferences/Panels/Confirm drag&drop operations.
Than on "drop" you'll see a dialog, press "More" button and uncheck "Set permissions" checkbox. You'll probably want to check "Use same settings next time" too.

I think you should have this at "0" as a default. I've not seen any other product which changes existing permissions each time you overwrite a file, so doing this as default is not what people expect.

It is off by default since build #110.

I also had problems with text files always getting transferred binary, that was the other reason I switched back to WS-FTP. That option is also on this "dreaded" dialog.

"Automatic" transfer mode is turned on by default.

I suggest you add .pl and .sh files to the list, because these also need to be transferred in text mode usually.

These extensions are included since build #101. However this did not affect current installations, even if you've upgraded.

Can you tell what "PreserveReadOnly=1" is for?

This has effect on download only. I means, that if you are downloading file that you don't have rights to write to, it is marked "read-only" in local directory.

It would be nice to have a second file extension list which triggers adding the executable bit, so that f.i. .pl files get first transferred in text mode and then made executable.

Good idea, I'll consider that.

Couldn't you add a toggle button or a button which launches the "Copy confirmation" dialog (or both), so one can change this any time at will?

I'll see.

To the layout issues: Thanks for screenshot, etc. I'll make window bigger.

After many years the option is even a default, but what's about giving the possibility of NOT changing the owner/group of the file, as well?
When I log as USERA:GROUPA and send a file that can be executed only if the owner is USEREXECUTOR:GROUPEXECUTOR, I have to change the ownership of the file every time.

If I am a developer, every time i send a new version of the file, i have to change the ownership and i didn't find where to disable that...

Esperanto wrote:

After many years the option is even a default, but what's about giving the possibility of NOT changing the owner/group of the file, as well?

When is ownership changing? When you overwrite an existing file?
It might be due to a transfer via a temporary filename:
https://winscp.net/eng/docs/resume#automatic
You can turn it off.

Thanks @martin, it was that. Maybe a note could be useful in the options:
Transfer by temporary filename (could change ownership of overwritten files)