Hi Sean,

Just following up on our conversation in #debian-emacs before I hit
another busy week and forget.  I took a look at the upstream README.md
to better inform this bug, to not be totally ignorant.

https://github.com/vspinu/sesman/blob/master/README.md

I noticed that while upstream states that IDEs are the primary focus,
the project is a "Generic Session Manager for Emacs".  Given that it
can manage non-Emacs processes I wonder if it would be useful for
building custom non-IDE sessions for specific tasks.

If that seems like too much work then it seems like
'desktop-save-mode' from desktop.el (built-in) should be recommended
in the long description for users who just want something simple to
save their buffers when they quit and restore them when they start a
new session--this is the most basic form of session management.

It sounds like sesman can do a lot more, if only because it is
designed to save and restore multiple named states.  I suspect that it
has great utility when task switching between radically different
complicated projects.  So the two things I'd like to see are:

1) Very short differences between the built-in desktop.el and sesman
2) Info that would help a dev determine if sesman could be useful (or not)
   for their project outside of the CIDER, ESS, Geiser, Robe, SLIME context.

Thanks!
Nicholas

control: tag -1 +help +newcomer

Dear Nicholas,

I don't think it can do this!

Patches would be welcome.

Hi Sean,

Sorry for the delay--I've been utterly swamped with work, and have a
failing power supply.

Maybe it's using the networking definition of "sessions" as a list of
connections, and only manages these?  Conversely, by glancing at the
README I noticed that sesman has "contexts...for example
current-buffer, default-directory, and project-current".  This, and
that project title is "Generic Session Manager for Emacs" suggests
that sesman can at least save/restore these.

Maybe it's session support is limited to a single buffer?  If so, the
description could say something to the affect that other session
management packages such as the built-in desktop.el are more
appropriate for saving a collection of buffers as a session.

I have to defer to you on this one, because you're more familiar with
the package, and I don't anticipate having the time to dig into the
details.  Maybe forward this question upstream?

Regards,
Nicholas