On Wednesday 10 February 2016 18:18:33 Nick Leverton wrote: > In article <201602100424.41617.gheskett@...>, > > Gene Heskett <trinity-users@...> wrote: > >On Wednesday 10 February 2016 02:54:50 Dr. Nikolaus Klepp wrote: > >> 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. > > > >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. > > Please excuse me asking: by Workspace, do you mean the numbered > desktops on Ctrl-1 Ctrl-2 etc, or is there some other TDE feature that > I've missed ? Assuming the former, the desktop number for each window > seems to be stored in the session entry for twin, not that for the > program itself. > > I don't know of any documentation for the feature, but I use "manually > saved" session option and things always restart on the right desktop. > > In the distant past, relying on logout to save session didn't always > work for me, or else would restore session once but then not again. > But that was way back in KDE3 days, and I've just stuck with the easy > option. > > Nick Well, unless froggy's magic twanger has been plucked, most of the r14.0.0.3 code base is still kde3.5. So unless someone has addressed it since the fork, that particular speed bump is probably still there. As for workspace 3 that I referred to, I have 10 such 'screens', and I usually have at least 4 of them with open terminals with multiple tabs on them. On workspace1 for instance, a 5 tab terminal runs, with tab 0 being used for a root copy of htop, with which I can find and destroy a runaway process. Tab 1 has a root tail -fn300 on /var/log/messages. Tab 2 is running in my home dir, and has a tail -fn50 log/fetchmail.log so I can sorta keep track of my network connection etc. Tab 3 ATM, has a tail -fn50 log/procmail.log but as long as procmail behaves itself, that can be shut down. I played with some of the procmail recipe's last evening, so I've been tracking how that is working. Next workspace has a 4 tab terminal running on it, with ssh -Y sessions live to each of my CNC machines scattered about the Ranchette. Theres 2 more workspaces with terminals running on them, for whatever. I normally run iceweasel on workspace 9, and kmail on workspace 10. The whatever category might be gaf, or pcb, or even qucs depending on what I'm attempting to do ATM. Boring isn't it. :( Cheers, Gene Heskett -- "There are four boxes to be used in defense of liberty: soap, ballot, jury, and ammo. Please use in that order." -Ed Howdershelt (Author) Genes Web page <http://geneslinuxbox.net:6309/gene>