Collapse the many forks? #51
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…ons directory don't leave a blank line at the end of the file.
Clean up the ftplugin a bit. Use the save_cpo pattern to ensure cpo is set appropriately, and define a b:undo_ftplugin. Change the b:match_words definition to match else/else if.
- Fix: multiline strings should not be modified. - Fix: "end" is always decreased by one. - Fix: "case" and "else" are always decreased by one. - Fix: continued lines are not treated differently. - Fix: "if", "while", etc followed by "begin" should increment next line by two instead of by one. - Fix: "case" should be one more than "switch". - Fix: multiline strings and continued lines are considered in the calculations for the next line.
- funced and fish_indent always uses tabs for indentation, use fish#Indent() to fix it. Works better with the improved fish#Indent(). - ftdetect should contain filetype detection code. Move autocmds to plugin/fish.vim. - Match new funced temp file name. - Add "else", "else if" and "case" to b:match_words to follow what's used by Vim's ftplugins. blankname: - dropped the syntax changes (cc: dag#28) Co-authored-by: blankname <>
… and funced files.
… to change this to only replace the tab if we're editing a new/blank function).
The wrong autocommand was changed in 0dfeda7. Also use BufNewFile instead of BufRead.
I didn't remove the iskeyword definition entirely because I believe including '_' and '.' is still useful. Use 'syntax iskeyword @,48-57,-,_,.,/' in the syntax definitions so that '/' is still matched by syntax patterns that use '\k'. cc: dag#44
Author: Nova <novadev94@gmail.com> Date: Wed Mar 25 17:33:36 2020 +0700
|
I think this project is basically dead, but I did a complete rewrite that properly highlights the newer fish features: It has much more accurate syntax highlighting and I plan on maintaining it and responding to issues/pulls for the foreseeable future. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello.
I'm assuming many people have submitted pull requests, but it's unclear why these haven't been merged? Is this an abandoned project? Would be good to know what people are using, if so.
Thanks.