1. 10 Aug, 2019 1 commit
  2. 19 Jul, 2019 1 commit
  3. 16 Jun, 2019 1 commit
  4. 06 May, 2019 1 commit
  5. 10 Feb, 2019 1 commit
    • Thomas Schöps's avatar
      Clang CodeCompletion: No auto-completion for numbers · e86c5a72
      Thomas Schöps authored
      Summary: When typing a number, code-completion is undesirable in my opinion, since most likely no completion item applies and it only distracts, obstructs the view, or is triggered accidentally. Thus, this patch prevents code completion from automatically getting triggered for numbers. It does not cover all cases (code completion will still show something for floating-point numbers that start with a dot, such as .1f) but should cover the most common cases. Manual completion with Ctrl+Space is still possible.
      
      Test Plan: Tested manually.
      
      Reviewers: #kdevelop, mwolff
      
      Reviewed By: #kdevelop, mwolff
      
      Subscribers: mwolff, brauch, kdevelop-devel
      
      Tags: #kdevelop
      
      Differential Revision: https://phabricator.kde.org/D17915
      e86c5a72
  6. 03 Dec, 2018 2 commits
  7. 20 Nov, 2018 2 commits
  8. 27 Oct, 2018 1 commit
  9. 25 Oct, 2018 1 commit
  10. 23 Oct, 2018 3 commits
  11. 12 Sep, 2018 1 commit
  12. 30 Aug, 2018 1 commit
  13. 20 Aug, 2018 1 commit
  14. 17 Aug, 2018 2 commits
  15. 15 Aug, 2018 3 commits
  16. 13 Aug, 2018 1 commit
  17. 06 Aug, 2018 1 commit
  18. 30 Jul, 2018 1 commit
  19. 20 Jul, 2018 1 commit
  20. 07 Jul, 2018 1 commit
  21. 27 Apr, 2018 1 commit
    • Milian Wolff's avatar
      Group completion requests and only handle the last one · e48c6265
      Milian Wolff authored
      Summary:
      I noticed that we sometimes wait quite long on code completion
      requests, especially when editing header files. The edit operation
      in a header invalidates the preamble, so reparsing will always take
      quite some time. Nothing we can do about that, really. But at least
      we can make sure we don't do work for naught:
      
      The old code just emitted signals whenever code completion is invoked.
      This can happen multiple times while we are editing the header. Since
      the computation takes time, the subsequent completion requests pile
      up and will all be handled eventually. If you are then impatient and
      go to a different file, we will still go through all requests even
      though they are not interesting anymore.
      
      This patch groups the completion requests together with a simple
      timer to ensure we only handle the last request once the current
      completion job has finished.
      
      Subscribers: kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D12298
      e48c6265
  22. 15 Mar, 2018 2 commits
  23. 01 Mar, 2018 1 commit
  24. 26 Feb, 2018 1 commit
  25. 09 Jan, 2018 4 commits
    • Milian Wolff's avatar
      Workaround: find declarations for constructor argument hints · 113deb25
      Milian Wolff authored
      Summary:
      For non-namespaced constructors we can find the declarations by
      manually adding the identifier a second time before the lookup,
      as that gives us the proper QID. This allows us to find the
      declaration for many situations, most notably for most Qt classes.
      
      Subscribers: kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D9745
      113deb25
    • Milian Wolff's avatar
      clang: Improve argument hint code completion · 203b02d4
      Milian Wolff authored
      Summary:
      Previously, the overload candidates never got an DUChain Declaration
      associated, meaning we could not inspect the API documentation in-line
      from the code completion. The reason was that most of the time the
      hinted declaration is also a valid "normal" completion item, and thus
      was found a second time. The findDeclaration call then returned null
      for the second call, since we added the declaration to the exclusion
      set after the first call. Instead, use a separate set for overload
      candidates to fix this. Note that the expanded argument hint item
      is still not showing any documentation in-line... Apparently there's
      more to fix to get this done properly.
      
      While at it, also use the ArgumentHintItem for the situations where
      we (now) find a Declaration, to get proper current-argument
      highlighting.
      
      Then fix the unit test to expect the default arguments. Though
      potentially this is clang-version dependent? Anyhow, this makes the
      test pass for me on my machine with libclang from LLVM 5.0.0.
      
      Reviewers: #kdevelop
      
      Subscribers: kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D9725
      203b02d4
    • Milian Wolff's avatar
      Cleanup: use auto and remove explicit KDevelop:: qualification from identifiers · f1f23ce1
      Milian Wolff authored
      Reviewers: #kdevelop
      
      Subscribers: kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D9721
      f1f23ce1
    • Milian Wolff's avatar
      Cleanup: Reduce amount of ifdefs · 35d1bfa3
      Milian Wolff authored
      Summary:
      Only use one ifdef and store result in a boolean, then use that
      variable elsewhere.
      
      Reviewers: #kdevelop
      
      Subscribers: kdevelop-devel
      
      Differential Revision: https://phabricator.kde.org/D9720
      35d1bfa3
  26. 21 Nov, 2017 1 commit
  27. 18 Nov, 2017 1 commit
    • Milian Wolff's avatar
      kdev-clang: Offer all include paths for code completion · 015141e3
      Milian Wolff authored
      We used to only offer code completion of project paths for local
      code completion in `#include "..."` contexts. And for vice versa,
      we only offered system paths for global code completion in
      `#include <...>` contexts. This is wrong, as the include style
      only changes the order in which a compiler iterates through these
      paths to find an include file. For code completion purposes, this
      is not important.
      
      Now we offer code completion in both path lists always. To show the
      user the right file/dir being included, we don't sort and unify the
      search path list anymore as that potentially changes the final result.
      Rather, we use a hash set to ensure we don't encounter paths multiple
      times and iterate over the search path lists in their original order.
      
      BUG: 386421
      015141e3
  28. 28 Sep, 2017 1 commit
  29. 13 Sep, 2017 1 commit