syncthing-android
syncthing-android copied to clipboard
syncthing
Feature request: allow "Save to Syncthing" to overwrite files
When using the "Save to Syncthing" option from the "share via" menu of another app, files that already exist in the synced folder will not be overwritten. (Currently, after attempting to save a file to a synced folder under an already-existing filename, a text box appears saying "0 files were copied to [folder name], 1 already exist" .)
Please add an option to allow the user to choose whether or not to overwrite files when using "Save to Syncthing". This could either be a pop-up dialogue each time the user tries to save files with names that already exist, or it could be set globally in a preferences menu somewhere.
I'm afraid I disagree. #1472 is, as far as I understand it, an issue with navigating subfolders in the file browser of "Save to Syncthing", whereas this is about whether "Save to Syncthing" will actually save a file or not.
Apologies if my original wording didn't make this clear.
Assume for this feature request that the user can identify exactly the filename (including any subfolder structures) that they want to write to: say, foo/bar.txt in a folder syncedfolder that Syncthing syncs.
Current behaviour seems to be that if foo/bar.txt already exists in syncedfolder when "Save to Syncthing" is told to write to it, then "Save to Syncthing" will exit without writing anything to foo/bar.txt, and instead display the message 0 files were copied to "syncedfolder", 1 already exists.
I think it would be useful if the user could change this behaviour: many apps out there are not able to edit the files in syncedfolder directly but only import them into some app-specific location, edit them there and then export them back to syncedfolder using the "Share to Syncthing" option of the "share via" menu. That "Save to Syncthing" will not overwrite pre-existing files complicates this procedure.
Please refrain from pointless comments, or we'll start locking issues. Use reactions to express your interest.
I figured it pointful to bring up a topic with no news in two years. Anyway, as no SPAM was intended, will switch to reactions-mode :)
No news means there is no news.
Regardless of the intent, the end result is spam, as your comment ended up generating an email and a notification to everyone who is watching this repo.
And that's exactly the intent, bringing the topic back up, as clearly if nothing happened in two years for such a minor issue it's clearly not been tracked as hoped (no blaming intended, just an innocent bring-up). Still, nevermind, no need for harsh answers though. Won't SPAM now, will stop answering.
Making +1/UP etc comments doesn't make things happen, it just annoys everyone and people unsubscribe from all notifications.
If you want to make stuff happen, open a pull request with the change you want to see.