Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

File Filter Regular Expressions Don't Work for Subdirectories when Synchronizing #6285

Closed
cyberduck opened this issue Oct 1, 2011 · 1 comment

Comments

@cyberduck
Copy link
Collaborator

d3534c6 created the issue

Hello,

I am using these filters:

Downloads:

.*~\..*|\.DS_Store|\.svn|CVS|RCS|SCCS|\.git|\.bzr|\.bzrignore|\.bzrtags|\.hg|\.hgignore|\.hgtags|_darcs|settings_local\.pyc?|.*\.pyc

Uploads:

.*~\..*|\.DS_Store|\.svn|CVS|settings_local\.pyc?|.*\.pyc

So basically I have added "settings_local.pyc?", and ".*.pyc" to the filters so that my compiled python and local settings are not transferred.

When I perform a synchronization between my local folder and remote SFTP folder, these filters correctly remove all .pyc files from the root remote directory. In subdirectories, however, the .pyc and settings_local.py files still appear.

To test if the problem was specific to my regular expressions, I tested against the first default regular expression ".~..". I put a file called "test~.txt" into both the root remote directory and a remote subdirectory ("local/test~.txt"). The file did not appear in either location for download when I synchronized. This suggests that there is something particular to my regular expressions, but I think I have written them correctly.

Thank you.

@cyberduck
Copy link
Collaborator Author

@dkocher commented

The regular expression configured looks fine, it should match any filename wether in a sub director or not. However, note that we do not delete files when synchronizing. I suppose you have previously uploaded these when the regular expression was not customized yet.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant