AM/PM in Thunderbird -

[Patrick O'Callaghan]

On Wed, 2014-02-26 at 23:45 +0600, g wrote:
> > I've a feeling we're talking at cross purposes, but here goes:
> 
> not sure what you mean by "cross purposes", but, that is ok with
> me. ;-)
> 
> >> now that the s/n has dropped, and i have finished playing with
> >> '.bashrc', 'alias', and a script file, i submit the following.
> >
> > Don't know what "s/n" means, but never mind.
> 
> s/n = Signal to Noise ratio.
> 
> bob know what it means. :-)

As do I, now that you've said you meant "s/n ratio".

> > What do you mean you don't close them? KDE closes them when you
> > terminate the session. You'd have to take special measures to
>  > prevent this and I'm not sure it's even possible to do in a
>  > sensible way (i.e. retaining some way to access the terminal
>  > after KDE closes).
> 
> so that you will know, it is possible.
> 
> yes, when kde is closed, what ever was running is closed, unless
> there was a 'nohup' issued.
> 
> when i _logout_ from kde desktop, to 'switch user', 'suspend to
> disk', 'suspend to memory', 'restart', or 'shutdown', i do not
> close out what ever i have sitting open in 'task bar'.

Switching user and suspending do not log out. Shutdown and restart do.

> ie, open windows "top to bottom":
>   4 firefox windows and library, 6 terminals, 4 konqueror windows,
>   a bash shell started from konqueror, freecell, ksnapshot, system
>   monitor, 4 kwrite windows, disk utility, system settings, address
>   book, thunderbird, and wireshark.
> 
> when i logout of kde for any of above reasons, i _do_not_ close any
> windows. when i login to kde again, _all_ of above windows are
> reopended with out my opening them again.

When you logout or restart, you are *not* continuing the same processes.
Presumably you have configured the KDE session manager to reopen the
same apps as when you left the session. These are new processes which
attempt to continue where they left off, but they are being executed
from the pristine binaries and will not conserve transitory environment
state (unless they are written to do that).

> >> in each of the terminals, i have at least 2 tabs open. in each
> >> terminal, when in right most tab, everything works fine. for some
> >> reason, that i did not bother to figure out why, it does not work
> >> in other tabs.
> >
> > Can't think of a reason for that offhand, other than some kind of
>  > script bug.
> 
> 'script bug'?

A bug in the .bashrc init script.
> 
> To be more precise: if you run KDE from a desktop manager (KDM,
>  > GDM, whatever) then terminating KDE logs you out. If you run KDE
>  > by first logging into a terminal and executing startkde then yes,
>  > you can terminate the KDE session, fiddle with Shell variables,
>  > then run another KDE session, so strictly speaking you haven't
>  > logged out and the new KDE session will see the altered
>  > environment. However any terminals that were running *within* the
>  > KDE session have been terminated and have to be re-executed (with
>  > the now current environment) when you re-enter KDE.
> 
> not all true. see above.

I disagree. I invite you to list the process IDs of the running apps in
one of your sessions, close the session without restarting the system,
start a new session, then list the PIDs again. The two lists will show
different PIDs.

poc