01:45 <ckanbot> [CKAN] politas opened issue #2174: Implement smart CLI autocompletion https://git.io/vFcxl

02:04 <ckanbot> [CKAN] HebaruSan commented on issue #2174: To see how autocompletion is implemented, take a look in `/etc/bash_completion.d/` if you're on a Debian-based distro. Basically you write a shell function that parses your partial command text and returns the valid options, and then you run some variant of the `complete` builtin to bind it to the command. Doing it properly _might_ require providing CKAN as a proper `.deb` package so we could put a file in `/e

03:51 <ckanbot> [CKAN] HebaruSan commented on issue #2169: After pulling this, three files are showing up as permanently having changes in the working directory even though no actual changes are present according to a diff:... https://git.io/vFCeL

03:59 <ckanbot> [CKAN] HebaruSan commented on issue #2169: After pulling this, three files are showing up as permanently having changes in the working directory even though no actual changes are present according to a diff:... https://git.io/vFCeL

06:35 <ckanbot> [CKAN] politas commented on issue #1888: There were a whole bunch of files with duplicated listings in the csproj file for tests. I removed all the ones that didn't exist. If anyone understands how to make these tests work, please help!!!! I can't get my head around them. https://git.io/vFCU7

06:48 <ckanbot> [CKAN] politas pushed 3 new commits to master: https://git.io/vFCTO

06:48 <ckanbot> CKAN/master 8dd0c27 Paul Hebble: Minor spelling and formatting clean-up

06:48 <ckanbot> CKAN/master f86c4ff HebaruSan: Lowercase v

06:48 <ckanbot> CKAN/master 4d3d978 Myk: Merge #2172 Minor spelling and formatting clean-up

07:02 <ckanbot> [CKAN] politas commented on issue #2174: We do actually have a plan to reduce the size of the registry. @techman83 has done some of the work in KSP-CKAN/NetKAN-bot#58 The idea is to create different repo downloads split up according to a config file (based on KSP versions), which we can then allow the users to select in the CKAN Settings dialog. The client functionality is mostly there, I think it's just a question of setting the default repo different

07:05 <ckanbot> [CKAN] politas commented on issue #2161: A CKAN shell, basically? Seems plausible. https://git.io/vFCT7

07:29 <ckanbot> [CKAN] politas commented on issue #1888: Some additional file changes forced by .gitattributes in that commit. https://git.io/vFneq

19:31 <ckanbot> [CKAN] HebaruSan commented on issue #1888: I'm a little concerned about the implications of using replaced_by with multiple arguments. Presumably this is for the case where I release a mod containing Part 1 and Part 2 and then disappear, and separate people take up separate maintenance of Part 1 and Part 2. But what if my mod also included a Part 3 that no one adopts? Do we want to upgrade users to the replacement mods and lose Part 3? Or do we tell th

19:36 <ckanbot> [CKAN] HebaruSan commented on issue #1888: I'm a little concerned about the implications of using replaced_by with multiple arguments. Presumably this is for the case where I release a mod containing Part 1 and Part 2 and then disappear, and separate people take up separate maintenance of Part 1 and Part 2. But what if my mod also included a Part 3 that no one adopts? Do we want to upgrade users to the replacement mods and lose Part 3? Or do we tell th

19:39 <ckanbot> [CKAN] HebaruSan commented on issue #1888: I'm a little concerned about the implications of using replaced_by with multiple arguments. Presumably this is for the case where I release a mod containing Part 1 and Part 2 and then disappear, and separate people take up separate maintenance of Part 1 and Part 2. But what if my mod also included a Part 3 that no one adopts? Do we want to upgrade users to the replacement mods and lose Part 3? Or do we tell th

19:48 <ckanbot> [CKAN] HebaruSan commented on issue #904: > Well, we have a perfect case at the moment...... https://git.io/vFCXW

23:07 <ckanbot> [CKAN] mathuin commented on issue #2174: I would note that if #2161 is implemented, this feature would be definitely possible within the repl/shell as it's all under CKAN's control. https://git.io/vFC5f

23:47 <ckanbot> [CKAN] politas commented on issue #1888: The reason I chose to mostly duplicate the contents of "#/definitions/relationship" for "replaced_by" in the schema was to limit replaced_by to a single mod. If at some stage there is a compelling argument to extend replaced_by to multiple mods, we could look at that, but the implementation of the concept I have gone with allows only a single replacement.... https://git.io/vFCdM

23:52 <ckanbot> [CKAN] politas commented on issue #1888: The reason I chose to mostly duplicate the contents of "#/definitions/relationship" for "replaced_by" in the schema was to limit replaced_by to a single mod. If at some stage there is a compelling argument to extend replaced_by to multiple mods, we could look at that, but the implementation of the concept I have gone with allows only a single replacement.... https://git.io/vFCdM

23:58 <ckanbot> [CKAN] politas commented on issue #904: > How did that turn out? It could be useful to examine now that the code is moving forward again.... https://git.io/vFCFo