10 Feb
2016
10 Feb
'16
12:25 p.m.
On Wednesday 10 February 2016 09:24:41 Gene Heskett wrote:
On Wednesday 10 February 2016 02:54:50 Dr. Nikolaus
Klepp wrote:
Why not just _try_, just for - I don't know - for heck's sake - doing
*exactly* what Nik suggested? You never know, it might work.
<quote>
I had to use "start with empty session" temporarily (for one or two reboots)
to get rid of some hikups.
</quote>
Lisi
Am Mittwoch, 10. Februar 2016 schrieb Gene
Heskett:
AKA turn it off, nuke those files in the session directory, restart and
reconfigure, turn it back on and restart again.
On Tuesday 09 February 2016 18:34:28 Lisi Reisz
wrote:
Hi Gene!
The terminal should be restored on the correct workspace, but sessions
are not overwritten, just saved anew. If I recall correctly, the
sessions are stored in ~/ .trinity/share/config/session, so you might
clean that directory, too. But first start with a clean session. On Tuesday 09 February 2016 23:10:08 Gene Heskett
wrote:
> On Tuesday 09 February 2016 14:36:21 Nick Leverton wrote:
> > In article <201602091426.58790.gheskett(a)shentel.net>et>,
> >
> > Gene Heskett <trinity-users(a)lists.pearsoncomputing.net> wrote:
> > >On Tuesday 09 February 2016 13:54:21 Dr. Nikolaus Klepp
> > > wrote: [...]
> > >
> > >> Hi Gene!
> > >>
> > >> Last time I used saved sessions to restore my workspace
> > >> after login, it worked flawless - but that's been more than
> > >> a year ago. But I also rember, I had to use "start with
> > >> empty session" temporarily (for one or two reboots) to get
> > >> rid of some hikups.
> > >>
> > >> Nik
> > >
> > >And where is that option? I don't recall seeing it when I
> > > walked thru it earler today. Are my cataracts getting that
> > > bad? :(
> >
> > In Control centre, it's in TDE Components / Session Manager.
> >
> > Nick
>
> Found it, was set for restore. Which is good but doesn't
> remember the workspace the restored stuff was running on.
>
> I note that most of the time, the restored term prompts do show
> the directory it was sitting in when I restarted it, causing
> that term & shell to be killed. So its remembering that, but not
> the workspace.
>
> Is that a bug? Or just hasn't been coded to do yet?
Have you tried Nik's suggestion and turned the restore off for a
couple of reboots?
Lisi
No I haven't Lisi. Does it not store a new list of stuff each time
as it shuts down when that is checked?
IDK.
Thanks Lisi.
Cheers, Gene Heskett Nik
looking at those files, I can't see a thing that looks like a workspace #
specifier. And they all carry a time stamp from the last restart, and a
long hashed from the *nix epoche time" extension to the name. Is there
documentation on this someplace the "unwashed" can read it?
And yet, kcalc alone is the only one that always re-opens on the same
workspace it was on so I think its possible. I may play with it once I
have an eye open simultaneously again.