#include "file.hpp" hints and completions...
Michael George Hart
michael.george.hart at gmail.com
Sat Apr 5 22:04:12 UTC 2014
As I said it is a low priority issue. But I will really dig into it tonight.
Sent from my iPad
> On Apr 5, 2014, at 4:52 PM, Kevin Funk <kfunk at kde.org> wrote:
>
>> On Saturday 05 April 2014 16:36:32 Michael George Hart wrote:
>> Kevin, you understood correctly...
>> Also, I have the latest build from trunk as of about a month ago
>>
>> This has been an issue for more that two years and I basically lived with it
>> --I always assumed it was some configuration parameter I did not have set
>> correctly.
>>
>> However, with my fresh install of openSuSE 13.1 with a brand new login, I
>> decided to hunt for the configuration parameter; which I didn't find.
>>
>> So, if you know of something that is not obvious I should try please let me
>> know.
>>
>> Thanks
>>
>> Sent from my iPad
>>
>>>> On Apr 5, 2014, at 3:54 PM, Kevin Funk <kfunk at kde.org> wrote:
>>>> On Saturday 29 March 2014 19:27:24 Michael George Hart wrote:
>>>> I have been meaning to ask someone how to get kdevelop4 to do hints and
>>>> completions of header file postfixes with hpp.
>>>>
>>>> If, I for example, what to enter #include "xyz" where xyz is a header
>>>> file
>>>> in my project.
>>>>
>>>> I notice, if xyz is a file postfixed with ".h" the intellisense will
>>>> automatically start giving hints as to what the file maybe.
>>>>
>>>> However, if the xyz is a file postfixed with ".hpp" intellisense offer no
>>>> hints to what the file I maybe attempting to enter. After the file has
>>>> been
>>>> entered there is every indication that kdevelop know the files this
>>>> there.
>>>>
>>>> Is there some configuration parameter I need to set so hints are also
>>>> offered by kdevelop4 as I enter project header files with ".hpp " as
>>>> there postfix
>>>>
>>>> Thanks
>>>>
>>>> *"...Hope is what makes us strong. It is why we are here. It is what we
>>>> fight with when all is lost..."*
>>>
>>> Hey,
>>>
>>> Maybe I'm misunderstand something, but that works fine for me with
>>> KDevelop
>>> 4.6 + master.
>>>
>>> I generated this file in some include dir:
>>> foobar.hpp
>>>
>>> I'm typing this in the editor window:
>>> #include "foo
>>>
>>> => And I get a completion item for "foobar.hpp"
>>>
>>> Greets
>
> I don't think there's a configuration parameter.
>
> KDevelop checks for the following extensions:
>
> "h,H,hh,hxx,hpp,tlh,h++" (cpputils.cpp in kdevelop.git)
>
> I'm wondering what's wrong on your side, as I cannot seem to reproduce the
> problem :/
>
> Greets
>
> --
> Kevin Funk
More information about the KDevelop-devel
mailing list