On Wednesday, 3 September 2014 at 19:38:44 UTC, Idan Arye wrote:
> Version 1.1.0 is out now. It provides the :DUjump command for jumping to the declaration of the symbol under the cursor. If DCD is not running, Dscanner will be used instead. You can also give :DUjump the symbol as an argument - in this case it'll always use Dscanner(since DCD only supports getting the symbol by byte position).
>
> GitHub repo: https://github.com/idanarye/vim-dutyl
> vim.org page: http://www.vim.org/scripts/script.php?script_id=5003

Can DUjump be set to open in a new window (internal to vim, not a new instance of vim)? For an example of why this would be better: you can't currently use DUjump if the file has unsaved changes.

On Sunday, 7 September 2014 at 18:14:33 UTC, John Colvin wrote:
> On Wednesday, 3 September 2014 at 19:38:44 UTC, Idan Arye wrote:
>> Version 1.1.0 is out now. It provides the :DUjump command for jumping to the declaration of the symbol under the cursor. If DCD is not running, Dscanner will be used instead. You can also give :DUjump the symbol as an argument - in this case it'll always use Dscanner(since DCD only supports getting the symbol by byte position).
>>
>> GitHub repo: https://github.com/idanarye/vim-dutyl
>> vim.org page: http://www.vim.org/scripts/script.php?script_id=5003
>
> Can DUjump be set to open in a new window (internal to vim, not a new instance of vim)? For an example of why this would be better: you can't currently use DUjump if the file has unsaved changes.

Sure, no problem, I'll get to it in the next release.

To be consistent with other Vim commands I'm gonna add :DUsjump and DUvjump for jumping in new windows.

I also plan on adding the bang option - :DUjump!(and it's split variants) - which will force it to use Dscanner even if DCD is running. I find that sometimes it's becoming too complicated for DCD to follow the declarations chain all the way to the source, and Dscanner - which gets the symbol from the command line arguments instead of a getting a byte position in a file - performs better. Even if it can't filter to find the exact declaration that I'm looking for, it displays multiple options that the one I'm looking for is among them, which is better than DCD that can't follow the entire chain and finds nothing.

On Sunday, 7 September 2014 at 20:07:20 UTC, Idan Arye wrote:
> On Sunday, 7 September 2014 at 18:14:33 UTC, John Colvin wrote:
>> On Wednesday, 3 September 2014 at 19:38:44 UTC, Idan Arye wrote:
>>> Version 1.1.0 is out now. It provides the :DUjump command for jumping to the declaration of the symbol under the cursor. If DCD is not running, Dscanner will be used instead. You can also give :DUjump the symbol as an argument - in this case it'll always use Dscanner(since DCD only supports getting the symbol by byte position).
>>>
>>> GitHub repo: https://github.com/idanarye/vim-dutyl
>>> vim.org page: http://www.vim.org/scripts/script.php?script_id=5003
>>
>> Can DUjump be set to open in a new window (internal to vim, not a new instance of vim)? For an example of why this would be better: you can't currently use DUjump if the file has unsaved changes.
>
> Sure, no problem, I'll get to it in the next release.
>
> To be consistent with other Vim commands I'm gonna add :DUsjump and DUvjump for jumping in new windows.
>
> I also plan on adding the bang option - :DUjump!(and it's split variants) - which will force it to use Dscanner even if DCD is running. I find that sometimes it's becoming too complicated for DCD to follow the declarations chain all the way to the source, and Dscanner - which gets the symbol from the command line arguments instead of a getting a byte position in a file - performs better. Even if it can't filter to find the exact declaration that I'm looking for, it displays multiple options that the one I'm looking for is among them, which is better than DCD that can't follow the entire chain and finds nothing.

Annnnnnnd... it's done. :DUsjump and :DUvjump will split the window before they jump. Also added the bang version.

I'm not making a new release yet(I still want to add another feature before that), but it's in the develop branch in GitHub.

Version 1.2.0 is out now. I've added the command :DUsyntaxCheck, :DUlsyntaxCheck :DUstyleCheck, and :DUlstyleCheck to run Dscanner's syntax or style checks and store the results in the quickfix or location list. As per Vim's conventions for commands that update these lists, it'll automatically jump to the first entry unless the command is called with a bang.

GitHub repo: https://github.com/idanarye/vim-dutyl
vim.org page: http://www.vim.org/scripts/script.php?script_id=5003

On Saturday, 13 September 2014 at 15:19:56 UTC, Idan Arye wrote:
> Version 1.2.0 is out now. I've added the command :DUsyntaxCheck, :DUlsyntaxCheck :DUstyleCheck, and :DUlstyleCheck to run Dscanner's syntax or style checks and store the results in the quickfix or location list. As per Vim's conventions for commands that update these lists, it'll automatically jump to the first entry unless the command is called with a bang.
>
> GitHub repo: https://github.com/idanarye/vim-dutyl
> vim.org page: http://www.vim.org/scripts/script.php?script_id=5003

I just updated both Dutyl and DCD and something broke along the way. I can see that Vim is communicating with DCD because the DCD server log shows that it received a request after a dot completion, but nothing shows up in Vim.

On Sunday, 14 September 2014 at 03:22:35 UTC, Andrei Amatuni
wrote:
> On Saturday, 13 September 2014 at 15:19:56 UTC, Idan Arye wrote:
>> Version 1.2.0 is out now. I've added the command :DUsyntaxCheck, :DUlsyntaxCheck :DUstyleCheck, and :DUlstyleCheck to run Dscanner's syntax or style checks and store the results in the quickfix or location list. As per Vim's conventions for commands that update these lists, it'll automatically jump to the first entry unless the command is called with a bang.
>>
>> GitHub repo: https://github.com/idanarye/vim-dutyl
>> vim.org page: http://www.vim.org/scripts/script.php?script_id=5003
>
> I just updated both Dutyl and DCD and something broke along the way. I can see that Vim is communicating with DCD because the DCD server log shows that it received a request after a dot completion, but nothing shows up in Vim.

The problem was with Dutyl - I used the `uniq` function, which
apparently was bleeding
new(https://github.com/LaTeX-Box-Team/LaTeX-Box/issues/190#issuecomment-47459338).

The fix is in `develop` now. It worked for me(on my Windows
installation - which has a not-as-up-to-date version of Vim as my
Linux installation) - let me know it works for you and I'll make
it an official bugfix.

On Sunday, 14 September 2014 at 20:06:13 UTC, Idan Arye wrote:
> On Sunday, 14 September 2014 at 03:22:35 UTC, Andrei Amatuni
> wrote:
>> On Saturday, 13 September 2014 at 15:19:56 UTC, Idan Arye wrote:
>>> Version 1.2.0 is out now. I've added the command :DUsyntaxCheck, :DUlsyntaxCheck :DUstyleCheck, and :DUlstyleCheck to run Dscanner's syntax or style checks and store the results in the quickfix or location list. As per Vim's conventions for commands that update these lists, it'll automatically jump to the first entry unless the command is called with a bang.
>>>
>>> GitHub repo: https://github.com/idanarye/vim-dutyl
>>> vim.org page: http://www.vim.org/scripts/script.php?script_id=5003
>>
>> I just updated both Dutyl and DCD and something broke along the way. I can see that Vim is communicating with DCD because the DCD server log shows that it received a request after a dot completion, but nothing shows up in Vim.
>
> The problem was with Dutyl - I used the `uniq` function, which
> apparently was bleeding
> new(https://github.com/LaTeX-Box-Team/LaTeX-Box/issues/190#issuecomment-47459338).
>
> The fix is in `develop` now. It worked for me(on my Windows
> installation - which has a not-as-up-to-date version of Vim as my
> Linux installation) - let me know it works for you and I'll make
> it an official bugfix.


Just updated it. It's working about 60-70% of the time now.
Sometimes it won't complete at first, and then after erasing and
retyping once or twice it'll show the completions. Thanks for the
quick fix though!

On Sunday, 14 September 2014 at 20:42:54 UTC, Andrei Amatuni
wrote:
> On Sunday, 14 September 2014 at 20:06:13 UTC, Idan Arye wrote:
>> On Sunday, 14 September 2014 at 03:22:35 UTC, Andrei Amatuni
>> wrote:
>>> On Saturday, 13 September 2014 at 15:19:56 UTC, Idan Arye wrote:
>>>> Version 1.2.0 is out now. I've added the command :DUsyntaxCheck, :DUlsyntaxCheck :DUstyleCheck, and :DUlstyleCheck to run Dscanner's syntax or style checks and store the results in the quickfix or location list. As per Vim's conventions for commands that update these lists, it'll automatically jump to the first entry unless the command is called with a bang.
>>>>
>>>> GitHub repo: https://github.com/idanarye/vim-dutyl
>>>> vim.org page: http://www.vim.org/scripts/script.php?script_id=5003
>>>
>>> I just updated both Dutyl and DCD and something broke along the way. I can see that Vim is communicating with DCD because the DCD server log shows that it received a request after a dot completion, but nothing shows up in Vim.
>>
>> The problem was with Dutyl - I used the `uniq` function, which
>> apparently was bleeding
>> new(https://github.com/LaTeX-Box-Team/LaTeX-Box/issues/190#issuecomment-47459338).
>>
>> The fix is in `develop` now. It worked for me(on my Windows
>> installation - which has a not-as-up-to-date version of Vim as my
>> Linux installation) - let me know it works for you and I'll make
>> it an official bugfix.
>
>
> Just updated it. It's working about 60-70% of the time now.
> Sometimes it won't complete at first, and then after erasing and
> retyping once or twice it'll show the completions. Thanks for the
> quick fix though!

I've noticed these things too. Might be an off-by-one mistake
with the byte position calculation. That'll have to wait for the
next bugfix version though - I've just released the bugfix for
the `uniq` problem(v1.2.1).

OK, version 1.3.0 is out. I fixed that off-by-one mistake and added some tags-related features:

 * A new command - :DUupdateCTags - for updating the tags file
 * DUjump and friends now push to the tag stack, so you can jump back with CTRL+T.

On Thursday, 14 August 2014 at 22:20:52 UTC, Idan Arye wrote:
> GitHub repo: https://github.com/idanarye/vim-dutyl
> vim.org page: http://www.vim.org/scripts/script.php?script_id=5003
>
> The main problem with my Vim plugin for DCD(placed inside the DCD repo) is the need to set the import paths manually. It was a manual task that the user had to do: DCD doesn't know the import path the current project is using. Vim doesn't know either.
>
> Luckily - DUB knows. So instead of separate Vim plugins for different tools, each operating it's own tool alone, I wanted to create one plugin that'll operate both DUB and DCD - one that can get the list of import modules from DUB and send it to DCD. That's how Dutyl was born.
>
> Currently, Dutyl's only features are using DCD for autocompletion and for DDocs, but it has a module system that allows it to add other tools, either to get more functionality or to get backup for features that some tools can't support for specific projects. Like dependency injection but with a real usecase: for projects that don't use DUB, Dutyl can back up to a manually written list of import paths saved in a hidden file in the project's dir.
>
> I'm open for suggestions for other tools and features to add to Dutyl(write them here, or preferably open GitHub issues with them)

How does dutyl know where to look for dub.json? It doesn't seem to find it on my system.