| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Fails on missing `vis` symbol as in `vis.win.file` ???
|
|\
| |
| | |
Turn on highlighting when suggestions keybinding Ctrl-W W is pressed
|
|/ |
|
|
|
|
| |
Fixes: f1c220802abcbb10a139ef99c98c803c10ca74e5
|
|\
| |
| | |
Rename 'spell_language' to 'spelling_language'
|
|/
|
| |
Following discussions on the editorconfig standard, I just renamed this property in the vis-editorconfig plugin (see https://github.com/seifferth/vis-editorconfig/commit/d99ec6bb31b042bf0b6111c20d622f64636d2ed6). In order to keep the naming somewhat consistent, I also updated the internal variable name that stores the spelling_language specified in editorconfig files. This commit updates the spellcheck plugin to use the updated variable name.
|
|\
| |
| |
| |
| | |
don't return anything in WIN_HIGHLIGHT event
See merge request muhq/vis-spellcheck!13
|
|/
|
|
|
| |
Returning true prevents a user from defining a WIN_HIGHLIGHT event in
addition to spellchecking.
|
|\
| |
| | |
add keybind to add word to user dictionary
|
| | |
|
| | |
|
|\ \
| |/
|/|
| |
| | |
consider the environment variable VIS_SPELLLANG as default
See merge request muhq/vis-spellcheck!12
|
|/
|
|
|
|
|
|
|
|
|
|
|
| |
If the variable VIS_SPELLLANG is not set the variable LANG is considered
next.
Passing the spellchecking language via the environment can be useful
when starting vis from different contexts.
My use case is different mail addresses in mutt.
On one address I mostly communicate in English and on another I
communicate in German. Passing the context specific language vis the
environment safes setting the spellchecking language for each email I
write.
|
|\
| |
| |
| |
| | |
fix typo detection at file start
See merge request muhq/vis-spellcheck!11
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
If a file starts with a typo our pattern [%A]typo[%A] can not find it.
However if the same typo appears a second type in the text our pattern
happily finds the second occurence skipping the first and all typos
in between.
In the text
typo1
Correct text typo2 ...
typo1
our pattern will match the second occurence of 'typo1' skipping
'typo2'.
Since we update our search index 'typo2' will never be found and
vis-spellcheck will show the user an information prompt.
Fix this behaviour by adding a special case for the first typo which may
start the text.
|
|\
| |
| |
| |
| | |
Sanitize LANG environment variable
See merge request muhq/vis-spellcheck!10
|
|/ |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
To me, this seems pretty useful for debugging purposes. It might
also be of general interest to the curious user.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
There is some discussion on the editorconfig side
about whether a 'spell_language' key could be added
(cf. https://github.com/editorconfig/editorconfig/issues/315,
https://github.com/seifferth/vis-editorconfig/pull/8). This key would
specify the natural language a file is written in and it would then
be up to the editor or plugin doing the spellchecking to respect that
setting and behave accordingly.
Since it is out of the scope of the vis-editorconfig plugin to
implement spellchecking, and since I would like the vis-editorconfig
plugin to work both with and without vis-spellcheck, I suggest
to use 'vis.win.file.spell_language' to store the document
language. With commit 0ee415c in the vis-editorconfig repo
(https://github.com/seifferth/vis-editorconfig), this value is already
set to the appropriate value. This commit adjusts the spellchecking
plugin to use the same global value. I did some testing that suggests
it should work.
There might still be some hickups if 'vis.win.file' does not exist.
This is a non-issue for editorconfig, since editorconfig only works
if 'vis.win.file.path' exists (which configuration is used depends
on the path). The Readme would also need some adjustment.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|\
| |
| | |
check if "LANG" environment variable exists before indexing it
|
|/ |
|
|
|
|
|
|
| |
* Remove unused variables
* Remove unused assginments
* Fix one actual bug (typo in variable name)
|
| |
|
|\
| |
| | |
Use single quotes around plugin path
|
|/ |
|
|
|
|
|
|
|
| |
The init.lua file is only a thin wrapper around a dofile call which loads
the actual plugin code in spellcheck.lua and returns the result.
Closes #5.
|
|
|
|
|
|
|
| |
Because the lexer.lex wrapper function is a closure it saves the
state of the ignored word table in the closure.
Therefore to see the effect of ignoring words we must rebuild the wrapper
closure.
|
|\
| |
| | |
Fix arrows in vis-menu by using vis:pipe()
|
|/ |
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
If the typo itself contains magic pattern characters we can't reliable find
it in the text.
|
| |
| |
| |
| |
| |
| | |
An iterator in lua stops if it returns nil.
This change will get a new typo from the unfiltered_iterator if
we encounter an empty one instead of returning nil.
|
| |
| |
| |
| |
| | |
apparently in the typo list produced by aspell there is a blank line
which messes with our search for typos.
|
| | |
|
| | |
|