Thiago Padilha

> @jamessan Saw the pipes stuff in vim-gnupg and neovim, should have been more optomistic. If communication is exclusively with pipes, then my understanding is that it won't hit the...

FWIW this is what I'm currently using as a workaround: ```python import typer import asyncio import functools from typing import Any, Callable, Coroutine, ParamSpec, TypeVar P = ParamSpec("P") R =...

I'm aware of the problem and have plans to address it after the first release(even mentioned in the new bountysource campaign). Some other related discussion: https://github.com/neovim/neovim/issues/2224#issuecomment-84730773

> Or even before the first release? :grin: https://tarruda.github.io/articles/neovim-smart-ui-protocol/ Yes. It may seem like this will hurt neovim stability and hold a first release even further, but as the post...

> Is there a issue or a repo (for the Typescript proof of concept) I can watch the state of smart ui protocol? I didn't find something on this issue...

> No. I'd define the RPC layer to be UTF-8 (error messages) resp. binary where needed. > > It would be really nice if nvim determines whether any given piece...

I just found out that OpenAI has a responses API implementation in the official gpt-oss repository. It could potentially be used as a reference for llama.cpp: https://github.com/openai/gpt-oss/tree/main/gpt_oss/responses_api This implementation supports...

As a temporary workaround, I've added this to my `.profile`: ``` if [ -z "$SSH_AUTH_SOCK" ]; then GCR_SSH_SOCK=/run/user/$(id -u)/gcr/ssh if [ -S $GCR_SSH_SOCK ]; then export SSH_AUTH_SOCK=$GCR_SSH_SOCK fi fi ```

I was under the impression some of these were already implemented in arabic.c/farsi.c . Are those implementations broken?

@bfredl will this be possible after #2077?