On 2019-03-15 02:52:33 Dr. Nikolaus Klepp wrote:
> Anno domini 2019 Thu, 14 Mar 22:40:38 -0500
>
>  J Leslie Turriff scripsit:
> > On 2019-03-14 20:15:13 Michael wrote:
> > > On Thursday 14 March 2019 06:26:16 pm J Leslie Turriff wrote:
> > > > On 2019-03-11 04:12:29 Dr. Nikolaus Klepp wrote:
> > > > > Anno domini 2019 Sun, 10 Mar 11:16:03 -0500
> > >
> > > .> >  J Leslie Turriff scripsit:
> > > > > > On 2019-03-10 10:35:32 BorgLabs - Kate Draven wrote:
> > > > > > > On Sunday 10 March 2019, J Leslie Turriff wrote:
> > > > > > > >       Is there a way to make TDE aware of running non-Trinity
> > > > > > > > applications so that they can be resurrected after
> > > > > > > > Logout/Login? I have at least one X11-based application (X2 -
> > > > > > > > The Programmer's Editor) that I use extensively, and it would
> > > > > > > > be nice if it could remember across Logout/Login events.
> > > > > > > >       I'm wondering if something like a DCOP wrapper might do
> > > > > > > > the job?
> > > > > > >
> > > > > > > Load the application into your autostart dir.
> > > > > > > /home/foo/.trinity/autostart
> > > > > > > Also, check the program's setting to see if it has an autostart
> > > > > > > feature.
> > > > > >
> > > > > >   Yes, that would work if I wanted it to start at every login,
> > > > > > not just if it was running when I logged out...
> > > > >
> > > > > Once upon a time there was a little kingdom where all applications
> > > > > held the X11 standards high and the grand master of session
> > > > > management called
> > > >
> > > >       So I guess you're saying that there's no way to get TDE to
> > > > notice my X2, then.
> > >
> > > You can use the autostart dir [1], but you'll need to do the work
> > > yourself. You could add a wrapper to starting X2 and a script in the
> > > autostart dir. Or better would be a check script in the shutdown dir
> > > (if it exists) and a corresponding script in the autostart dir.
> > >
> > > Here's some out of context code from something else, hack-and-slash as
> > > needed.
> > >
> > > #!/bin/bash
> > > /path-to-X2/X2
> > > Pid=`pgrep -f /path-to-X2/X2`
> > > if [ "$Pid" != "" ] ; then
> > > #  echo Already running...
> > > #  ps "$Pid"
> > >   touch /home/foo/.trinity/apps-to-restart/X2
> > >   exit
> > > fi
> > >
> > > In any event, what you want can be done, it just might be painful.
> > >
> > > Best,
> > > Michael
> > >
> > > [1] Mine seems to be called:  /home/michael/.trinity/Autostart
> >
> > 	You're apparently misunderstanding what I'm looking for.  I don't want
> > this program to Always start when I login, only when it was running at
> > the time that I previously logged out.  That's why I wondered if some
> > sort of DCOP wrapper might be appropriate.
> >
> > Leslie
>
> As your editor is not xsession-aware you have to wrap it some shell script,
> that just saves the state of x2 in the form of commandline invocation in a
> file when it's close due to TDE shutdown. So there is no invocation of X2
> when no X2 was open when TDE closed the session. At TDE login you execute
> that file with invocations and be happy. Sure, you have to manage some
> stuff like which desktop to put it, window placement etc. but that's not
> that complicated.
>
> Nik

	Yes, but what to put in that wrapper?  That's what my original question was.

Leslie