-
krig
Hi! Right now the extension system is very limited. Extensions can add assets like themes and tasks, plus language grammar, lsp and dap support. But even those have very limited APIs. In theory it might be possible to write them in other languages that can target Wasm, but the only infrastructure available is for writing them in rust and the APIs are very rusty, so I actually don't know how possible that is.. You also need WASI support
-
nicoco
I can't do more ATM, but I started investigating when the "debug pytest test case" menu disappeared. I went back up to dcc98485, the regression is still here. so it's either this commit or a commit before...
-
Rob
Which (macOS/iOS) clients are people using to participate here? (I have tried Monal IM and converse.js, but the experience is very “subpar”…)
-
krig
I’m also using Monal and it’s not great no, it just basically works. I also use Fluux Messenger on mac which is more featureful
-
krig
@nicoco hmm that commit seems unlikely, but I have been doing some cleanup/clippy stuff that could have introduced a bug..
-
krig
@nicoco do you have an example project and steps for reproducing the problem? Rust debugging still works with the gutter icon so it seems to be something with the python code specifically
-
GnarlyOtaku
> Which (macOS/iOS) clients are people using to participate here? (I have tried Monal IM and converse.js, but the experience is very “subpar”…) My Mac toting friends love fluux. I don't mind it either but a lack of omemo support is something i can't stand ↺
-
nicoco
> @nicoco do you have an example project and steps for reproducing the problem? Rust debugging still works with the gutter icon so it seems to be something with the python code specifically Sure! https://git.sr.ht/~nicoco/gram-debug-regression 1. clone 2. open with gram 3. run `uv sync` to install pytest (or have pytest available globally somehow) 4. open `test_stuff.py` 5. The gutter ▶️ launch tests, but does not open a menu allowing to chose between "running the test case" and "launch debugger for the test case" ↺
-
krig
thanks!
-
nicoco
> My Mac toting friends love fluux. I don't mind it either but a lack of omemo support is something i can't stand siskin-im was fine (not awesome) when I was apple-jailed by my previous employer. gajim is OK but it's GTK, so generally not liked by apple people. some people enjoy TUI clients, there is profanity and poezio that work fine (not much experience with them, I actually dislike TUIs so...) ↺
-
mort
> So I think everything except the repl is solved now, and the repl barely works anyway... so I merged the fixes Remember that the repl thing isn't really to fix a problem, it's just cleaning up things a tiny bit by not depending on async-std. It might be that reverting the change to repl and keeping it on smol+async-std is the right choice here
-
mort
I honestly didn't know gram/zed supported Jupyter notebooks before investigating what depends on async-std lol
-
mort
> Which (macOS/iOS) clients are people using to participate here? (I have tried Monal IM and converse.js, but the experience is very “subpar”…) BeagleIM is the best client I've found on macOS. It works .. mostly satisfactorily. Only issue I've had is that it sometimes logs me out, but it notifies me and then I can right click my account in account settings and re-enable it. On iOS I use Monal and it's pretty terrible, it hides the last message behind the text input. I wish I knew of a better alternative. On Linux I use Dino and it's great.
-
krig
@mort the repl stuff should work again now, though I have barely looked at it before and it is really bare-bones.. Definitely needs some work to be usable
-
nicoco
oh yes, beagleim not siskim-im sorry
-
krig
@nicoco found it, pushed a fix now.. I cleaned stuff a bit too aggressively when cleaning out collab stuff and managed to remove the debug locator stuff for the builtin languages. I guess rust was broken too but I never use that so I didn’t know what it was supposed to do 😅
-
emilinya
I guess the async propblems you have had stem from gram using multiple async runtimes for some reason. I wonder if we could remove smol and keep tokio as the sole runtime. I'll play around a bit to get an idea of the feasibility and scope of such a chance
-
krig
yeah I wonder why they picked smol to begin with
-
emilinya
Good question, smol advertises itself as a small and fast runtime, but for an application like gram, a more heavy duty runtime like tokio seems more appropriate. You then also get all the benefits that come with using the de facto standard runtime