Strange behaviour about file permissions

[Giova84]

If I uncheck "execute" under "Permissions" settings of a folder, i cannot copy/move/create files inside folders, and i cannot see present files (in this case the folder will result empty and with 0 KiB)

If I uncheck "read" and "write" (but keep the check on "execute"), instead i can copy and see files inside folders.

Look at attached screenshots.

hrev46154

[umccullough]

The "execute" permission on a directory determines whether the user can access the contents or navigate to it. This is standard for unix-based file permissions (which BeOS used, and Haiku also shares).

For further information: ​http://en.wikipedia.org/wiki/Filesystem_permissions#Traditional_Unix_permissions

[Giova84]

Thank you for the explanation and sorry for my ignorance :-)

[siarzhuk]

May be we should just rename "Execute" to "Browse" for the dialogs opened on folders?

[jscipione]

That would be confusing to people who understand Unix file permissions.

[siarzhuk]

Replying to jscipione:

That would be confusing to people who understand Unix file permissions.

Not agree. Those who can understand that "execute" on the folder is not "execute" but "browse" will never confuse if "browse property" will have the "browse" name. IMO they are just smart enough to be traped by such misunderstanding. And they are living in the console anyway. ;-)