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

README - update writelto, attempts to fix #169 #196

Open
wants to merge 2 commits into
base: main
Choose a base branch
from

Conversation

kieranjol
Copy link

I'm almost certain that this is fairly wrong in a few ways, but maybe it'll get the ball rolling. Any edits/fixes are very welcome..

README.md Outdated
@@ -108,11 +108,9 @@ Whenever a tape is ejected, the script will export the tape’s index (as an XML
To write data onto a tape, run the following command:

```
writelto
writelto -t $tape_serial /Volumes/$tape_serial
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That would write the content of the lto tape onto the same lto tape. A better example would be:
writelto -t $tape_serial $any_other_place

@kieranjol
Copy link
Author

Lol I'm sorry, I'm going pretty blind here.looks like your PR would make this redundant as the docs would be correct of that was merged?

@privatezero
Copy link
Member

I think that even after that PR is merged, the docs still should be updated along the lines you are doing! I see that PR more as a check against data not being entered initially. People should probably know that they need to add both those values for a complete executable command.

@@ -108,11 +108,9 @@ Whenever a tape is ejected, the script will export the tape’s index (as an XML
To write data onto a tape, run the following command:

```
writelto
writelto -t $tape_serial $source_directory
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry to nitpick, but I think maybe writing inputs as variables in the docs might confuse some people who aren't familiar with $ denoting a user changeable variable?

I never am sure of the most intuitive way to denote user inputs in docs, but maybe TAPE_SERIAL and SOURCE_DIRECTORY, or possibly [Tape Serial] [Source Directory]? (Although when I have used the latter format I often find myself having to explain that the [ ] are not part of the command. I wonder if there is any common precedent across amiaos repos?

@kieranjol
Copy link
Author

I agree, maybe the all caps, with an example command to make it extra clear?

@privatezero
Copy link
Member

I think that makes sense!

Copy link
Member

@retokromer retokromer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it not be clearer to use two flags: one for the tape_serial and one for the source_directory?

@retokromer
Copy link
Member

ping

@retokromer
Copy link
Member

ping ping

@retokromer
Copy link
Member

Has this PR not been superseded by ed8ccab?

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.

4 participants