Restoring files in their tabs after closing SciTE with open files

713 views
Skip to first unread message

RichardOnRails

unread,
Nov 20, 2007, 2:34:00 AM11/20/07
to scite-interest
Hi,

I just read the SciTE documentation to get a tab bar to open all the
time. And draging file-names from Windows Exploer to SciTE Version
1.72 has opened them in separate tabs.

When I save the session and then close/open SciTE, I get a list of the
names of files that were open when I last closed SciTE. I expected it
would restore the previous session with each file opened in it's
respective tab.

So I checked the documentation again and found save.recent=1, which I
added to the PLAT_WIN section of Ruby.properties (since I use SciTE
exclusively for editing/running .rb files). This didn't seem to do
anything.

Any ideas?

Thanks in Advance,
Richard

maciejr

unread,
Nov 20, 2007, 9:12:25 AM11/20/07
to scite-interest
Did you try "save.session"? Have a look at:
http://scintilla.sourceforge.net/SciTEDoc.html

You seem to be running an older version of SciTE (should be 1.74 atm),
so you may encounter already-fixed bugs and behaviour different from
the current docs.
It is probably better to put your custom settings in "User options" or
you might loose them when you upgrade SciTE.

Maciej.

RichardOnRails

unread,
Nov 20, 2007, 7:51:23 PM11/20/07
to scite-interest
Hi,

I'm running 1.72. I'll get the latest version.

I did try to save session, but when I opened the session in a new
instance of SciTE, only a path to the session members was displayed.
Their content in separate tabs is what I expected but failed to
receive.

Regards,
Richard

RichardOnRails

unread,
Nov 20, 2007, 8:12:03 PM11/20/07
to scite-interest
Hi,

I installed ver. 1.74, saved a session, opened a new instance and
loaded the session.

Again, I got a list of filenames in the session. BUT, this time, I
double-clicked one of the names and, voila, the tabbed files' contents
appeared.

Problem solved! Thank you very much for the encouragement to try the
latest version, though I suspect that double-clicking a session item
is the key issue.

Best wishes,
Richard

On Nov 20, 9:12 am, maciejr <maciej.radziejew...@gmail.com> wrote:
Reply all
Reply to author
Forward
0 new messages