How to use the KDE application link to start a console app in a specified working dir

[Salane KIng]

On Thursday 30 October 2003 10:57 pm, Salane KIng wrote:
> On Thursday 30 October 2003 12:45 am, Parzival Herzog wrote:
>
> > I am a Windows habituated person learning to use Linux and KDE, currently
> > I
 am having the following problem, and neither KDE docs nor Google can
> > shed any light on it:
> >
> > I am trying to automatically start the spambayes proxy server (a Python
> > script), at login. I thought that placing an entry in the
> > ~/.kde/Autostart
 directory would do the trick. So I created a "Link to
> > Application" in this directory. I tried several things as the "Command",
> >
> > 1, the full path to the python script that implemets the spambayes
> > server
 2, python (the full path to the script)
> > 3, a bash script containing a cd to the spambayes server working
> > directory
 (wherein it finds a configuration file) and the command (2)
> > above. 
> > In all of these cases the "Run in terminal" option is checked.
> >
> > Then I double click the link to test this. A terminal window briefly
> > appears and then disappears. (BTW, if I type command (1), or (2)  above
> > in
 a Konsole, the server always starts and there are no problems)
> >
> > I would like (a) to be able to have the terminal window not close on the
> > failure I describe above, so I can read the Python traceback and
> > possibly
 diagnose the problem; and (b) be able to set the working
> > directory that the server is started in on automatic start.
> >
> > I have tried using "-i" as a Terminal option, assuming that it would set
> > the bash -i (interactive) option, and thus bash would not terminate, but
> > this has no detectable effect.
> >
> > There seems to be no documentation or help tips whatsoever about the
> > Execute tab of this dialog, so what the "Panel Embedding" section means
> > is
 absolutely obscure, and what the "Terminal options" would be is also
> > unclear. So (c) I would like to know what these data in the dialog are
> > supposed to do.
> >
> > Can anyone help me to accomplish my goals, or point me to more detailed
> > documentation that might help in this case?
> >
> > Thanks, Parzival
> > ___________________________________________________
> > This message is from the kde mailing list.
> > Account management:  http://mail.kde.org/mailman/listinfo/kde.
> > Archives: http://lists.kde.org/.
> > More info: http://www.kde.org/faq.html.
>
> 
> I hate to say this but the do not close option is in kde
> 3.1.93(kde3.2alpha2) 
 under advanced options. I suppose that it could be
> in 3.1 but if you haven't found it it probably is not there. 3.1.93 is an
> alpha version of kde and still is a work in progress so beware of using in
> production or critical areas. I have been running it and I still get the
> occasional crash, but it works pretty good for an alpha.
> ___________________________________________________
> This message is from the kde mailing list.
> Account management:  http://mail.kde.org/mailman/listinfo/kde.
> Archives: http://lists.kde.org/.
> More info: http://www.kde.org/faq.html.
have you tried konsole option --noclose perhaps as an option command
___________________________________________________
This message is from the kde mailing list.
Account management:  http://mail.kde.org/mailman/listinfo/kde.
Archives: http://lists.kde.org/.
More info: http://www.kde.org/faq.html.