Sure. I use --bind mounts to link working directories on various SSDs to a common location that gets backed up frequently. The bind mounts are preferable to symlinks so that backups of the common location (backed up onto slower HDD storage) execute correctly---traversing symlinks is not a reasonable option for me since each of those working directories makes extensive use of symlinks to save space, and dereferencing all of those would replicate a bunch of data, making backups much slower and data restores essentially impossible.
In my case, having a bunch of ".Trash-1000"s hiding is problematic. I work around it currently by making judicious use of "locate" and "find". For me, just having "delete" direct-delete the files---like what happens when you delete a file within a symlinked folder on a different FS---instead of moving them to a ".Trash-1000" folder would be much better, but I can't speak for everyone on this.
Sure. I use --bind mounts to link working directories on various SSDs to a common location that gets backed up frequently. The bind mounts are preferable to symlinks so that backups of the common location (backed up onto slower HDD storage) execute correctly- --traversing symlinks is not a reasonable option for me since each of those working directories makes extensive use of symlinks to save space, and dereferencing all of those would replicate a bunch of data, making backups much slower and data restores essentially impossible.
In my case, having a bunch of ".Trash-1000"s hiding is problematic. I work around it currently by making judicious use of "locate" and "find". For me, just having "delete" direct-delete the files---like what happens when you delete a file within a symlinked folder on a different FS---instead of moving them to a ".Trash-1000" folder would be much better, but I can't speak for everyone on this.
In any case, it looks like Rodrigo Silva also has some relevant comments in the bugzilla site linked earlier (https:/ /bugzilla. gnome.org/ show_bug. cgi?id= 604015).