Fork me on GitHub
#cursive
<
2024-03-07
>
onetom01:03:42

@U0567Q30W how do u schedule the updating of the documentation? for example, it would be useful to put what u said about the "custom port file" in the mailing list announcement email into https://cursive-ide.com/userguide/repl.html#remote-repls so i can just point my colleagues to it to learn about it. the related https://github.com/cursive-ide/cursive/issues/2559 PR also mentions > it would be easier to be able to run a script before the REPL starts up that retrieves the host IP and sets it which made me wonder whether it's possible somehow with the current implementation, because that would be really flexible, if we wouldn't need to be stateful about it by creating actual files. of course spawning processes comes with a lot of complexity too... i was also wondering what should i put into port files, if im using socket repl connections? also repl://..., since the uri scheme is ignored? then i was also wondering how to make a remote nREPL connection through a https://nrepl.org/nrepl/usage/server.html#using-clojure-cli-tools, instead of a host & port?

$ mkdir -m go-rwx nrepl-test
$ clj -M:nREPL -m nrepl.cmdline --socket nrepl-test/socket

onetom01:03:11

i noticed you have updated some of the screenshots, showing the new jetbrains ui 🙂 niiice!

onetom01:03:41

ah, nvm, i just noticed the version selector below the toc of the user guide!

p-himik11:03:05

Would it be possible to add such changelogs to this section in the plugin update dialog?

cfleming06:03:16

Currently the doc update is a pretty manual process due to the screenshot generation. I try to keep on top of it, but it occasionally gets away from me and becomes a big pile of work. I recently spent a good couple of days updating various versions’ worth, so it’s fairly up to date now (although still with some big gaps that need documenting).

cfleming06:03:28

I’ll try to add those changelogs there, yes.

👍 1