kio_giobridge IO slave
kevin.krammer at gmx.at
Sun Jan 6 16:03:26 GMT 2008
On Sunday 06 January 2008, Stephan Kulow wrote:
> Am Samstag 05 Januar 2008 schrieb Kevin Krammer:
> > I'd rather have this as an environment variable or a config entry, with a
> > preference on the config entry since environment variables basically
> > require that the users know which shell config files are sourced by their
> > shell in non-interactive mode (when startkde runs) and interactive mode
> > (when they have a shell in Konsole).
> And you don't think distributions can set environment variables?
Of course they can and so do admins or even users.
However, experience shows that environment variables can lead to certain user
support problems, e.g. environment for interactive shells is OK (and this is
what users usually check) while the one for the session is not (e.g .bashrc
The environment variable approach has the advantage that one can subject a
single application to a different environment on demand, but on the other
hand has the disadvantage of being unchangable for anything already running,
e.g. no switching through GUI without session restart.
> I don't
> see how this makes "smb:/ doesn't work" any easier to track.
I think this is a different issue. The one discussed in this subthread is
about switching between "native" KIO slaves and bridged GIO access, for
example for the purpose of tracking down the cause of a problem (whether the
problem is in the GIO based stack or the application or server itself)
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 189 bytes
Desc: This is a digitally signed message part.
More information about the kde-core-devel