Thanks for your advice, I wondered about that. The only thing I can't
figure out now is why does the above script in all situations *but*
the ~/Desktop case. When I find out I'll post it here.
--
NAUTILUS_SCRIPT_CURRENT_URI is set to $HOME when executing scripts from desktop
https://launchpad.net
Mmmhh... I have the weirdest thing : I tried your zenity script and it
works !
Displays "file:///home/username/Desktop" as expected.
Apparently its my script whose buggy :
#!/bin/bash
cd $NAUTILUS_SCRIPT_CURRENT_URI
exec gnome-terminal
But it works for every single directory I tried *except
I use Dapper 6.06 (dist-upgraded from 5.10).
> Do you use the option to have your user directory as desktop?
What option are you referring to exactly ? I don't recall changing
such a setting ... but
maybe its an old setting from a previous version of Ubuntu (I think I
dist-upgraded twice without
Public bug reported:
Binary package hint: nautilus
When I execute a nautilus script via the context menu by right-clicking
on the desktop, nautilus sets the variable NAUTILUS_SCRIPT_CURRENT_URI
to the value $HOME.
Shouldn't it be $HOME/Desktop instead ?
This would be more sensible IMHO.
For in
Something else : when the focus is on the list and the user types, an
embedded real-time search box appears. I beleive that feature should be
deactivated in this context.
--
Alt-F2 launcher behaves annoyingly
https://launchpad.net/bugs/49305
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu
By "it disappears" I mean that the list updates itself as a complete
list again, which I find very confusing...
--
Alt-F2 launcher behaves annoyingly
https://launchpad.net/bugs/49305
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
Public bug reported:
Binary package hint: nautilus
Sorry for the unclear bug title, I'll try to explain this annoying bug
as simply as I can.
The new Alt-F2 launcher in Gnome 2.14 (on Dapper) presents a list of
"known applications" under the command edit box. This list behaves
incorrectly and /
Public bug reported:
Binary package hint: gnome-screensaver
gnome-screensaver misinterprets arbitrary clock changes as being periods
of inactivity. Hence, when changing the clock in the forward direction
for more than the configured timeout, the screensaver launches.
This is a rather minor bug,