I do customer support and I shift from one problem to another problem and then back to the first problem.
Is it possible to save the current state of emacs which includes the buffers in particular and maybe the "register" values (when I do point-to-register) to a file. Then clear the state, work on a new problem, save the new state at that time. Then be able to go back and restore the first state?
Utopia would each of these states to be saved in its own individual file.
I've been told of a packaged named "windows" that does this but I can't find it because the name gets too many hits.
On Wed, Sep 7, 2011 at 11:02 AM, Perry Smith <pedz...@gmail.com> wrote: > I do customer support and I shift from one problem to another problem and > then back to the first problem.
> Is it possible to save the current state of emacs which includes the > buffers in particular and maybe the "register" values (when I do > point-to-register) to a file. Then clear the state, work on a new problem, > save the new state at that time. Then be able to go back and restore the > first state?
> Utopia would each of these states to be saved in its own individual file.
> I've been told of a packaged named "windows" that does this but I can't > find it because the name gets too many hits.
On Wed, Sep 7, 2011 at 11:40 AM, Jai Dayal <dayals...@gmail.com> wrote: > I think this could be accomplished rather easily with screen (in the > terminal type "which screen" to see if it's installed).
> It will change a few key strokes, but nothing major.
> Good thing is about screen, is when you're disconnected, you can ssh back > in and re-attach to the screen and everything is there.
> On Wed, Sep 7, 2011 at 11:02 AM, Perry Smith <pedz...@gmail.com> wrote:
>> I do customer support and I shift from one problem to another problem and >> then back to the first problem.
>> Is it possible to save the current state of emacs which includes the >> buffers in particular and maybe the "register" values (when I do >> point-to-register) to a file. Then clear the state, work on a new problem, >> save the new state at that time. Then be able to go back and restore the >> first state?
>> Utopia would each of these states to be saved in its own individual file.
>> I've been told of a packaged named "windows" that does this but I can't >> find it because the name gets too many hits.
Perry Smith <pedz...@gmail.com> writes: > I do customer support and I shift from one problem to another problem > and then back to the first problem.
> Is it possible to save the current state of emacs which includes the > buffers in particular and maybe the "register" values (when I do > point-to-register) to a file. Then clear the state, work on a new > problem, save the new state at that time. Then be able to go back and > restore the first state?
> Utopia would each of these states to be saved in its own individual > file.
> I've been told of a packaged named "windows" that does this but I > can't find it because the name gets too many hits.
It's called "desktop". Try M-x desktop-save and M-x desktop-read
On Wed, 2011-09-07 at 10:02 -0500, Perry Smith wrote:
> I do customer support and I shift from one problem to another problem and then back to the first problem.
> Is it possible to save the current state of emacs which includes the buffers in particular and maybe the "register" values (when I do point-to-register) to a file. Then clear the state, work on a new problem, save the new state at that time. Then be able to go back and restore the first state?
> Utopia would each of these states to be saved in its own individual file.
> I've been told of a packaged named "windows" that does this but I can't find it because the name gets too many hits.
> Thank you,
> pedz
Hi,
It sounds like you're looking for the package Workgroup for Windows. It
provided the features you're looking for. Here are some URLs:
> I do customer support and I shift from one problem to another problem and then back to the first problem.
> Is it possible to save the current state of emacs which includes the buffers in particular and maybe the "register" values (when I do point-to-register) to a file. Then clear the state, work on a new problem, save the new state at that time. Then be able to go back and restore the first state?
> Utopia would each of these states to be saved in its own individual file.
> I've been told of a packaged named "windows" that does this but I can't find it because the name gets too many hits.
I also recommend screen. We do some home-automation things via computer, so
when things go wrong its handy to just switch to the relevant screen which is
right in the state I need to quickly fix the problem.
.Tami
.signature: syntax error at line 1: `(' unexpected
> I think this could be accomplished rather easily with screen (in the
> terminal type "which screen" to see if it's installed).
> It will change a few key strokes, but nothing major.
> Good thing is about screen, is when you're disconnected, you can ssh back in
> and re-attach to the screen and everything is there.
> http://www.slac.stanford.edu/grp/cd/soft/epics/extensions/iocConsole/... > On Wed, Sep 7, 2011 at 11:02 AM, Perry Smith <pedz...@gmail.com> wrote:
> > I do customer support and I shift from one problem to another problem and
> > then back to the first problem.
> > Is it possible to save the current state of emacs which includes the
> > buffers in particular and maybe the "register" values (when I do
> > point-to-register) to a file. Then clear the state, work on a new problem,
> > save the new state at that time. Then be able to go back and restore the
> > first state?
> > Utopia would each of these states to be saved in its own individual file.
> > I've been told of a packaged named "windows" that does this but I can't
> > find it because the name gets too many hits.
> > Thank you,
> > pedz
On Thu, 2011-09-08, Tami wrote:
> On 2011 September 7 Jai Dayal wrote:
>> On Wed, Sep 7, 2011 at 11:02 AM, Perry Smith <pedz...@gmail.com> wrote:
>> > I do customer support and I shift from one problem to another problem and
>> > then back to the first problem.
>> I think this could be accomplished rather easily with screen (in the
>> terminal type "which screen" to see if it's installed).
>> It will change a few key strokes, but nothing major.
>> Good thing is about screen, is when you're disconnected, you can ssh back in
>> and re-attach to the screen and everything is there.
> I also recommend screen. We do some home-automation things via computer, so
> when things go wrong its handy to just switch to the relevant screen which is
> right in the state I need to quickly fix the problem.
And I recommend it too. It's well worth learning if you're doing
*anything* Unix-related where you jump between tasks and hosts.
I keep one (named) screen session per task I'm doing at work; typically
two or three active and half a dozen more on the backburner.
You'll have to run Emacs in terminal mode though if you want to
combine them. If you're (like me) very attached to X11 Emacs, you may
not like that. Myself, I don't keep much state in Emacs itself --
Emacs does text editing and screen holds the various shells where most
of my valuable state is.
/Jorgen
-- // Jorgen Grahn <grahn@ Oo o. . .
\X/ snipabacken.se> O o .
