sciteco/teco.ini, branch v2.5.2

introduced $SCITECOCONFIG env variable, and set different default for $SCITECOPATH on Windows

2014-11-24T06:46:01+00:00

 * $SCITECOCONFIG has been introduced, so have a macro-accessible location
   for the profile, buffer session etc.
   This is set to the program dir on Windows. That way, the config files
   will be found, regardless of the current working dir, but it may also
   be set up for Unix-like environments on Windows.
 * $SCITECOPATH defaults to the program dir + "/lib" now on Windows.
 * The default profile is now always called ".teco_ini". Also on Windows.
   Platform differences like this would need to be documented.
 * The sample teco.ini has been renamed to "sample.teco_ini" for clarity

allow setting the "*" register as an alternative to nEB

2014-11-22T18:52:47+00:00

this is more consistent with SciTECO's idea of abstract registers
and allows the currend buffer to be saved on the Q-Register stack.
This allows the idiom: [* ! ...change current buffer... ! ]*

added a buffer session module (session.tes)

2014-11-22T17:10:49+00:00

This is a simple and straight-forward implementation of
buffer sessions in SciTECO. A session is merely a SciTECO script
that opens files when executed (and restores properties).
The current session is identified by this script's filename in
Q-Register "session.path": ~/.teco_session by default.
Users may set "session.path" to manage different profiles.
An abstraction of session "names" is not provided. Users are expected
to hack these on their own.

For the common task of having one session per profile, the
"session.git" macro is provided. It set's up the current session
relative to the current Git repository.
This will create ".teco_session" files in the root of Git
repositories, that may be added to a global ignore pattern (or they
may even be versioned!)

renamed ED hook register to "ED" and protect ED hook executions

2014-11-20T05:17:39+00:00

SciTECO commands usually only take parameters from the stack that
they need. Without protecting the ED hook execution with brace operators,
additional arguments not consumed by the hook-dispatching command
are passed into the ED hook invocation. Also an ED hook macro could
leave additional values on the expression stack (by accident).
All of this may lead to undefined behaviour if ED hooks
are involved.

added first draft of new modular lexer system

2014-11-19T22:36:07+00:00

adapted sample teco.ini: margin setup must be done for every new document

2014-11-16T22:34:24+00:00

changed syntax for long Q-Register names: use [] brackets instead of {}

2014-11-01T23:06:28+00:00

this breaks many existing scripts, and means you may have to rebuild SciTECO
with ./configure --enable-bootstrap

The syntax of SciTECO might change in backwards-incompatible until
version 1.0 is released.

use 0,xED instead of ED#xED in teco.ini

2013-03-20T11:43:27+00:00

EM...$ command to read macro from file and execute immediately (just like "M")

2013-02-24T23:49:27+00:00

 * useful for using macro libraries

added some default function key macros

2013-02-22T00:18:06+00:00