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

-l option for tldr command is ambiguous, inconsistent with help message #108

Closed
Producdevity opened this issue Oct 30, 2023 · 3 comments · Fixed by #103
Closed

-l option for tldr command is ambiguous, inconsistent with help message #108

Producdevity opened this issue Oct 30, 2023 · 3 comments · Fixed by #103

Comments

@Producdevity
Copy link

GitHub Issue Title:

-l option for tldr command is ambiguous, inconsistent with help message

Issue Description:

Problem Description:

When running tldr -h, the help message indicates that -l can be used as a shorthand for --list. However, using tldr -l results in the following error:

tldr: option -l is ambiguous

Steps to Reproduce:

  1. Run tldr -h to view available options.
  2. Run tldr -l.

Expected Behavior:

The -l option should behave the same as --list, listing all entries in the local database.

Actual Behavior:

An error message is displayed indicating that the -l option is ambiguous.

Environment:

  • OS: macOS 14.0 (23A344)
  • tldr version: v1.6.0
  • installer: Brew

Additional Information:

The --list option works as expected when used in place of -l.

Possible Solutions:

  • Update the help message to remove -l if it is not supported.
  • Fix the ambiguity of the -l option to make it function as described.

If you can identify the specific file or code section where this issue originates, I'd be happy to submit a pull request to resolve it.

@kbdharun kbdharun transferred this issue from tldr-pages/tldr Oct 31, 2023
@kbdharun
Copy link
Member

Thanks for the issue, this would potentially be fixed by #103.

@kbdharun kbdharun linked a pull request Oct 31, 2023 that will close this issue
@Producdevity
Copy link
Author

Thanks for the issue, this would potentially be fixed by #103.

Seems like it! Can we leave this one open until verified?

@kbdharun
Copy link
Member

kbdharun commented Nov 5, 2023

Thanks for the issue, this would potentially be fixed by #103.

Seems like it! Can we leave this one open until verified?

Yep, merging that PR will automatically close this one. Till that I would suggest leaving it as it is.

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

Successfully merging a pull request may close this issue.

2 participants