tldr-pages/tldr-node-client

Follow the XDG Base Directory Specification

Wsine opened this issue · 5 comments

Wsine commented

Expected behaviour

Move the default config file location to ${XDG_CONFIG_HOME:-$HOME/.config}/tldr/tldrrc
Also move the default cache file location to ${XDG_CACHE_HOME:-$HOME/.cache}/tldr

Actual behaviour

Current config file location $HOME/.tldrrc
Current cache file location $HOME/.tldr/cache

Environment

  • Operating system - OSX/Linux
bl-ue commented

This will probably have to go into 4.0.0 as it's a breaking change. Or maybe we can search for both paths for the config file and cache directory.

  • 👍2
vladimyr commented

This will probably have to go into 4.0.0 as it's a breaking change. Or maybe we can search for both paths for the config file and cache directory.

I'm definitely in support both camp because not everyone agrees on XDG and breaking changes should be avoided unless they are absolutely neccessary.

  • 👍3
vladimyr commented

@bl-ue I don't really care about label names but picking bug is problematic because Refined Github lists them in another tab 🙃

  • 👍1
bl-ue commented

No problem. Yeah, refined GitHub is pretty cool, but there were some UI quirks that I didn't like, but I guess that with the amount of features it provides I'll keep it.

By the way, how did you figure out to get that #:~:text=... stuff in the URL? I've seen it before but not from human-typed links like that.

vladimyr commented

but there were some UI quirks that I didn't like, but I guess that with the amount of features it provides I'll keep it.

Same here. FWIW they have a ton of customization options plus they are pretty responsive and welcoming to constructive feedback.

By the way, how did you figure out to get that #:~:text=... stuff in the URL? I've seen it before but not from human-typed links like that.

Sooner or later I'll reveal all of my tricks 😅 https://github.com/GoogleChromeLabs/link-to-text-fragment

  • 😄1
  • ❤️1
  • 👀1