Not logged in
Log in now
Create an account
Subscribe to LWN
LWN.net Weekly Edition for May 16, 2013
A look at the PyPy 2.0 release
PostgreSQL 9.3 beta: Federated databases and more
LWN.net Weekly Edition for May 9, 2013
(Nearly) full tickless operation in 3.10
It would be possible to make Emacs session-aware.
That could be fixed
Posted Sep 23, 2008 7:29 UTC (Tue) by nix (subscriber, #2304)
Hm, perhaps a shutdown/restart could appear to the Lisp code like all the
process sentinels signalling a process death/network disconnection,
something they have to deal with anyway... obviously you'd also want a
session-save-hook and session-restore-hook, so that things that *want* to
be aware of shutdown/restart can be. (And let's implement it with proper
serialization/deserialization of the in-core Lisp state, not with
unexec()! :) )
Posted Sep 23, 2008 15:00 UTC (Tue) by shapr (guest, #9077)
Posted Sep 23, 2008 15:14 UTC (Tue) by rlk (guest, #47505)
* Shell buffers (input and output history -- including input and output history of the shell, which isn't quite the same thing as the emacs idea of that)
* Command output buffers and other temporary buffers, including *scratch*
* Files that you're looking at that may get changed behind your back that you deliberately haven't reverted yet.
* The state of the lisp world
Obviously, emacs loses all of this if it crashes, but this in the context of choosing to reboot vs. suspend/resume. I'll take my chances on crashes, and I do save my work, but it's still more efficient to keep a session going as long as possible.
Copyright © 2013, Eklektix, Inc.
Comments and public postings are copyrighted by their creators.
Linux is a registered trademark of Linus Torvalds