HedgeDoc VS fzf

Nice and simple. I feel the only lacking feature for a basic blog is having unlisted blog posts, which is very handy when you want to share it to proof-readers. This can be done on google doc/hedgedoc [0] for sure, but then when porting there are very often typos creeping in.

[0] https://hedgedoc.org/

Maybe Hedgedoc will fit these needs? You can use markdown to format. https://hedgedoc.org/

If self-hosting is an option for you I would recommend that you go with HedgeDoc. Completely open source, you get all the features you asked for including real time collaboration.

You can give HedgeDoc (https://hedgedoc.org/) a try as a replacement for Google Docs.

It is the one that works best for concurrent editing IMO (but it is markdown which can be a problem for some)

I use one singular HedgeDoc document for that purpose. It's not exactly the same intent as Google Keep, but it's an awesome project I use anyway and fills the role perfectly for me personally.

HedgeDoc is a web-based, self-hosted, collaborative markdown editor. This open-source option allows a team to easily share ideas on notes, graphs and presentations in real-time. troubleshootmertr finds it a good option "for knowledgebase."

HedgeDoc [0] allows you to collaborate in markdown, and also create slides.

[0] https://hedgedoc.org/ and https://demo.hedgedoc.org/slide-example?both

For writing Markdown documents I use Hedgedoc.

fzf : https://github.com/junegunn/fzf

Those are the most used aliases in my gitconfig.

"git fza" shows a list of modified/new files in an fzf window, and you can select each file with tab plus arrow keys. When you hit enter, those files are fed into "git add". Needs fzf: https://github.com/junegunn/fzf

"git gone" removes local branches that don't exist on the remote.

"git root" prints out the root of the repo. You can alias it to "cd $(git root)", and zip back to the repo root from a deep directory structure. This one is less useful now for me since I started using zoxide to jump around. https://github.com/ajeetdsouza/zoxide

> my history is so noisy I had to find another way

The fzf search syntax can help, if you become familiar with it. It is also supported in atuin [2].

[1]: https://github.com/junegunn/fzf#search-syntax

[2]: https://docs.atuin.sh/configuration/config/#fuzzy-search-syn...

You call it with `n` and get an interactive fuzzy search for your directories. If you do `n ` instead, it’ll start the find with `` already filled in (and if there’s only one match, jump to it directly). The `ls` is optional but I find that I like having the contents visible as soon as I change a directory.

I’m also including iCloud Drive but excluding the Library directory as that is too noisy. I have a separate `nl` function which searches just inside `~/Library` for when I need it, as well as other specialised `n` functions that search inside specific places that I need a lot.

¹ https://github.com/sharkdp/fd

² https://github.com/junegunn/fzf

View on GitHub

I do find the history pager stuff interesting, but ultimately not of tremendous use for me. I rebound all my history search stuff to use fzf[1] (via a fish plugin for such[2]), and so haven't been aware of the issues

[1] https://github.com/junegunn/fzf

[2] https://github.com/PatrickF1/fzf.fish

You can also use fzf with ripgrep to great effect:

[1]: https://github.com/junegunn/fzf/blob/master/ADVANCED.md#usin...

There are two plugins allowing us to use fzf in Vim: the native fzf plugin directly installed with fzf, and fzf.vim. The second plugin is built on the first one.