Seeing I had a new version of emacs I bit the bullet and quit my old
sessions. And also rebooted, why not?
Something I have never noticed before: When I ran emacs again it pegged
a couple of cores at 100%, for a decent amount of time, worrying me. But
then it stopped. :whew: I restarted emacs anyway, just to be safe, have
a clean start.
On a different machine, before quitting I stopped to notice there was an
interestingly named buffer:
*Async-native-compile-log*
Huh. Emacs jumped on the async bandwagon??
-kb
P.S. I also had recently configured screen (where I usually run emacs)
to do its lockscreen. But how stupid. It is really more of a "lock
terminal", it doesn't require a password to reattach to a screen
session, which was my whole motivation, I sometimes have a root shell
persisting inside screen. Grrr.
_______________________________________________
Discuss mailing list
Discuss@driftwood.blu.org
https://driftwood.blu.org/mailman/listinfo/discuss
