Folder contents was not excluded when exclude pattern was */.AppName/files/*

[slrslr]

Hello,

exclude pattern is: */.AppName/files/*

i expected that it will exclude content of the /home/me/.AppName/files folder but files/directories inside it was backed up seemingly

i have not wanted to use full path, like Back In Time is doing when i right click that folder called "files" and select Add to Exclude.

[daveTheOldCoder]

Try /home/me/.AppName/files to exclude the folder and its contents, or /home/me/.AppName/files/* to exclude the folder's contents but not the (empty) folder.

.AppName/files and .AppName/files/* may work too, but they would also match folders with that pattern outside of /home/me.

When the path starts with a /, it's interpreted as an absolute path.

[slrslr]

thx, yes, this works: .AppName/files/* though this does not: */.AppName/files/* which is a bit confusing and a reason why i have created this issue, if this something that can be internally made working

[daveTheOldCoder]

I think the include/exclude patterns are simply passed along to the rsync command, so that command's behavior determines how they work.

[octohedron]

Would be nice to display this information in the exclude dialog

[buhtz]

Would be nice to display this information in the exclude dialog

You mean as a "help text"? For example a tool tip or something like this?

[octohedron]

I would make it more explicit, i.e. without having to look for any additional help or tooltip, something like this in the dialog.

Example: "node_modules/*" would exclude all node_modules folders in the system.

Or even better

There's no need to add anything before a folder to exclude it system wide, e.g. "node_modules/*" would exclude all node_modules folders in the system.