State of documentation

[Sven Brauch]

> Ah, I see. So is it the *first* save that makes the difference?
Yes, exactly.

I don't really know about the autocompletion question! This always
worked well for me, and KDevelop used to offer autocompletion as soon
as the current expression was long enough (3 characters, I think).
Doesn't it do that for you?

Bye,
Sven

2011/5/30 Wolfgang Bangerth <bangerth at math.tamu.edu>:
>
>> One hint from me, too: You write "This happens in the background after
>> you start KDevelop but it doesn't happen as you type along.". This is
>> not entirely correct; KDevelop will reparse files as you edit them
>> every 0.5 seconds or so. The reason it didn't work in your case was
>> that the file was not saved *at all*, and thus didn't have a mime type
>> set (so KDevelop could not know it's actually meant to be C code you
>> were writing).
>
> Ah, I see. So is it the *first* save that makes the difference?
>
> Do you happen to know the answer to the other question I had: How to
> *automatically* get auto-completion, without having to do Ctrl+Space?
>
> Thanks
>  W.
>
> -------------------------------------------------------------------------
> Wolfgang Bangerth                email:            bangerth at math.tamu.edu
>                                 www: http://www.math.tamu.edu/~bangerth/
>