Re: docker syntax files
On Thursday, August 21, 2014 3:49:25 PM UTC+9, Lokesh Mandvekar wrote: > Hi, > > I was hoping syntax highlighting for docker could be included by default in > vim. The files can be found here: > https://github.com/docker/docker/tree/master/contrib/syntax/vim > > Would the BSD license cause any trouble in this matter? > > Thanks, > -- > Lokesh I prefer to use syn-include for trailing part of RUN command. -- -- You received this message from the "vim_dev" 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_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: docker syntax files
Ben, I do see your point now. And yes, it's probably best that distros use upstream docker's vim files itself than having those sent over here which is an added expense. Bram, upto you to decide the fate of docker syntax files already included. FWIW, fedora will have a docker-io-vim subpackage which will install these files from upstream docker. Apologies about the mess I created. -- -- You received this message from the "vim_dev" 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_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: docker syntax files
Kenichi Ito wrote: > runtime/filetype.vim > " Dockerfile > au BufNewFile,BufRead Dockerfile setf=dockerfile > > This become > filetype==dockerfile > > > This patch fixes it. > --- > diff --git a/runtime/filetype.vim b/runtime/filetype.vim > index 896ccc1..60a47e1 100644 > --- a/runtime/filetype.vim > +++ b/runtime/filetype.vim > @@ -531,7 +531,7 @@ au BufNewFile,BufRead configure.in,configure.ac setf > config > au BufNewFile,BufRead *.cu setf cuda > > " Dockerfile > -au BufNewFile,BufRead Dockerfile setf=dockerfile > +au BufNewFile,BufRead Dockerfile setf dockerfile > > " WildPackets EtherPeek Decoder > au BufNewFile,BufRead *.dcd setf dcd Thanks for the correction! -- >From "know your smileys": % Bike accident. A bit far-fetched, I suppose; although... o _ _ _ _o /\_ _ \\o (_)\__/o (_) _< \_ _>(_) (_)/<_\_| \ _|/' \/ (_)>(_) (_)(_) (_)(_)' _\o_ /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the "vim_dev" 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_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: docker syntax files
runtime/filetype.vim " Dockerfile au BufNewFile,BufRead Dockerfile setf=dockerfile This become filetype==dockerfile This patch fixes it. --- diff --git a/runtime/filetype.vim b/runtime/filetype.vim index 896ccc1..60a47e1 100644 --- a/runtime/filetype.vim +++ b/runtime/filetype.vim @@ -531,7 +531,7 @@ au BufNewFile,BufRead configure.in,configure.ac setf config au BufNewFile,BufRead *.cu setf cuda " Dockerfile -au BufNewFile,BufRead Dockerfile setf=dockerfile +au BufNewFile,BufRead Dockerfile setf dockerfile " WildPackets EtherPeek Decoder au BufNewFile,BufRead *.dcdsetf dcd --- -- -- You received this message from the "vim_dev" 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_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: docker syntax files
Honza Pokorny wrote: > Here are the docker syntax files. I added a simple note about the > license to the main file. I have moved setting commentstring to an ftplugin file. I moved some lines arround in the syntax file to follow the style that most syntax files used. And use "hi def link" instead of "hi link", so that users can change the colors easier. Please pick up the latest version from the Mercurial repository. -- >From "know your smileys": O:-) Saint /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the "vim_dev" 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_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: docker syntax files
Here are the docker syntax files. I added a simple note about the license to the main file. On Friday, August 22, 2014 5:00:43 PM UTC+2, Bram Moolenaar wrote: > Honza Pokorny wrote: > > > > > I'm the original author of the syntax highlighting code. I'm not sure > > > if I'm in a position to make the call on this anymore. > > > > > > The code started out in my own repository on GitHub > > > > > > https://github.com/honza/dockerfile.vim > > > > > > But then It got included in docker proper where others have made > > > contributions. If you think it's acceptable, I could send you a copy > > > of what's in the docker repository with the license added into the > > > file itself. > > > > > > I'm not really sure how this stuff usually works, and I'm happy to > > > help. Just let me know. > > > > I'm not a lawyer, but I suppose the BSD license is compatible with the > > Vim license. Thus including that license in the header of the file is > > probably OK. > > > > -- > > The future isn't what it used to be. > > > > /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ > > ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ > > \\\ an exciting new programming language -- http://www.Zimbu.org/// > > \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the "vim_dev" 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_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout. docker-vim.tar.gz Description: Binary data
Re: docker syntax files
Sounds like Bram disagrees with almost my entire premise, so probably
Docker stuff'll just get merged into Vim. Responding point-by-point
anyway.
On Fri, Aug 22, 2014 at 12:40 AM, Lokesh Mandvekar
wrote:
> On Thu, Aug 21, 2014 at 04:43:58PM -0400, Benjamin R. Haskell wrote:
>> As with the Docker Zsh completion file that just got included in
>> upstream Zsh, I'd prefer that this doesn't make it into Vim "proper".
>> Including it in another project just makes changes harder to
>
> From a distro package perspective, using zsh completion or vim syntax from
> contrib causes ownership issues (certainly on fedora and its
> downstreams, perhaps other distros too) as the dirs in which these files would
> be installed are owned by other packages. See:
> https://bugzilla.redhat.com/show_bug.cgi?id=1127570#c3
> Including them in the main repo would solve that.
I have no idea how Fish is typically structured, but I'd be surprised
if it were different from how Zsh and Vim have a "site packages"
directory, which isn't generally owned by the relevant program. E.g.
on my current (Arch) system, there's a `/usr/share/vim/vimfiles`
directory, which contains the following files owned by packages other
than `vim`:
```
compiler/lilypond.vim is owned by lilypond 2.18.2-2
ftdetect/augeas.vim is owned by augeas 1.2.0-1
ftdetect/lilypond.vim is owned by lilypond 2.18.2-2
ftplugin/lilypond.vim is owned by lilypond 2.18.2-2
indent/cmake-indent.vim is owned by cmake 2.8.12.2-2
indent/lilypond.vim is owned by lilypond 2.18.2-2
syntax/HGAnnotate.vim is owned by mercurial 3.0-1
syntax/PKGBUILD.vim is owned by pacman 4.1.2-6
syntax/asciidoc.vim is owned by asciidoc 8.6.9-1
syntax/augeas.vim is owned by augeas 1.2.0-1
syntax/cmake-syntax.vim is owned by cmake 2.8.12.2-2
syntax/lilypond-words is owned by lilypond 2.18.2-2
syntax/lilypond-words.vim is owned by lilypond 2.18.2-2
syntax/lilypond.vim is owned by lilypond 2.18.2-2
syntax/tmux.vim is owned by tmux 1.9_a-1
```
> If it's only Fedora's/RHEL's problem and if others don't want it included
> here, I'm cool with bugging the package maintainers to include this in
> their rpms.
>
>> propagate. Instead of taking just a pull request against the Docker
>> repo, a change goes through the idiosyncratic (and slower) Vim runtime
>> files change process (which apparently still involves emailing files
>> in the year 2014).
>
> The files that were upstreamed certainly won't be deleted from docker/contrib
> as per
> https://github.com/docker/docker/issues/7657 . I guess some people
> could take it upon themselves to periodically upstream changes from
> docker/contrib.
That was part of my main thrust with:
>> - They contribute to the amount of maintenance work Bram has to do
>> - ...
>> - They can't be updated as easily as they can if developed independently
I'd be happier if there was no effort needed to periodically upstream
changes, because whoever packages Docker would handle packaging the
related Vim syntax files.
>> I think the state of the Vim ecosystem would be much better if:
>>
>> 1. Vim shipped with (or at least advocated the use of) a reasonable
>> plugin/addon/package manager
>> - This would at least discourage the poor manageability of "Just
>> untar this into ~/.vim"
>>
>> 2. Vim didn't distribute (m/)any language-/tool-specific addons
>> - They contribute to the amount of maintenance work Bram has to do
>> - They detract from the amount of work that can be done on core Vim
>> - They can't be updated as easily as they can if developed independently
>> - They're subject to Vim's licensing (... kind of?). (At a
>> minimum, licensing has to be considered. In the separately-developed
>> scenario, it's simply not a concern.)
>> - They're weirdly tied to a single (point of failure) author.
>>
>> 3. Projects (like Docker) that have Vim files would set them up in a
>> way usable by (a) Vim plugin manager(s).
>> - "Via pathogen, the usual way..."¹ seems a bit glib/useless
>>
>> #'s 1 and 2 are obviously out-of-scope for this Docker-specific
>> request. But #3 should be easily achievable, AFAICT:
>>
>> My preferred plugin manager, Vundle², for example, makes installing
>> the Docker syntax files as simple³ as adding one of the following to
>> `.vimrc` or equivalent:
>>
>> ```
>> " if installing from scratch:
>> Plugin 'docker/docker', {'rtp': 'contrib/syntax/vim/'}
>>
>> " if you already have `docker/docker` checked out:
>> Plugin 'file://
Re: docker syntax files
Honza Pokorny wrote: > I'm the original author of the syntax highlighting code. I'm not sure > if I'm in a position to make the call on this anymore. > > The code started out in my own repository on GitHub > > https://github.com/honza/dockerfile.vim > > But then It got included in docker proper where others have made > contributions. If you think it's acceptable, I could send you a copy > of what's in the docker repository with the license added into the > file itself. > > I'm not really sure how this stuff usually works, and I'm happy to > help. Just let me know. I'm not a lawyer, but I suppose the BSD license is compatible with the Vim license. Thus including that license in the header of the file is probably OK. -- The future isn't what it used to be. /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the "vim_dev" 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_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: docker syntax files
Benjamin Haskell wrote:
> (The following assumes I haven't missed something about the Vim
> development process during my extended absence from vim-{dev/use}.)
>
> On Thu, Aug 21, 2014 at 3:39 PM, Bram Moolenaar wrote:
> >
> > Lokesh Mandvekar wrote:
> >
> >> I was hoping syntax highlighting for docker could be included by
> >> default in vim. The files can be found here:
> >> https://github.com/docker/docker/tree/master/contrib/syntax/vim
> >>
> >> Would the BSD license cause any trouble in this matter?
> >
> > I prefer the author sending the file to me, so that it's explicit that
> > it is OK to include in the distribution.
> >
> > I don't see a License statement in the file itself. I would have to
> > include the LICENSE file somehow.
> >
> > /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
>
> As with the Docker Zsh completion file that just got included in
> upstream Zsh, I'd prefer that this doesn't make it into Vim "proper".
> Including it in another project just makes changes harder to
> propagate. Instead of taking just a pull request against the Docker
> repo, a change goes through the idiosyncratic (and slower) Vim runtime
> files change process (which apparently still involves emailing files
> in the year 2014).
>
> I think the state of the Vim ecosystem would be much better if:
>
> 1. Vim shipped with (or at least advocated the use of) a reasonable
> plugin/addon/package manager
> - This would at least discourage the poor manageability of "Just
> untar this into ~/.vim"
>
> 2. Vim didn't distribute (m/)any language-/tool-specific addons
> - They contribute to the amount of maintenance work Bram has to do
> - They detract from the amount of work that can be done on core Vim
> - They can't be updated as easily as they can if developed independently
> - They're subject to Vim's licensing (... kind of?). (At a
> minimum, licensing has to be considered. In the separately-developed
> scenario, it's simply not a concern.)
> - They're weirdly tied to a single (point of failure) author.
>
> 3. Projects (like Docker) that have Vim files would set them up in a
> way usable by (a) Vim plugin manager(s).
> - "Via pathogen, the usual way..."¹ seems a bit glib/useless
>
> #'s 1 and 2 are obviously out-of-scope for this Docker-specific
> request. But #3 should be easily achievable, AFAICT:
>
> My preferred plugin manager, Vundle², for example, makes installing
> the Docker syntax files as simple³ as adding one of the following to
> `.vimrc` or equivalent:
>
> ```
> " if installing from scratch:
> Plugin 'docker/docker', {'rtp': 'contrib/syntax/vim/'}
>
> " if you already have `docker/docker` checked out:
> Plugin 'file:///home/bhaskell/git/docker/contrib/syntax/vim'
> ```
A little while ago I asked what the best plugin manager was, and there
was no clear answer. And in my opinion there is not one that can be
included with Vim that has all the features that most users want.
Several people worked on a plugin manager to cover their own needs, none
of them is "complete".
Anyway, we still need to include the most ofen used filetype support in
Vim itself, so that when you install Vim you can go ahead editing files
without doing lots of setup work.
On top of that, more than 50% of the times I get new runtime files I
have to ask the author to improve something.
--
Don't read everything you believe.
/// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org///
\\\help me help AIDS victims -- http://ICCF-Holland.org///
--
--
You received this message from the "vim_dev" 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_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: docker syntax files
Bram, I'm the original author of the syntax highlighting code. I'm not sure if I'm in a position to make the call on this anymore. The code started out in my own repository on GitHub https://github.com/honza/dockerfile.vim But then It got included in docker proper where others have made contributions. If you think it's acceptable, I could send you a copy of what's in the docker repository with the license added into the file itself. I'm not really sure how this stuff usually works, and I'm happy to help. Just let me know. Thanks On Thursday, August 21, 2014 9:39:27 PM UTC+2, Bram Moolenaar wrote: > Lokesh Mandvekar wrote: > > > > > I was hoping syntax highlighting for docker could be included by default in > > > vim. The files can be found here: > > > https://github.com/docker/docker/tree/master/contrib/syntax/vim > > > > > > Would the BSD license cause any trouble in this matter? > > > > I prefer the author sending the file to me, so that it's explicit that > > it is OK to include in the distribution. > > > > I don't see a License statement in the file itself. I would have to > > include the LICENSE file somehow. > > > > -- > > A fine is a tax for doing wrong. A tax is a fine for doing well. > > > > /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ > > ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ > > \\\ an exciting new programming language -- http://www.Zimbu.org/// > > \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the "vim_dev" 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_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: docker syntax files
On Thu, Aug 21, 2014 at 04:43:58PM -0400, Benjamin R. Haskell wrote:
> As with the Docker Zsh completion file that just got included in
> upstream Zsh, I'd prefer that this doesn't make it into Vim "proper".
> Including it in another project just makes changes harder to
From a distro package perspective, using zsh completion or vim syntax from
contrib causes ownership issues (certainly on fedora and its
downstreams, perhaps other distros too) as the dirs in which these files would
be installed are owned by other packages. See:
https://bugzilla.redhat.com/show_bug.cgi?id=1127570#c3
Including them in the main repo would solve that.
If it's only Fedora's/RHEL's problem and if others don't want it included
here, I'm cool with bugging the package maintainers to include this in
their rpms.
> propagate. Instead of taking just a pull request against the Docker
> repo, a change goes through the idiosyncratic (and slower) Vim runtime
> files change process (which apparently still involves emailing files
> in the year 2014).
The files that were upstreamed certainly won't be deleted from docker/contrib
as per
https://github.com/docker/docker/issues/7657 . I guess some people
could take it upon themselves to periodically upstream changes from
docker/contrib.
>
> I think the state of the Vim ecosystem would be much better if:
>
> 1. Vim shipped with (or at least advocated the use of) a reasonable
> plugin/addon/package manager
> - This would at least discourage the poor manageability of "Just
> untar this into ~/.vim"
>
> 2. Vim didn't distribute (m/)any language-/tool-specific addons
> - They contribute to the amount of maintenance work Bram has to do
> - They detract from the amount of work that can be done on core Vim
> - They can't be updated as easily as they can if developed independently
> - They're subject to Vim's licensing (... kind of?). (At a
> minimum, licensing has to be considered. In the separately-developed
> scenario, it's simply not a concern.)
> - They're weirdly tied to a single (point of failure) author.
>
> 3. Projects (like Docker) that have Vim files would set them up in a
> way usable by (a) Vim plugin manager(s).
> - "Via pathogen, the usual way..."¹ seems a bit glib/useless
>
> #'s 1 and 2 are obviously out-of-scope for this Docker-specific
> request. But #3 should be easily achievable, AFAICT:
>
> My preferred plugin manager, Vundle², for example, makes installing
> the Docker syntax files as simple³ as adding one of the following to
> `.vimrc` or equivalent:
>
> ```
> " if installing from scratch:
> Plugin 'docker/docker', {'rtp': 'contrib/syntax/vim/'}
>
> " if you already have `docker/docker` checked out:
> Plugin 'file:///home/bhaskell/git/docker/contrib/syntax/vim'
> ```
Haven't used plugin managers myself, and I'll be sure to try them out, but
I think the aforementioned file/dir ownership issues would be
applicable in this case too. Correct me if I'm wrong.
>
> --
> Best,
> Ben
>
> ¹:
> https://github.com/docker/docker/tree/cb47ddd968747091fd1b3d408dd36c4c2086e69f/contrib/syntax/vim#installation
> ²: https://github.com/gmarik/Vundle.vim
> ³: "simple", and in this case, amazingly inefficient (since it clones
> the whole Docker repo). "simple" != "perfect". With Pathogen, on the
> other hand, you could download an archive of just that
> `contrib/syntax/vim/` directory. But that's an extra (manual!) step.
Thanks,
--
Lokesh
pgpDfZyo8EJPG.pgp
Description: PGP signature
Re: docker syntax files
(The following assumes I haven't missed something about the Vim
development process during my extended absence from vim-{dev/use}.)
On Thu, Aug 21, 2014 at 3:39 PM, Bram Moolenaar wrote:
>
> Lokesh Mandvekar wrote:
>
>> I was hoping syntax highlighting for docker could be included by default in
>> vim. The files can be found here:
>> https://github.com/docker/docker/tree/master/contrib/syntax/vim
>>
>> Would the BSD license cause any trouble in this matter?
>
> I prefer the author sending the file to me, so that it's explicit that
> it is OK to include in the distribution.
>
> I don't see a License statement in the file itself. I would have to
> include the LICENSE file somehow.
>
> /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\
As with the Docker Zsh completion file that just got included in
upstream Zsh, I'd prefer that this doesn't make it into Vim "proper".
Including it in another project just makes changes harder to
propagate. Instead of taking just a pull request against the Docker
repo, a change goes through the idiosyncratic (and slower) Vim runtime
files change process (which apparently still involves emailing files
in the year 2014).
I think the state of the Vim ecosystem would be much better if:
1. Vim shipped with (or at least advocated the use of) a reasonable
plugin/addon/package manager
- This would at least discourage the poor manageability of "Just
untar this into ~/.vim"
2. Vim didn't distribute (m/)any language-/tool-specific addons
- They contribute to the amount of maintenance work Bram has to do
- They detract from the amount of work that can be done on core Vim
- They can't be updated as easily as they can if developed independently
- They're subject to Vim's licensing (... kind of?). (At a
minimum, licensing has to be considered. In the separately-developed
scenario, it's simply not a concern.)
- They're weirdly tied to a single (point of failure) author.
3. Projects (like Docker) that have Vim files would set them up in a
way usable by (a) Vim plugin manager(s).
- "Via pathogen, the usual way..."¹ seems a bit glib/useless
#'s 1 and 2 are obviously out-of-scope for this Docker-specific
request. But #3 should be easily achievable, AFAICT:
My preferred plugin manager, Vundle², for example, makes installing
the Docker syntax files as simple³ as adding one of the following to
`.vimrc` or equivalent:
```
" if installing from scratch:
Plugin 'docker/docker', {'rtp': 'contrib/syntax/vim/'}
" if you already have `docker/docker` checked out:
Plugin 'file:///home/bhaskell/git/docker/contrib/syntax/vim'
```
--
Best,
Ben
¹:
https://github.com/docker/docker/tree/cb47ddd968747091fd1b3d408dd36c4c2086e69f/contrib/syntax/vim#installation
²: https://github.com/gmarik/Vundle.vim
³: "simple", and in this case, amazingly inefficient (since it clones
the whole Docker repo). "simple" != "perfect". With Pathogen, on the
other hand, you could download an archive of just that
`contrib/syntax/vim/` directory. But that's an extra (manual!) step.
--
--
You received this message from the "vim_dev" 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_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: docker syntax files
Lokesh Mandvekar wrote: > I was hoping syntax highlighting for docker could be included by default in > vim. The files can be found here: > https://github.com/docker/docker/tree/master/contrib/syntax/vim > > Would the BSD license cause any trouble in this matter? I prefer the author sending the file to me, so that it's explicit that it is OK to include in the distribution. I don't see a License statement in the file itself. I would have to include the LICENSE file somehow. -- A fine is a tax for doing wrong. A tax is a fine for doing well. /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ ///sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org/// \\\help me help AIDS victims -- http://ICCF-Holland.org/// -- -- You received this message from the "vim_dev" 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_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
docker syntax files
Hi, I was hoping syntax highlighting for docker could be included by default in vim. The files can be found here: https://github.com/docker/docker/tree/master/contrib/syntax/vim Would the BSD license cause any trouble in this matter? Thanks, -- Lokesh pgpeuXBUWT3pd.pgp Description: PGP signature
