| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
* the Curses UI does that too
|
|
* the GTK UI shows the horizontal scrollbar by default,
while Scinterm doesn't.
Since showing them with Scintilla's default settings is
ugly but setting them up properly is costly and should
be decided by the user.
|
|
* this has long been broken in the GTK UI.
It must not be possible to let Scintilla react to mouse and
keyboard events since all side-effects on the buffer state
must be via the SciTECO language.
|
|
* the execution thread does not block the main thread (with
the main loop).
* therefore if SciTECO executes a long-running macro,
the UI stays "responsive".
* also this allows us to handle ^C interruptions.
This is part of the solution to #4 for GTK+ UIs.
* to speed up execution and avoid frequent UI redraws
(now that we run concurrently, there are even more redraws),
the view change is applied only after key presses.
* also we freeze all UI updates on the view during SciTECO's
key processing.
* Closing the window, requests a graceful execution thread
shut down. This may later be extended to allow programmable
window close-behaviour using a special function key macro
(e.g. mapped to the "Break" key).
|
|
|
|
* disable ED hook while exuting the "add" hook.
This avoids the "edit" hook being invoked recursively.
* the speed improvement was not measurable, but it also won't
hurt
|
|
* this fixes the CTRL+V command
* PDC_set_function_key() may be used to implement a
"shutdown" function key macro later on.
* interruptions via CTRL+C are not (easily) possible
in this port of PDCurses - similar to XCurses.
However, I may ask the author if this is possible.
|
|
* CTRL+C interruptions are now possible.
ncurses/win32 needs a noraw() (bug!?) and
the console_ctrl_handler for this to work.
* setting the window title is not possible on this port
* stdio output can be redirected, even in interactive mode.
Also, we can write to stdout/stderr even in interactive mode
without disrupting the terminal.
After endwin(), the user will see these messages (if they
haven't been redirected).
* there's one bug left:
the Scintilla cursor is not drawn correctly at the end of
lines.
* part of the solution to #4
|
|
* enabled via --with-interface=xcurses, so we can configure
it automatically via xcurses-config.
This also adds XCURSES_CFLAGS and XCURSES_LIBS.
* The X11 window class name is set to "SciTECO".
X11 resource overrides can currently not be set via
sciteco's command line. The user may use .Xdefaults though.
* interruptions via CTRL+C are currently not supported.
Apparently, XCurses also does send SIGINT in cbreak() mode.
An XCurses-specific hack would be cumbersome.
* ~InterfaceCurses() should probably be rewritten.
Curses cleanup should be completely in restore_batch() as
the destructor may be called after Curses-cleanup handlers.
E.g. isendwin() SEGFAULTs on XCurses when called from the
destructor.
|
|
this avoids some problematic includes, so we no longer have
to #undef interface.
Also it should speed up building a bit.
|
|
* requires a recent patch to Scinterm
* can be overwritten in SciTECO's build system via NCURSES_CFLAGS or
PDCURSES_CFLAGS.
* NCURSES_LIBS has also been introduced. The check for ncurses
will now use pkg-config if available.
* eases multiple builds with different Curses variants
(e.g. when cross-compiling for Windows)
* pass more toolchain variables into Scintilla build process (CC and RANLIB).
This should fix Cross-compiling Scintilla/Gtk
* Pass GTK cflags into Scintilla/Gtk build system.
|
|
* this was an issue at least in PDCurses/win32
|
|
* it now works as in the ncurses port: ^C during macro execution
interrupts just as SIGINT does; else it is read as a character.
* On Windows we need to register a special "console ctrl handler"
which is the analogue to a signal handler.
* It must be tested how ncurses/win32 and PDCurses/win32a behaves
in this regard. PDCurses/win32a is still actively maintained,
so we can also patch its source base.
* See #4
|
|
* relies on a patched version of Scinterm that allows you to
construct Scintilla objects, send messages etc. before Curses
is initialized.
The Scintilla and Scinterm submodules have been updated.
* This once and for all fixes batch mode and stdio redirections
in batch mode on all Curses platforms and operating systems.
* Fixes the ^C-does-not-interrupt bug on ncurses/UNIX.
See #4.
* On ncurses/UNIX we will still do a newterm()-initialization.
This allows us to keep stdout/stderr alone in case they are
redirected. This effectively allows redirecting SciTECO's
output into a file even in interactive mode.
ncurses/UNIX now behaves like, e.g. PDCurses/win32a and GTK+
in this regard.
* Curses environment variable handling fixed.
The environment registers are exported into the process environment
so that Curses environment variables can be set/modified by the
SciTECO profile.
* Use term.h for accessing terminfo now.
Explained set_window_title() limitations.
* fixed interruption via SIGINT. If the UI is waiting for user
input, SIGINT is effectively ignored instead of letting the
next character fail always.
* Updated sciteco(1) and sciteco(7): More options, environment variables
and signals documented. Also rewritten DESCRIPTION section
(different modes of operation).
|
|
* Scintilla was built as a .PHONY target, so we trigger its build
process always when we depend on scintilla.a.
The problem was that a real file (scintilla.a) was declared .PHONY
which meant that it was always considered updated by Make.
This triggered a relink of everything depending on scintilla.a.
Always. When doing a bootstrap build, this would always result
in rebuilding the symbols-*.cpp files, etc...
* Now the Scintilla build process will always be triggered,
but scintilla.a is handled like an ordinary target.
When we depend on scintilla.a our recipe will only be executed
if the recursive make for Scintilla actually did update scintilla.a
|
|
* the registers beginning with "$" are exported into sub-process
environments. Therefore macros can now modify the environment
(variables) of commands executed via EC/EG.
A variable can be modified temporarily, e.g.:
[[$FOO] ^U[$FOO]bar$ EC...$ ][$FOO]
* SciTECO accesses the global environment registers instead of
using g_getenv(). Therefore now, tilde-expansion will always
use the current value of the "$HOME" register.
Previously, both register and environment variable could diverge.
* This effectively fully maps the process environment to a subset of
Q-Registers beginning with "$".
* This hasn't been implemented by mapping those registers to
special implementations that updates the process environment
directly, since g_setenv() is non-thread-safe on UNIX
and we're expected to have threads soon - at least in the GTK+ UI.
|
|
* also added a warning about building on Windows
|
|
* it's now at Scintilla v3.5.6 and Scinterm v1.6
* the Curses tab-stop fix was removed from the sciteco-dev branch
since Mitchell cared about getting it upstream.
It is part of Scintilla v3.5.5 and Scinterm v1.6.
Scinterm built fine with Scintilla v3.5.6, so we're using the
newer release.
|
|
* expands to the value of $HOME (the env variable instead of
the register which currently makes a slight difference).
* supported for tab-completions
* supported for all file-name accepting commands.
The expansion is done centrally in StateExpectFile::done().
A new virtual method StateExpectFile::got_file() has been
introduced to pass the expanded/processed file name to
command implementations.
* sciteco(7) has been updated: There is now a separate section
on file name arguments and file name handling in SciTECO.
This information is important but has been scattered across
the document previously.
* optimized is_glob_pattern() in glob.h
|
|
* The unnamed buffer must be handled separately since the "lexer.test..." macros
assume that register "*" is non-empty.
Else it will be configured for some arbitrary lexer.
* this was a regression compared to v0.6.4
|
|
string formatting)
|
|
appending to "$"
* these operations are unsupported and there is no benefit
in ignoring them silently. It only confused the user.
|
|
working directory
* FG stands for "Folder Go"
* FG behaves similar to a Unix shell `cd`.
Without arguments, it changes to the $HOME directory.
* The $HOME directory was previously only used by $SCITECOCONFIG on Unix.
Now it is documented on its own, since the HOME directory should also
be configurable on Windows - e.g. to adapt SciTECO to a MinGW or Cygwin
installation.
HOME is initialized just like the other environment variables.
This also means that now, the $HOME Q-Register is always defined
and can be used by platform-agnostic macros.
* FG uses a new kind of tab-completion: for directories only.
It would be annoying to complete the FG command after every
directory, so this tab-completion does not close the command
automatically. Theoretically, it would be possible to close
the command after completing a directory with no subdirectories,
but this is not supported currently.
* Filename arguments are no longer completed with " " if {} escaping
is in place as this brings no benefit. Instead no completion character
is inserted for this escape mode.
* "$" was mapped to the current directory to support an elegant way to
insert/get the current directory.
Also this allows the idiom "[$ FG...new_dir...$ ]$" for changing
the current directory temporarily.
* The Q-Register stack was extended to support restoring the string
part of special Q-Registers (that overwrite the default functionality)
when using the "[$" and "]$" commands.
* fixed minor typos (american spelling)
|
|
out beyond empty arguments
* it was annoying not to be able to rub out anything with ^W if the current string
argument was empty.
* Now, the special file name and string argument handling for ^W is effective
only if the current argument is non-empty, else we fall back to the rub-out-command
behaviour.
* So now, if you press ^W in a string argument, it is rubbed out until empty and
on the next ^W press, the entire command will be rubbed out.
|
|
* the rubout/reinsert-word behaviour of misc. string arguments
is suboptimal for file name arguments as it depends on Scintilla's
word characters.
By default, the directory separators are not considered word
characters, but this could be changed by the user.
* The behaviour of ^W in file name arguments is now fixed and
independant from the Scintilla configuration:
It always rubs out or re-inserts one hierarchy level of the
file name.
|
|
|
|
As SciTECO can only edit regular files (or symlinks to regular files),
we can exclude directories from the list of files matched by <EB> glob
patterns.
|
|
* EN may now be used for matching file names (similar to fnmatch(3)).
This is used to check the current buffers file extension in the
lexer configuration macros instead of using expensive Q-Register
manipulations.
This halves the overall startup time - it is now acceptable even
with the current amount of lexer configurations.
* EN may now be used for checking file types.
session.tes has been simplified.
* BREAKS macro portability (EN now has 2 string arguments).
* The Globber class has been extended to allow filtering of
glob results by file type.
|
|
* these are still not all languages supported by Scintilla.
scite2co.lua does not do a good job of generating styles when
SciTE's property files use hardcoded colors/fonts.
This commit only includes reasonably good conversion results.
The remaining languages need some additional manual labor.
* Even these lexers are not perfect and should be revised by comparing
them with SciTE's properties.
* So many lexers make the "lexer.auto" macro too slow.
We need some optimization. E.g. the search-command optimization
described in TODO, or an extended EN command for globbing manually
specified file names.
|
|
* they are updated with the results of scite2co.lua
This makes it easier in the future to update lexer settings
based on the property files of new SciTE releases.
|
|
SciTE properties files
|
|
|
|
|
|
minimum version
* it was necessary to increase the upstream version so I could
upload new versions to launchpad while debugging PPA build issues.
* ChangeLog finalized for v0.6.4
* SciTECO requires at least libglib v2.28 (but that's only a guess)
|
|
* it also sets the compatibility level to 7 which was required
when building for Ubuntu Lucid. This version cannot be supported
however since its libglib version is too old.
|
|
package is built
* you no longer have to make an entire clean when e.g. uploading
for another Ubuntu release. Therefore, the source tar ball is
preserved (it must be the same for all packages with the same
upstream version).
* also try to extract the SciTECO version from the ./configure script
instead of hardcoding it in ./distribute
|
|
template base class constructors
* v4.4 is still officially supported by SciTECO (see INSTALL)
* Ubuntu Lucid appears to use v4.4 by default and lucid is till
supported by PPA. So this should fix building SciTECO in its PPA
for Ubuntu Lucid.
|
|
* If TERM is set but wrong, it might still fail. Errors are reported now.
* If $TERM is unset or empty, we refuse to start the interactive mode.
Unfortunately, we cannot easily let curses decide this since
newterm() does not work as expected.
* However this solution should be quite good: Either $TERM is empty - then
batch mode will work but not interactive mode.
Or it is not empty, then it is checked by the first call to newterm()
when initializing batch mode.
The chance of starting up interactive mode with a wrong $TERM
or in head-less environments is now quite low.
* This is most likely responsible for the PPA build issues.
|
|
expression stack
this was probably a regression from d94b18819ad4ee3237c46ad43a962d0121f0c3fe
and should not be in v0.5.
The return value of Expressions::find_op() must always be checked since
it might not find the operator, returning 0 (it used to be 0).
A zero index pointed to uninitialized memory - in the worst case it
pointed to invalid memory resulting in segfaults.
Too large indices were also not handled.
This was probably responsible for recent PPA build issues.
Valgrind/memcheck reports this error but I misread it as a bogus warning.
I took the opportunity to clean up the ValueStack implementation and
made it more robust by adding a few assertions.
ValueStacks now grow from large to small addresses (like stack data
structures usually do).
This means, there is no need to work with negative indices into the
stack pointer.
To reduce the potential for invalid stack accesses, stack indices are
now unsigned and have origin 0. Previously, all indices < 1 were
faulty but weren't checked.
Also, I added some minor optimizations.
|
|
|
|
|
|
|
|
* allows us to link against PDCurses/win32a statically.
It requires additional Windows DLLs (gdi32 and comdlg32) and since
there's no PDCurses configuration mechanism, it is easiest to set
the PDCurses linker flags using a PDCURSES_LIBS env variable.
* This is only possible since Scintilla links statically, we do the
linking of the binary and can provide the linker flags.
It is still not possible to overwrite the CFLAGS used for PDCurses
without modifying the Scinterm Makefile.
* Using PDCURSES_LIBS we can get rid of --with-interface=emcurses since
if library checks fail with EMscripten, we can simply define
PDCURSES_LIBS="-lpdcurses"
|
|
Unfortunately, I cannot really test this curses port
since it is not supported by Windows 2000 (missing AttachConsole() API)
and it does not run very well in Wine.
Under Wine, it does not require the LINES and COLS variable to be set.
However, endwin() and the refresh later on result in a very unusable
state of operation. I cannot currently check whether this is true on
Windows XP or later.
|
|
If there was a rubbed out command line and you tab completed
a file name in a string argument (TAB in ^G mode), the immediate
editing modifier was automatically reset.
This still happens if nothing could be tab completed and you
type a few characters and try to complete again (since ^G mode
will be reset). If this feature is used often, the user should perhaps
define a function key as ^G^I^G.
|
|
|
|
|
|
* Automake was trying to overwrite the submodule Scintilla
(that should be distributed) with the local copy of Scintilla
(perhaps because the directory had the same name).
Instead, we now copy the submodule Scintilla manually into
the distribution directory.
|
|
* fnkeys.tes has been updated to enable the command line
editing macros (cursor keys, etc.) only in the "start" state.
This avoids the annoying effect of inserting the macros
into string arguments where they have no effect and must be
rubbed out again.
|
|
|
