diff --git a/content/posts/2023-06-23-neovim-telescope-freebsd-problems/index.md b/content/posts/2023-06-23-neovim-telescope-freebsd-problems/index.md
new file mode 100644
index 0000000..4583893
--- /dev/null
+++ b/content/posts/2023-06-23-neovim-telescope-freebsd-problems/index.md
@@ -0,0 +1,44 @@
++++
+# 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', 'neovim' ]
+
+# showBreadcrumbs = true
+# showDate = false
+# showReadingTime = false
+# showWordCount = false
+# showPagination = false
+
+# feed_exclude = true
+# site_exclude = true
+
+draft = true
+
++++
+
+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.
+
+## TODO: fix formatting, add text
+
+cd into `.local/share/nvim/lazy/telescope-fzf-native.nvim`
+
+make sure GNU make is installed `pkg install gmake`
+
+execute `gmake` which creates the file `build/libfzf.so`
+
+now telescope worked for me.
+
+lua_ls still won't work (platform not supported)