You can not select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
33 lines
1.1 KiB
33 lines
1.1 KiB
+++
|
|
# vim: ft=markdown
|
|
title = 'Neovim, Telescope, FreeBSD: problems?'
|
|
summary = '''I dropped my old configuration that I practically
|
|
copied from other people for Neovim. I'm now using AstroNvim...'''
|
|
date = '2023-06-23T07:50:32+02:00'
|
|
# lastmod = ''
|
|
categories = [ 'computerstuff' ]
|
|
tags = [ 'freebsd', 'openbsd', 'neovim' ]
|
|
|
|
+++
|
|
|
|
I've been using other peoples config for Neovim for a while and although
|
|
it worked well for the most files I was a bit unhappy because I rarely
|
|
understood most configuration parts of it.
|
|
|
|
As I'm not working in IT or other computer related areas I'm not the one
|
|
that feels the need to dive into this deeply. I'm using AstroNvim for now
|
|
(I also had a look at NvChad) and I'm quite happy since today when I finally
|
|
got to fix the problem with Telescope (fzf) which never worked before on
|
|
either FreeBSD nor OpenBSD.
|
|
|
|
Move into `.local/share/nvim/lazy/telescope-fzf-native.nvim` directory.
|
|
|
|
Make sure GNU make is installed `pkg install gmake` on FreeBSD or
|
|
`pkg_add gmake` on OpenBSD.
|
|
|
|
Execute `gmake` which creates the file `build/libfzf.so`
|
|
|
|
Now Telescope worked for me.
|
|
|
|
lua_ls still won't work (platform not supported).
|