Skip to content

Conversation

@daveman1010221
Copy link

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.

gpanders and others added 12 commits January 5, 2020 15:59
…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 <>
… 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
@nickeb96
Copy link

I think this project is basically dead, but I did a complete rewrite that properly highlights the newer fish features:

nickeb96/fish.vim

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants