broot.vim icon indicating copy to clipboard operation
broot.vim copied to clipboard

Broot Launching in "Plain Text" and not opening files in vim

Open dardardario opened this issue 2 years ago • 6 comments

I setup this plugin using Vundle and got it installed and ready to go, but I ran into a couple issues.

Issue Description: Initially after the setup running the Broot command would not do anything without any error messages. After looking through the source I tried a few things and changed the start command from br to broot. This change launched brood in a separate split but without the usual formatting:

image

Besides this, trying to open a file from within the plugin still opens it externally from vim and does not seem to work correctly.

Mitigation steps:

  • Re-installing the plugin.
  • Stepping through the Broot command with vim debug + term_start command would fail to run since command br was not recognized +. Seems to be linked to zsh config maybe? + This seems to indicate the the script seems to be going through each function without any other issues
  • Checking broot config + Script did not seem to be editing conf.taml + manually added the lines in the script with no change in output behavior

Since it's my first time posting here I'm not sure what details to post to help diagnose the issue, so some guidance would be appreciated.

dardardario avatar May 18 '22 23:05 dardardario

Hi @dardardario,

I think the first issue is that you haven't installed br as a command in your shell. I think you are using zsh, right? Check out this page of Broot's documentation on how to make the br argument available. This will also allow you to cd with broot :)

If you have done this (or did already), please make sure that vim's term_start uses your zsh under the hood to execute commands. This would explain the case that you did install the br command but vim is complaining about not finding it (because it uses a root zsh or another shell etc.).

Also, I'm using neovim, are you using vim?

lstwn avatar May 19 '22 09:05 lstwn

Hi @Istwn, the br command works in vim when I call the :terminal command and open a shell up in there. When calling it from term_start is pops up with this error: image

Besides this it seems like the plugin started working after a system reset but broot still launches in that weird text mode which mades it difficult to use. It seems like boots conf.toml was not loading properly before then. Any ideas on what that could be?

On my system I'm running zsh with the oh-my-zsh plugin and running regular vim.

What's the best way to check what term_start is using zsh? I think the issue is likely related to that since it seems like its not getting to the part of my zshrc which defines br before it tries calling it.

Thanks for the help!

dardardario avatar May 19 '22 17:05 dardardario

Fixed the "br" command issue by link my ~/.zshrc to my ~/.zshenv. Still running into the issue with no formatting on broot.

Besides this issue which seems to be limited to formatting I have not had other issues: image

Seems like some colors work but the meat of Broot's formatting is not working which makes it hard to tell which file you have currently selected. Any ideas?

dardardario avatar May 19 '22 21:05 dardardario

Hi, I don’t know what the exact problem is. My guess is that this is not related to the plugin but rather related to your vim/zsh configuration. An interesting idea to check out would be to test how a different terminal application that uses colors looks like when started in your term_start environment. Does it lack color support, too? Maybe you can start your debugging journey like this..

If you find a non-configuration related issue with this plugin on your journey let me know!

lstwn avatar May 24 '22 12:05 lstwn

I am also running into this issue running neovim. Using :terminal, br runs fine. :!br does not work. Any ideas?

deanykao avatar Jun 16 '22 16:06 deanykao

I updated this plugin to support

  1. multiple instances of broot running peacefully next to each other (unrelated to this thread though)
  2. broot's updated cli flags (in v1.6.0 broot dropped support for the --out flag on which this plugin relied on)

Maybe (2) caused some issues relevant to this thread (except for color problems, these are related to your config files and terminal emulator). You might want to try again and report if things work properly or not. Hope it helps!

lstwn avatar Oct 02 '22 16:10 lstwn