-
Notifications
You must be signed in to change notification settings - Fork 81
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zsh-autosuggestions work in floating window, but not in 'normal' mode / quickfix window #36
Comments
You can use |
I'm putting it down to this issue: neovim/neovim#7018 EDIT: Changing zsh-autosuggestions highlight colours makes them visible. I think the highlight colour I'm using isn't visible in Also figured out that I just needed to set the background colour to the same as my in-built colorscheme. Thanks for building this. Really useful. |
For anyone else with this issue, it's actually caused by iTerm color settings as described here: zsh-users/zsh-autosuggestions#416 (comment) |
Hopefully this is clear from the screenshots. When Floatterm is invoked with default

floaterm_type
, i.e. this global variable is not set, the terminal appears in a floating window, and suggestions fromzsh-autosuggestions
are visible.However, if

g:floaterm_type
is set to'normal'
, then they are not visible.Another issue that is visible in these screenshots is that when the window type is set to
'normal'
then the colorscheme is inherited from whatever has been set in myinit.vim
. However, in floating window mode the colorscheme is something else. I can create a separate issue for this if not answered here.EDIT: Ideally I'd like a terminal in a fullscreen buffer with no borders that I can toggle with a shortcut. Is setting
g:floaterm_width
, andg:floaterm_height
to1
the best way to do that, or is there a better way? Do I even need this plugin to do that?The text was updated successfully, but these errors were encountered: