--nextPart1466107.7hI6eeJ3Fg
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

El Lunes 17 Marzo 2008, Anders Lund escribi=C3=B3:
> Why? I expect the sm to start exactly the programs that was open when I
> left ;) (Then of course, I do not run the same session on different
> systems.)

I'm with Anders here, what seems to be logical is that if I saved the sessi=
on=20
in KDE4 with kwrite from KDE3 opened, when I want to restore the session, t=
he=20
logical thing is to restore kwrite from KDE3 and not from KDE4.

=46or "roaming users" (which anyways is not *by far* the normal case at all=
),=20
there's a solution of compromise: first try to run the command in the path=
=20
that was executing when saving ther session. if it doesn't exist, then=20
execute the first command in PATH, or the second etc.
So, basically add the saved path of the command to the beginning of PATH an=
d=20
then execute.

BTW, is there any chances this gets backported in KDE3? I'm using some KDE4=
=20
apps in KDE3 and I have the same problem.

=2D-=20
"The reasonable man adapts himself to the world; the unreasonable one
persists in trying to adapt the world to himself. Therefore all progress
depends on the unreasonable man." (George Bernard Shaw)

--nextPart1466107.7hI6eeJ3Fg
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)

iD8DBQBH3iizHxqR9mwfUxYRAj/yAJ0doeQwpIVE5YefVBuSLgbqK6aCngCghcLO
ElrCav+L/CDXdKQPjyoPyjM=
=zHGJ
-----END PGP SIGNATURE-----

--nextPart1466107.7hI6eeJ3Fg--