www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.ide - Help with d.vim Syntax file for Vim

reply ulyssesdwolfe <ulyssesdwolfe gmail.com> writes:
Hi,

There seems to be some missing statements in the standard d.vim 
that gets distributed with vim regarding auto-commenting.
Whenever I am in a multiline comment for example a ddoc statement 
and start a new line by hitting the Enter key, the result is an 
indentation of 1 on the new line and no comment char unlike the 
syntax in normal c and cpp files. It doesn't matter if the 
comment start was with '/**' or '/++'.

I took a look at the runtime/syntax/c.vim for hacking the 
auto-commenting out of that file and putting it in d.vim. But I 
am not familiar with any of those calls.
I was wondering if someone who is more familiar with Vimscript 
can tell me what lines or quick fix I need to put in the syntax 
file to get the auto-commenting to work for d editing.

ty
Jul 02 2017
parent reply Petar Kirov [ZombineDev] <petar.p.kirov gmail.com> writes:
On Sunday, 2 July 2017 at 09:50:28 UTC, ulyssesdwolfe wrote:

 Hi,

 There seems to be some missing statements in the standard d.vim 
 that gets distributed with vim regarding auto-commenting.
 Whenever I am in a multiline comment for example a ddoc 
 statement and start a new line by hitting the Enter key, the 
 result is an indentation of 1 on the new line and no comment 
 char unlike the syntax in normal c and cpp files. It doesn't 
 matter if the comment start was with '/**' or '/++'.

 I took a look at the runtime/syntax/c.vim for hacking the 
 auto-commenting out of that file and putting it in d.vim. But I 
 am not familiar with any of those calls.
 I was wondering if someone who is more familiar with Vimscript 
 can tell me what lines or quick fix I need to put in the syntax 
 file to get the auto-commenting to work for d editing.

 ty


Have you tried https://github.com/JesseKPhillips/d.vim? I'm not 
sure if
the issues you mentioned are fixed there, but if they're not I
suggest you open issues on that repo. Last time I contributed 
there
the author was helpful & responsive.
Jul 03 2017
parent reply ulyssesdwolfe <ulyssesdwolfe gmail.com> writes:
On Monday, 3 July 2017 at 16:13:28 UTC, Petar Kirov [ZombineDev] 
wrote:


 Have you tried https://github.com/JesseKPhillips/d.vim?


Thanks for the reply.
I did take a quick peek at that repo. It supplies the d.vim that 
gets distributed with vim and it seems there is also an old issue 
that addresses the same/similar problem.

https://github.com/JesseKPhillips/d.vim/issues/24
Jul 06 2017
parent Petar Kirov [ZombineDev] <petar.p.kirov gmail.com> writes:
On Thursday, 6 July 2017 at 12:30:18 UTC, ulyssesdwolfe wrote:

 On Monday, 3 July 2017 at 16:13:28 UTC, Petar Kirov 
 [ZombineDev] wrote:


 Have you tried https://github.com/JesseKPhillips/d.vim?


 Thanks for the reply.
 I did take a quick peek at that repo. It supplies the d.vim 
 that gets distributed with vim and it seems there is also an 
 old issue that addresses the same/similar problem.

 https://github.com/JesseKPhillips/d.vim/issues/24


I suggest you ping the maintainer there. Perhaps he forgot about 
it, or he didn't have time to investigate it back when it was 
reported.
Jul 06 2017