Closed hornjbl closed 3 years ago
Can you wrap the comments to keep it within 80 columns?
For example, not this:
# Imagine this is a really long line which far exceeds 80 columns.
But instead this:
# Imagine this is a really long
# line which far exceeds 80
# columns.
But of course, 80 columns, not whatever I wrapped to there. :P
Will do ;-)
Nailed it!
Nailed it!
Apologies, I saw afterward that the 80 col limit is clearly mentioned in the docs. Should have paid more attention...
It's okay. It was a fairly recent addition, AFAIK. I wrote the LenChk tester, which you can use if you want to test line length before sending a PR. Refer to its --help
or -h
output if you need usage information.
Please test; it should be available at cheat.sh/lse
now.
Maybe it should be lse.sh
and not lse
, or other way around?
Your command must be lse
and not lse.sh
?
Thanks @chubin, tested and it's working.
Ah, agree, the command is lse.sh, so if you prefer the file to be named with the name and extension, I'm happy to update.
Being new to github and collaborating on someone else's repo, do I just rename the file in my local repo, push to remote, and create a new pull request? Will it handle the rename accordingly and not just see it as a new file?
Yes, you can do it just as any other repository change. I already did it for you. It must be available under the new name now
I've added a script that I often need to refer to my own notes for :
This is the linux-smart-enumeration, or lse script, based on enum4linux.