Re: (Obscure) problem with bash syntax highlighting

2019-05-24 Thread Gary Johnson
On 2019-05-24, Tony Mechelynck wrote: > On Fri, May 24, 2019 at 1:52 PM 'J S' via vim_use > wrote: > [...] > > Note: I tried contacting the listed author/maintainer (Charles > > Campbell) via email first (before posting this), but the mail > > bounced. It looks like the sh.vim file hasn't been

Re: (Obscure) problem with bash syntax highlighting

2019-05-24 Thread Tony Mechelynck
On Fri, May 24, 2019 at 1:52 PM 'J S' via vim_use wrote: [...] > Note: I tried contacting the listed author/maintainer (Charles Campbell) via > email first (before posting this), but the mail bounced. It looks like the > sh.vim file hasn't been updated since 2014. Dr. Chip's adress is listed

Re: (Obscure) problem with bash syntax highlighting

2019-05-24 Thread L A Walsh
-- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php ok, though isn't it more important to prune unnecessary content? :-| On 2019/05/21 13:17, 'J S' via

(Obscure) problem with bash syntax highlighting

2019-05-24 Thread 'J S' via vim_use
bash allows (yes, it is a "bashism") syntax like: $ echo ${var:9:5} To mean extract a substring of the variable, starting at position 9 and of length 5. But is also allows the offset (and then length, too, but ignore that for now) to benegative.  But, alas, as noted in "man bash", if the offset