Is there some magical combination of options that will cause SciTE to
maintain a session [file] like (say) VS would? That is, if I load a
session explicitly, add and/or remove some files, and then exit Scite,
the next time that session is loaded it comes up with the updated set?
Clearly SciTE *could* recall (by file name) that it currently has a
session loaded, and be able to rewrite that session file at exit...
but it seems that whatever "auto" portions of session functionality
that do exist do it at the level of an unnamed file set, rather than
"symbolically"?
Possibly something like save.session=2 could enable this style of
operation?
Robert Roessler
[EMAIL PROTECTED]
http://www.rftp.com
_______________________________________________
Scite-interest mailing list
[email protected]
http://mailman.lyra.org/mailman/listinfo/scite-interest
