Hi,
I played a little bit. And have some questions to ask. What it the purpose
of <project>.tags file in ~/.cache/gnome-builder/tags?
From debug output the program complains "Error open file ...". It is clear
since the file is not there. clang completion gives so many
C functions such so it becomes hard to use completion. Ideally, I would
like to have at least something similar to OmniCppCompletion (in Vim) in
gtkmm project.
Can we summarize all possible completion options here? I may help with
documentation. Thus,
two options:
1) clang
2) ctags
|-- Automatically generated file (Describe general process for end users)
|-- Custom ctags file. (How to make file, Where to place file,
Configuration etc)
Common questions:
Difference between C and C++ completion if any.
> On 02/01/2017 08:56 PM, Pavlo Solntsev wrote:
>> How can I manually rebuild ctags with parameters? I saw in source code
>> some parameters were provided. I would be useful if we can see a
>> massage in status bar "ctags was updated" if buidler does this
>> automatically.
>
> It updates with a 10 seconds delay after a save. Since we always try to
> keep things up to date, having a status message isn't very useful. For
> debugging, try running with more verbosity to get more information using
> -vvvv (the last v is only useful if you've compiled with --enable-tracing).
>
> We do not currently have a way to alter the ctags parameters. But if you
> are using autotools, we don't run the ctags command anyway. We defer to
> "make ctags" to perform the tags generation.
>
> -- Christian
> _______________________________________________
> builder-list mailing list
> [email protected]
> https://mail.gnome.org/mailman/listinfo/builder-list
>
______________________________
Розпродаж жіночого, чоловічого та підліткового трикотажу від українського
виробника
http://go.meta.ua/anabel_sales_ua
_______________________________________________
builder-list mailing list
[email protected]
https://mail.gnome.org/mailman/listinfo/builder-list
