On Fri, 24 Feb 2017 19:10:41 +0100 Francesco Poli wrote:
> On Mon, 19 Dec 2016 14:34:54 +0100 Bas Zoetekouw wrote:
>
> > Hi,
> >
> > On 19/12/16 14:02, James McCoy wrote:
> > > On Mon, Dec 19, 2016 at 11:55:50AM +0100, Bas Zoetekouw wrote:
> > >> Vim's currenr behaviour for syntax highlighting o
On Mon, 19 Dec 2016 14:34:54 +0100 Bas Zoetekouw wrote:
> Hi,
>
> On 19/12/16 14:02, James McCoy wrote:
> > On Mon, Dec 19, 2016 at 11:55:50AM +0100, Bas Zoetekouw wrote:
> >> Vim's currenr behaviour for syntax highlighting of shell scripts (with
> >> #!/bin/sh and /bin/sh pointing to dash) is to
Hi,
On 19/12/16 14:02, James McCoy wrote:
> On Mon, Dec 19, 2016 at 11:55:50AM +0100, Bas Zoetekouw wrote:
>> Vim's currenr behaviour for syntax highlighting of shell scripts (with
>> #!/bin/sh and /bin/sh pointing to dash) is to mark command
>> substititions using the $(foo) construction as an er
On Mon, Dec 19, 2016 at 11:55:50AM +0100, Bas Zoetekouw wrote:
> Vim's currenr behaviour for syntax highlighting of shell scripts (with
> #!/bin/sh and /bin/sh pointing to dash) is to mark command
> substititions using the $(foo) construction as an error.
Not that I can see.
> This is incorrect,
Package: vim
Version: 2:8.0.0095-1
Severity: normal
Tags: patch
Vim's currenr behaviour for syntax highlighting of shell scripts (with
#!/bin/sh and /bin/sh pointing to dash) is to mark command
substititions using the $(foo) construction as an error.
This is incorrect, as POSIX sh alllows this con
5 matches
Mail list logo