Sessions are very useful to have all files open at the same
place on next load. However, the project is not reloaded
(Cute 0.2.5) and so things like build do not work. Wouldn't it
make sense to save the project in the session as well?
Logged In: YES
You have to set the build, go and compile command in the
project options dialog.
Why saving projects in sessions? Projects are a replacement
for session. They can save more information at once.
Logged In: NO
Projects seem only to save information about which files are part
of a project and what build commands, etc. can be used. A
sessions seems to store which files are actually open and where
the cursors are, etc. These seem complimentary to me.
If I have understood correctly, then I was suggesting that a
reference to a project be stored in the session, so that the
project settings could be restored by reloading the project that is
referred to in the session. It seems currently, that I have to load
a session and then open a project as two steps.
It is possible to define a new project load function in the
CUTE/Python API and load the project when opening a session.