1. 14 Jun, 2021 1 commit
  2. 14 Mar, 2021 1 commit
  3. 04 Mar, 2021 1 commit
  4. 01 Mar, 2021 1 commit
  5. 23 Feb, 2021 1 commit
  6. 18 Feb, 2021 1 commit
  7. 17 Feb, 2021 2 commits
  8. 16 Feb, 2021 1 commit
    • Héctor Mesa Jiménez's avatar
      split project settings into shared and local parts · 4a8234a4
      Héctor Mesa Jiménez authored
      When working with certain languages, it could be useful
      to keep the `.kateproject` file tracked by a VCS and share
      the global settings (just like .kateconfig). However, it
      is often needed to adapt that file in order to work in a
      local workspace (hard-coded paths for LSP, build, etc.),
      but right now you are forced to track the whole configuration
      or to keep `.kateproject` out from the repository.
      This patch allows to separate the project settings in two
      files: the shared one (the good old `.kateproject`), and
      a local one.
      When a `.kateproject` file is found, the plugin will look
      for the local file, and when found, its values will take
      The file for the local part of the project settings follows
      the same convention than the project notes file:
      If the value defined in the local part is an object, it will
      be merged with the object in `.kateproject`. Otherwise, the
      local value will override completely the shared value.
      One use case is to allow the LSP server to be aware of a
      python module installed only in a virtual environment.
      Since this changes uses the function to merge json object
      from the lspclient plugin, that function is moved to the
      shared folder. Tests in kate/autotest.
  9. 06 Feb, 2021 2 commits
  10. 05 Feb, 2021 1 commit
  11. 29 Jan, 2021 2 commits
  12. 18 Jan, 2021 1 commit
  13. 09 Jan, 2021 2 commits
  14. 06 Jan, 2021 2 commits
  15. 04 Jan, 2021 1 commit