monkoose / fzf-hoogle.vim Goto Github PK

Every time I press enter an i gets inserted. I'm using the latest neovim git version together with the latest fzf and fzf-vim.

Before pressing enter:

After pressing enter:

This happens regardless of what is typed in the search field before hand.

If you start fzf-hoogle with :Hoogle! it will open window in new tab, but when you hit enter to research with new query it opens just default window because in sink* just :Hoogle is used.
Not sure how to implement it currently.

I installed Hoogle today and using it from the command line and with server works but no results show up when using through fzf hoogle.

My config:

call plug#begin()
  Plug 'monkoose/fzf-hoogle.vim'
  Plug 'junegunn/fzf', {'dir': '~/.fzf', 'do': './install --all'}
call plug#end()

let g:hoogle_path='/usr/bin/hoogle'

Hi, thanks for the great extension.

I noticed the following error, when running :PlugUpdate.

I think it's due to changes in the repository that lead to this behavior.

I think these changes were not introduced by me (the user). At least not intentionally. And this exact same scenario happened on two different machines with different operating systems.

It can be worked around with:

cd ~/.vim/plugged/fzf-hoogle.vim
git reset --hard

Arch Linux
NVIM v0.5.0-245-g1bfccf028
jq-1.6
Hoogle 5.0.17.3
fzf 0.20.0 (30577b0)

minirc.vim

call plug#begin()
Plug 'junegunn/fzf', {'dir': '~/.fzf', 'do': './install --all'}
Plug 'monkoose/fzf-hoogle.vim'
let g:hoogle_path = '/home/user/.local/bin/hoogle'
call plug#end()

Any ideas?

Hi, thanks for this amazing plugin!
Is it possible to have fzf-hoogle read from a local hoogle server? I'd like to be able to fuzzy search any of my local packages

Because on the hackage some base packages changed some html and on /src/ they added type annotations on mouse hover (that change internal html a lot), current source preview of fzf-hoogle.vim broken and looks ugly.
Possible solution - fix it for this packages, or just completly remove the code with this feature and just open browser tab with source code.

Hi! @monkoose! I just installed fzf-hoogle.vim and upon looking up some stuff, the right pane is nothing but raw JSON:

System infos:

• jq 1.6
• Fedora 31
• ZSH 5.7.1
• curl 7.66.0

Sometimes getting source code with curl is slow. There is ways for optimizations like caching previously requested pages or maybe using haskell haddock local documentations. Or maybe use asynchronous approach with job_start()

Is there a way to disable fzf-hoogle: hoogle is not installed. Plugin disabled. or maybe start the plugin only for .hs files ? I have a per project hoogle installed via nix-shell. As soon as I am out editing any file, I now get the warning (which is not helpful when editing markdown).
neovim has a vim.notify interface that can be helpful for thins kind of message

I added
--bind "ctrl-x:execute(echo {} | xsel -i)" to fzf parameters
it kind of works but the display is messed up unless I exit back to vim

Once in a while I experience a stack smashing error after pressing with a search query, unfortunately the error message is quite bare and I haven't been able to reliable trigger the error. My neovim simply immediately quits and the shell reports a stack smashing error and neovim being terminated by a sigabrt. Would you have any clue how I'd be able to gather more information to debug this error? I saw a commit for fixing an error related to empty searches, this is not what causes this error given that I've experienced the stack smashing error with searches which obviously do yield results such as searching for sort.

Luckily I haven't had any big problems but I think this is quite a severe bug given that it causes data loss. This is because when neovim is forcefully killed by the sigabrt nothing is saved nor is it recoverable by undofile.

Some version info which might be related:
hoogle 5.0.18
NVIM v0.5.0-dev+933-g4620ad604
Tmux 3.1c-2.1
fish 3.1.2-1744-ga4e2a3c04

I suspect this might have something to do with hoogle given that a stack smashing error is related to gcc and given that your plugin runs as vimscript I wouldn't expect it to trigger a stack smashing error, haskell which compiles to c would obviously be a much more likely culprit. Although I do suspect the way hoogle is triggered would cause this error.

The example text has a muted grey color using the Nord color scheme, however to me it doesn't seem very readable on the given screen shot either.

Nord:

Screenshot:

Perhaps a less muted color should be used or an option given to customize the preview?

Hi,

Thanks for working on this plugin, looks great! I was giving it a try and bumped into this issue.

Is the hoogle_cache.json generated by this plugin? If so, would it be possible to configure the path for it? I'm on NixOS and the plugin installation directory is immutable by default.