Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't find Custom pages #364

Closed
canh25xp opened this issue Apr 18, 2024 · 3 comments
Closed

Can't find Custom pages #364

canh25xp opened this issue Apr 18, 2024 · 3 comments

Comments

@canh25xp
Copy link

canh25xp commented Apr 18, 2024

I'm follow this instruction to create my own personal pages. But it didn't seem to work.

Step to reproduce :

  1. Install it
sudo apt install tealdeer
  1. Find Custom pages dir : tldr --show-paths
Config dir:       /home/michael/.config/tealdeer/ (OS convention)
Config path:      /home/michael/.config/tealdeer/config.toml
Cache dir:        /home/michael/.cache/tealdeer/ (OS convention)
Pages dir:        /home/michael/.cache/tealdeer/tldr-pages/
Custom pages dir: /home/michael/.local/share/tealdeer/pages/
  1. Add my customs pages:
/home/michael/.local/share/tealdeer/pages
└── foo.page.md

Content of foo.page.md:

# foo

> Foo

- Test

`foo --bar`
  1. Try it: tldr foo
Warning: Page `foo` not found in cache.
Try updating with `tldr --update`, or submit a pull request to:
https://github.com/tldr-pages/tldr

I tried update the cache by tldr --update. But it still didn't work. Am I missing something ?

tealdeer version : 1.5.0
OS : WSL Debian

@niklasmohrin
Copy link
Collaborator

niklasmohrin commented Apr 18, 2024

Hey, the docs are already displaying an upcoming change to the naming scheme of custom pages that has not been released yet. For 1.5.0, the correct description is here: https://github.com/dbrgn/tealdeer/blob/v1.5.0/docs/src/usage_custom_pages.md

Closing as duplicate of #358

@niklasmohrin niklasmohrin closed this as not planned Won't fix, can't repro, duplicate, stale Apr 18, 2024
@brainwo
Copy link

brainwo commented Jun 4, 2024

This issue should be pinned, I came with the same question after minutes of debugging what could possibly be wrong in my setup.

If not this issue then #358, but #358's title isn't that descriptive.

@niklasmohrin niklasmohrin pinned this issue Jun 6, 2024
@niklasmohrin
Copy link
Collaborator

Sure, I guess this could help in the meantime

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants