aboutsummaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* create a file snapshot before modifying the textmasterFlorian Fischer2025-12-091-0/+21
|
* use vis' pipe buffer support to check a string for typosFlorian Fischer2025-12-091-3/+11
| | | | | | | | | Since lua does not support bidirectional popen, we used to write to a temporary file each time we checked some string for typos. A string is always checked when using the syntax aware mode. Using the buffered pipe offered by vis removes potential overhead introduced by the write/read cycle and preserve SSD writes.
* Eliminated function call syntax sugar for stringsNomarian2025-10-121-6/+6
|
* Redundant step on for loopNomarian2025-10-121-1/+1
|
* Removed impossibilityNomarian2025-10-121-3/+0
|
* typo_iter redundant pattern [%A] -> %ANomarian2025-10-121-1/+1
|
* typo_iter gmatch [^\n]+ instead and one less check on getting typosNomarian2025-10-121-2/+2
|
* typo_iter only returns start,finish or nil if typo is nilNomarian2025-10-121-3/+3
|
* typo_iter typo iterator gmatch"%S+" instead of (.-)\nNomarian2025-10-121-1/+1
|
* typo_iter return early instead of having a big if typo thenNomarian2025-10-121-32/+31
|
* escape_lua_pattern() is now a string pattern/replNomarian2025-10-121-23/+5
|
* No forking when trying to check for spellchecking utilities in $PATH (use ↵Nomarian2025-10-121-7/+13
| | | | package.searchpath instead)
* Single return statement on get_lang()Nomarian2025-10-091-5/+2
|
* Set/find default_lang from a single string.matchNomarian2025-10-091-4/+4
|
* Shut up luacheckNomarian2025-10-091-0/+2
|
* remove unused parameter and replace tabs with spacesFlorian Fischer2025-07-121-6/+6
|
* Don't crash if vis.win has not been initialized yet.Matěj Cepl2025-07-121-5/+5
|
* feat: automatically enable spellchecking through local settingMatěj Cepl2025-03-102-0/+11
| | | | | | | | | When the local setting spellcheck.spelling_autoenable is set to true and spelling is available (via `spelling_language` setting in .editorconfig), vis will automatically enable spellchecker without any additional user action. References: https://github.com/editorconfig/specification/pull/41
* Makes :spell and :spell+ avaibleTopoetry2025-03-091-0/+14
|
* do not break if lua-lpeg and thus the lexers table is absentFlorian Fischer2024-05-241-5/+14
|
* improve languauge in commentsFlorian Fischer2024-05-101-4/+4
|
* always use the empty string to reset the cached dataFlorian Fischer2024-05-101-1/+1
|
* cleanup wrong return values in key mappingFlorian Fischer2024-05-101-5/+5
|
* return early if viewport is not availableFlorian Fischer2024-05-101-0/+1
|
* cleanup some old vis API usageRandy Palamar2024-04-261-11/+4
| | | | | The vis lexer hasn't used redrawtime for a while and it has been removed from the API.
* support new viewport table for vis >= v0.9Florian Fischer2024-04-251-1/+2
|
* Merge pull request #12 from roguh/turn_on_highlighting_when_suggestingfischerling2024-02-131-0/+3
|\ | | | | Turn on highlighting when suggestions keybinding Ctrl-W W is pressed
| * Turn on highlighting when suggestions keybinding Ctrl-W W is pressedRivera Calzadillas2024-02-121-0/+3
|/
* use spelling_language in spelllang optionFlorian Fischer2023-11-271-1/+1
| | | | Fixes: f1c220802abcbb10a139ef99c98c803c10ca74e5
* Merge pull request #11 from seifferth/patch-1fischerling2023-09-251-2/+2
|\ | | | | Rename 'spell_language' to 'spelling_language'
| * Rename 'spell_language' to 'spelling_language'Frank Seifferth2023-09-251-2/+2
|/ | | 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.
* Merge branch 'noreturn' into 'master'Florian Fischer2023-09-151-7/+0
|\ | | | | | | | | don't return anything in WIN_HIGHLIGHT event See merge request muhq/vis-spellcheck!13
| * don't return anything in WIN_HIGHLIGHT eventRandy Palamar2023-09-141-7/+0
|/ | | | | Returning true prevents a user from defining a WIN_HIGHLIGHT event in addition to spellchecking.
* Merge pull request #10 from rnpnr/add-wordsfischerling2023-04-202-1/+30
|\ | | | | add keybind to add word to user dictionary
| * ignore newly added word to prevent it from being highlightedFlorian Fischer2023-04-201-2/+13
| |
| * add keybind to add word to user dictionaryRandy Palamar2023-04-192-0/+18
| |
* | Merge branch 'spelllang-env-var' into 'master'Florian Fischer2023-04-171-1/+1
|\ \ | |/ |/| | | | | consider the environment variable VIS_SPELLLANG as default See merge request muhq/vis-spellcheck!12
| * consider the environment variable VIS_SPELLLANG as defaultFlorian Fischer2023-04-171-1/+1
|/ | | | | | | | | | | | | 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.
* Merge branch 'fix-leading-typo-detection' into 'master'Florian Fischer2023-03-021-18/+19
|\ | | | | | | | | fix typo detection at file start See merge request muhq/vis-spellcheck!11
| * fix typo detection at file startFlorian Fischer2023-03-021-18/+19
|/ | | | | | | | | | | | | | | | | | | | | 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.
* Merge branch 'master' into 'master'Florian Fischer2023-02-211-3/+2
|\ | | | | | | | | Sanitize LANG environment variable See merge request muhq/vis-spellcheck!10
| * Sanitize LANG environment variableIsmael Luceno2023-02-201-3/+2
|/
* github: remove github workflowFlorian Fischer2021-12-291-39/+0
|
* CI: disable unused falsely copied test jobFlorian Fischer2021-12-281-5/+5
|
* CI: add simple Gitlab CI configFlorian Fischer2021-12-282-0/+34
|
* make: use POSIX check-formatFlorian Fischer2021-12-282-5/+10
|
* make formatFlorian Fischer2021-12-281-2/+3
|
* [Readme] update Readme to reflect the file language changesFlorian Fischer2021-10-071-3/+3
|
* Add 'spelllang' command to print the current valueFrank Seifferth2021-10-071-0/+6
| | | | | To me, this seems pretty useful for debugging purposes. It might also be of general interest to the curious user.
* Use 'vis.win.file.spell_language' rather than 'spellcheck.lang'Frank Seifferth2021-10-071-5/+12
| | | | | | | | | | | | | | | | | | | | | | | | | 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.