> Did you install the executables afterward, or did you test in the test shell? In case you installed the executables, can you please explain how you did it? I couldn't find out how.
I used the test shell and the GUI, which opens using deja-dup-preferences inside of that shell to add the path in the first place.
> If you used the test shell, that might be "normal": I noticed that when testing things in the test shell, using the current revision 1570 (my patch has nothing to do with it), neither the trash nor the user's special directories are found, i.e.
> Environment.get_user_special_dir(UserDirectory.MUSIC)
> returns an empty string
Oh. I was not aware of this. If this is the case, we need to find another way to test this.
> If this non-support of special directories is indeed, as I understand it, a bug in the test shell, and if it is not beyond my abilities, I would be happy to try and fix it.
Feel free, but do not put to much effort into this, because we will need to migrate the test shell to another command someday. See bug #1624861 which itself turned out to be too hard for me to fix it.
> Did you install the executables afterward, or did you test in the test shell? In case you installed the executables, can you please explain how you did it? I couldn't find out how. preferences inside of that shell to add the path in the first place.
I used the test shell and the GUI, which opens using deja-dup-
> If you used the test shell, that might be "normal": I noticed that when testing things in the test shell, using the current revision 1570 (my patch has nothing to do with it), neither the trash nor the user's special directories are found, i.e. get_user_ special_ dir(UserDirecto ry.MUSIC)
> Environment.
> returns an empty string
Oh. I was not aware of this. If this is the case, we need to find another way to test this.
> If this non-support of special directories is indeed, as I understand it, a bug in the test shell, and if it is not beyond my abilities, I would be happy to try and fix it.
Feel free, but do not put to much effort into this, because we will need to migrate the test shell to another command someday. See bug #1624861 which itself turned out to be too hard for me to fix it.
Best Regards
Vej