Ran Shaham

Hi @cherniavskii, I can share my use case if it helps. I have data with much more "columns" (headers) than "rows" (data points). Also, the header text can be quite...

Thanks for the reply. Yes, manually changing this to fish works. I think zed should detect that my login shell is fish and do it automatically, no? Also, the `detect_venv`...

Happens to me as well, both on UNIX and SSHMUX sessions. * OS: vanilla macOS 14 * wezterm: `20231203-124028-e3cd2e93` * neovim: `v0.10.0-dev-2008+g4ee656e4f`

Almost opened another feature request, requesting "call hierarchy". Then I remembered that the technical name for it in LSP world is incoming_calls, and found this :) So I'll add this...

Awesome! thanks!

Hi @folke, I tried it out, and it's not exactly what I expected from a call-hierarchy UI. In such UI I expect the incoming calls entries to recursively have their...

I just looked at: `lua/lsp-setup/utils.lua` and it seems like `opts` are hardcoded. I guess changing the config to support something like that is possible, but maybe you don't want to...

Did anyone find a workaround? I really prefer (and rely on) wezterm's mux feature over tmux, but I can't use neovim inside it, which makes it unusable :(

Worked around it by setting: ```lua client_callback = function(port, _) local cmd = ("neovide --server localhost:%s"):format(port) vim.fn.jobstart(cmd, { detach = true, on_exit = ... }) end, ```

Hi @amitds1997, sorry for disappearing. I actually stopped using neovide with remote-nvim, since it was less convenient than tmux+TUI (I wanted persistent terminals in the remote host). I didn't test...