Friday, July 15, 2016

Re: Wrong vim color syntax

2016-07-14 23:24 GMT+03:00 Richard Mitchell <rwmitchell@gmail.com>:
> On Thursday, July 14, 2016 at 11:03:47 AM UTC-4, Willem D'Haese wrote:
>> On Thursday, 7 July 2016 07:20:22 UTC+2, Christian Brabandt wrote:
>> > Am 2016-07-06 22:18, schrieb Willem D'Haese:
>> > > Hello,
>> > >
>> > > There seems something wrong with the coloring in this code with VIM -
>> > > Vi IMproved 7.4 (2013 Aug 10, compiled Jun 10 2014 06:55:55)?
>> > >
>> > > cat <<EOF>/etc/yum.repos.d/influxdb.repo
>> > > [influxdb]
>> > > name = InfluxDB Repository - CentOS \$releasever
>> > > baseurl =
>> > > https://repos.influxdata.com/centos/\$releasever/\$basearch/stable
>> > > enabled = 1
>> > > gpgcheck = 1
>> > > gpgkey = https://repos.influxdata.com/influxdb.key
>> > > EOF
>> > >
>> > > WriteLog Output Info "Tick - Installing influxdb"
>> > > yum install influxdb -y
>> > >
>> > > git clone https://github.com/letsencrypt/letsencrypt /opt/letsencrypt
>> > >
>> > > WriteLog Output Info "Tick Build End"
>> >
>> >
>> > Missing information here. What syntax/filetype is this? Please first try
>> > to
>> > get a newer syntax file (perhaps from the repository from the maintainer
>> > or
>> > you might try the included runtime file from a later vim version)
>> >
>> > If that does not help, please contact the maintainer of the file
>> > (address is given in the header of the file) and discuss the issue with
>> > him.
>> > It looks like the syntax script does not handle here documents.
>> >
>> > Best,
>> > Christian
>>
>> Hello Christian,
>>
>> Thanks for the help. It is actually a Bash script with filename FireTIG (without .sh extension) I made myself. Where can I find the syntax file for Bash?
>>
>> Grtz
>
> As a pointless programming tip, I put the proper extension on my script code files (.sh, .pl, etc) and then use make to copy&strip the extension/chmod them into a bin area. While this seems unnecessary, besides making it easier for vim know how to colorize the code, it also allows the use of find/grep for searching.

I find omitting extensions for somebody's own non-published scripts
completely useless. Most of time I in any case use tab completion to
finish script name, so it is not going to save typing time. But as it
is uncommon for third-party executables to have an extension (it is
also the reason why there is no extension on many of my published
scripts) it is less likely that your script with extension happen to
share a name with something you recently installed.

>
> --
> --
> 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
>
> ---
> You received this message because you are subscribed to the Google Groups "vim_use" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

--
--
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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

No comments: