>On Tuesday 27 December 2005 11:45, you wrote:
>> > - XDG_DATA_DIRS. this has already caused problems for us with the
menu
>> >spec in that it can't be changed within a session,
>>
>> Why would you want that?
>
>because they are set wrong.
That's the cause that needs fixing then. The rest is fixi
On Tuesday 27 December 2005 11:45, you wrote:
> > - XDG_DATA_DIRS. this has already caused problems for us with the menu
> >spec in that it can't be changed within a session,
>
> Why would you want that?
because they are set wrong. so the user has to set up the env var then log
out, log back in .
> - XDG_DATA_DIRS. this has already caused problems for us with the menu
>spec in that it can't be changed within a session,
Why would you want that?
>can't be changed by
>installing a new desktop (think of multiple desktops on the same
system)
Each desktop startup sequence can adjust it accordi
hi all...
in the spirit of keeping this process moving, can we have an update on where
the various projects are with regard to vetting the drafts of the community,
public and FD.o documents within their projects for adoption?
as for KDE, we've discussed it on our KDE eV list and seem to have ar
hi philip..
before i comment on the email and spec itself (which i do below), we need to
ensure that we don't go at it back-asswards (yet again). instead of trying to
posit a standard at the umbrella level and then getting everyone to implement
it (a pathway to and from failure), standard possi
On most platforms, Desktop configuration management is ugly. Yet it's a
feature that is often requested. The platform that implements the most
used desktop configuration management is Microsoft Windows with it's
Group Policy features*. These features also allow for "Remote" Desktop
Configuration Ma
