Skip to content

Remove redundante variable docs from README #681

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

Merged
merged 2 commits into from
Jan 5, 2022
Merged

Conversation

scop
Copy link
Owner

@scop scop commented Jan 4, 2022

While working on #678, I noticed we have some redundant and inaccurate descriptions in README for some variables. I'm sure some of these are not FAQ's these days any more either.

This removes the redundant descriptions from README, moves it elsewhere for tar, and generally makes the info a bit less scattered. I think we should make the main README.md even smaller going forward, but that's something for another PR.

scop added 2 commits January 4, 2022 21:51
While at it, make semantics of setting the variable more accurate: it
needs to be set before the *tar* completion is sourced (not
bash_completion), and it needs to be set to a non-null value.
They are largely duplicating what we have in doc/bash_completion.txt,
and inaccurate in saying the vars can be set to anything -- they need to
be set to a non-null value.
@akinomyoga
Copy link
Collaborator

Maybe we can change the extension of doc/bash_completion.txt from .txt to .adoc so that GitHub renders the content of the file (just like Markdown files). Then we can put a link to the file in README.md.

@scop scop merged commit 9357f35 into master Jan 5, 2022
@scop scop deleted the docs/variable-docs branch January 5, 2022 12:49
@scop
Copy link
Owner Author

scop commented Jan 5, 2022

Yup, either that, or change all docs to markdown. Markdown covers our needs fine, and more people are familiar with it than with asciidoc.

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 this pull request may close these issues.

2 participants