aboutsummaryrefslogtreecommitdiff
AgeCommit message (Collapse)AuthorFilesLines
2016-04-22build: change lpeg into lua integrationMarc André Tanner1-14/+7
Instead of compiling lpeg separately and then copying the object files into the lua source directory, copy the lpeg source files into the lua build tree and build it together.
2016-04-22build: clean up make local/standalone implementationMarc André Tanner2-17/+9
Run configure script for all targets instead of fiddling with Makefile variables directly.
2016-04-21vis-lua: allow selection modification by assigning to cursor.selectionMarc André Tanner2-1/+10
2016-04-21vis-lua: implement vis:message(msg)Marc André Tanner2-7/+18
2016-04-21vis-lua: also accept a range as argument for file:delete and file:contentMarc André Tanner2-14/+34
2016-04-21vis: also show user registered :-commands in :help outputMarc André Tanner1-4/+6
2016-04-21vis: list usable symbolic keys in :help outputMarc André Tanner1-1/+76
2016-04-21test: update to include lua based testsMarc André Tanner1-9/+6
2016-04-21vis-lua: add vis:command_register to map a Lua function to a :-commandMarc André Tanner2-0/+36
The following registers `:foo` as a command which prints a few things to stdout: vis:command_register("foo", function(argv, force, win, cursor, range) for i,arg in ipairs(argv) do print(i..": "..arg) end print("was command forced with ! "..(force and "yes" or "no")) print(win.file.name) print(cursor.pos) print(range ~= nil and ('['..range.start..', '..range.finish..']') or "invalid range") return true; end)
2016-04-21vis-lua: add utility function to push a Filerange onto the Lua stackMarc André Tanner1-11/+15
2016-04-21vis: add infrastructure to register custom :-commandsMarc André Tanner5-1/+59
2016-04-21vis: do not lazy allocate :-commandsMarc André Tanner3-10/+15
The built in commands should always be available.
2016-04-21map: add map_free_full utility functionMarc André Tanner2-0/+16
2016-04-20vis-lua: load files from directory specified with ./configure --sharedir=DIRMarc André Tanner2-6/+9
Close #231
2016-04-20vis-lua: trigger start event after ui has been initializedMarc André Tanner5-2/+14
2016-04-20vis: handle termination from within win_open event gracefullyMarc André Tanner2-12/+12
2016-04-19vis: add :set horizon optionDavid B. Lamkins4-4/+24
Can be used to specify the number of bytes before the visible area to consider for syntax highlighting. Defaults to 32K for now, whereas before it was 16K.
2016-04-19vis: add an unsigned option type for :set commandMarc André Tanner2-1/+4
2016-04-19test: add test for :wq in normal mode with multiple cursorsMarc André Tanner1-5/+10
Close #276
2016-04-19vis: add actions for prev/next character motions within the same lineMarc André Tanner1-0/+12
For now they are not mapped to any key by default, but can be enabled with: :map! normal l <cursor-line-char-next> :map! normal h <cursor-line-char-prev>
2016-04-19Fix vis-test git submodule integrationMarc André Tanner2-2/+2
2016-04-19Integrate vis-test git submoduleMarc André Tanner4-4/+21
2016-04-18vis-lua: strip relative paths from package.{path,cpath}Marc André Tanner1-0/+41
Allthough the default paths should take precedence we do not want to execute arbitrary code from the current working directory.
2016-04-18vis-lua: cleanup lua package.path handlingMarc André Tanner1-43/+29
2016-04-18vis: use internal file to show lua errorsMarc André Tanner3-6/+9
This means no event handlers are run for it, hence there is no chance for recursive errors.
2016-04-18vis: do not run event handlers for internal filesMarc André Tanner1-3/+3
Should have been part of f50465312dbb7e8fcb2409aa691d1aea7a43c466.
2016-04-18text: when saving also fsync(2) the destination directory after rename(2)Marc André Tanner1-1/+17
2016-04-17Mention #vis-editor IRC channel in READMEMarc André Tanner1-0/+3
Close #270
2016-04-17Mention slmenu(1) in READMEMarc André Tanner1-1/+3
2016-04-17vis: indicate primary cursor by using a different color instead of blinkingMarc André Tanner3-6/+3
Blinking caused more problems (#251, #202) than it solved. Blank cells were especially problematic.
2016-04-17vis: remove mapping from ' ' to <Space>Marc André Tanner1-1/+1
This reverts part of bd1d849b2033b04a372542c59d458d4f8279c937 just use a literal space within your key mappings. Close #280
2016-04-17sam: except for visual mode, apply :w to whole fileMarc André Tanner1-16/+57
Also in visual mode, warn if :w is not forced by ! because the file will be reduced to the active selection.
2016-04-17text: add infrastructure to save non-contiguous rangesMarc André Tanner2-113/+199
2016-04-16vis-lua: add vis.mode propertyMarc André Tanner2-0/+6
2016-04-16vis-lua: update API documentaiton in READMEMarc André Tanner1-1/+3
2016-04-16vis-lua: add cursor.selection propertyMarc André Tanner2-0/+17
2016-04-16vis-lua: add window.cursors[] arrayMarc André Tanner2-0/+39
2016-04-16vis-lua: add window.cursors_iterator functionMarc André Tanner2-0/+25
2016-04-16vis-lua: add cursor.number propertyMarc André Tanner2-0/+6
2016-04-15vis-lua: change cursor object implementationMarc André Tanner2-22/+15
2016-04-15view: add view_cursors_place(cursor, line, col) functionMarc André Tanner2-0/+8
2016-04-15view: add view_cursors_col functionMarc André Tanner2-0/+7
2016-04-15view: add view_cursors_line functionMarc André Tanner2-0/+7
2016-04-15vis-lua: add file.size to return file size in bytesMarc André Tanner2-0/+6
2016-04-15vis-lua: add file.newlines to detect type of new linesMarc André Tanner2-0/+17
2016-04-15vis: calculate auto indent for all cursors individuallyMarc André Tanner1-6/+9
2016-04-15vis: fix wrong usage message for :unmap commandMarc André Tanner1-1/+1
2016-04-15vis: improve handling of ~ and environment variables when opening filesMarc André Tanner2-2/+6
2016-04-15vis: do not run registered event handlers for internal filesMarc André Tanner1-1/+1
This fixes interactive :-commands when the user has configured to set custom options vis:command(...) via the Lua win_open event handler. The problem was that the creation of the window for the command prompt would itself trigger an execution of a :-command. Upon successful completion the editor would switch to normal mode. Therefore the interactively entered command would not be applied to the correct range.
2016-04-14vis: allow mapping of <Space>Marc André Tanner3-6/+6
One should generally use <Space> in mappings: :map! normal <Space> h except for insert/replace mode where a literal space has to be used: :map! insert " " foo
You can read more about the author.