-
-
Notifications
You must be signed in to change notification settings - Fork 4.1k
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
lp: add page #321
lp: add page #321
Conversation
|
||
- Print the output of a command. | ||
|
||
`echo "test" | lp -d {{printer_name}}` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
-d
is demonstrated below, so I'd suggest leaving this example as the simpler echo "test" | lp
(which also applies the "progressive complexity" principle). If you change this, make sure to add "to the default printer" to the command description.
Hi. I implemented all of the changes. I got rid of the lpstat -d command as it appeared to be redundant. Let me know what you think. Thanks. |
|
||
`lp -d {{printer_name}} {{path/to/filename}}` | ||
|
||
- Print N copies of file to default printer (replace N with desired number of copies). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
"of file" --> "of a file"
"to default" --> "to the default"
@Qtrain how about the suggestion not to use |
@waldyrious I'm not sure what you mean. I was under the impression that the descriptions shouldn't have commands in them. So, I'm not really sure how you want me to change it. Would you be able to provide an example? Additionally, I added that line at the suggestion of @lord63 please see above conversation. I apologize for the sprawling commit here to btw. This is my first time attempting to commit to an open source repo so any "hand-holding" is greatly appreciated. Thx! |
Sure, I meant something like this:
|
I'm actually not in favour of having other commands in the description (especially complex expressions with pipes). I'd rather keep it simple and say |
I honestly think we need to balance between general principles (not having commands in descriptions, which I agree) and what's more useful for the user here (straight up giving them the answer they need). "see lpstat command" forces them to an extra step and is not much better than the RTFM problem which tldr aims to alleviate. In this specific case I believe the commands are justified, especially since they're so short and simple. |
hello, I added another commit. Please let me know what you think. Thanks. |
Sorry for all of the novice mistakes. I deleted, re-forked and re-cloned the repository in an effort to get around the error with this line -[[ -z "$MD_FILES" ]] || GEM_PATH=.gem .gem/bin/mdl "$MD_FILES" However I still received the error and the only way I could get it to work was by replacing the above line with this . MD_FILES= So, as you can see, I am obviously making mistakes, but, I’m just not sure how to do it correctly, and I really don’t know how to research the commit process given that I don’t even understand the above code. Again my apologies. However, I did add an lpstat file to the commit :)
|
I agree with being pragmatic, but all in all still stand by my previous comment:
I think "giving the answer they need" is tricky because we don't know what people need. Some people might just want a refresher on how |
Otherwise, keen to merge this page as soon as we can. @Qtrain's put a lot of work into it and it's great to get new commands 👍 We can always adjust a few things later. |
@rprieto @waldyrious Thanks for the feedback and bearing with me on this mess (cringe). Please let me know what next steps need to be taken. I don't want to end up accidentally submitting yet another pull request. Thanks. |
@rprieto @waldyrious Hi guys, I would still like to get this committed if possible. I realize that I am behind the branch now, so, I was hoping one of you might be able to provide some direction. Please let me know. Thanks. |
Thank you very much for a valuable contribution! I had to make new commit instead of yours because the branches diverged too much :) I used your text, but changed the structure:
If you want you are welcome to submit further pull requests to improve these pages. Keep the good work! |
@igorshubovych No worries! Thanks very much for taking the reigns, I really appreciate your help! Cheers |
fixed and deleted line in shell script that was giving me problems. Let me know if you need changes. thx.