dotfiles VS skim

I ended up implementing the 1% of features I use most myself and using a plugins for navigating and managing lists of checkboxes. I've used this setup for a few years now and can't imagine life without it.

I use tmuxp for this with my projects set up like this and I use a script to open the ones I'm currently working on in a single tmux session.

Exactly the same as me. I even use fzf to search for and open my tmuxinator projects.

I tried vimwiki for a while but I found I used a tiny subset of its functionality and couldn't get it to respect my choice of syntax highlighting for markdown. It set me off in the right direction though.

The fact that it's _just_ a directory full of markdown files allowed me to easily migrate to my own home-grown setup that reimplements the three keybindings I actually used.

https://github.com/peteryates/dotfiles/blob/master/nvim/.con...

Everything is configured with tmuxp and I can set the whole thing up with a single command.

It's ideal for dotfiles. Here are mine

> I can rebuild my configuration(Aside from some fussy embedded toolchains) in half an hour or so. VS code, a few different linters, swissknife, stack tabs, timestamper, indenticator, pylance.... done.

I can clone my dotfiles repo[0], run a single command that installs all my dependencies[1], another that links my config and I'm done. That gives me a fully-configured neovim with all my plugins (thanks vim-plug) within 2 minutes.

[0] https://github.com/peteryates/dotfiles/

[1] https://github.com/peteryates/dotfiles/blob/master/Makefile#...

I really like using something like fuzzy search for menus like these. https://github.com/Cloudef/bemenu is pretty cool in that it works both in a terminal, X11 and on Wayland, so if you want to do something graphical later you can easily migrate. There's also fzf and skim, which work similarly but are only for the terminal.

Current profiles (to be improved upon): | Profile | Details | | ---------------- | ------------------------------------------ | | default | fzf-lua defaults, uses neovim "builtin" previewer and devicons (if available) for git/files/buffers | | fzf-native | utilizes fzf's native previewing ability in the terminal where possible using bat for previews | | fzf-tmux | similar to fzf-native and opens in a tmux popup (requires tmux > 3.2) | | max-perf | similar to fzf-native and disables icons globally for max performance | | telescope | closest match to telescope defaults in look and feel and keybinds | | skim | uses skim as an fzf alternative, (requires the sk binary) |

There’s also a variety of fuzzy finders like https://github.com/lotabout/skim or fzf. Basically the same thing, but different interface.

Have you ever tried sk? skim is an fzf re-write in 🦞. While I use it occasionally, I never really incorporated fzf into my workflow so I'd be interested to hear your opinion.

I’m not familiar at all with fzf, but I do know that skim supports this.

You state that as a blank and white fact, but there's nuance.

https://github.com/lotabout/skim/issues/317#issuecomment-652...

fzf skim

Agreed, but use skim instead