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
list allows usage of -l
w/o -s
while get doesn't
#4
Comments
On the other side, > papeer get -l2 https://blog.lapw.at
cannot use limit option if depth/selector is not specified In your case, where you want the selector to be automatically determined, you may use a the
https://github.com/lapwat/papeer#depth-option Hope it helps |
However, it could be a nice feature to add. When you specify a limit option, it is also implicit that you want to look for one level down. |
I took the opportunity to add the feature you requested in this issue in release Now both commands should be accepted and have the same behavior: papeer get -d1 -l2 https://blog.lapw.at
papeer get -l2 https://blog.lapw.at |
Wow, now I understand both the original issue better and it's already fixed! I'm more than grateful, what a wonderful tool! |
The
list
command implicitly allows using no selector and uses the default of""
. Get doesn't work when only passing-l
, nor does it work with passing-s ""
. In my case the "default" selector thatget
uses works quite well, but simply spits out a few chapters at the end that I intend to omit. Usingpapeer list -l 5 <uri>
does that, however I cannot do the same withpapeer get -l 5 <uri>
.I think ideally it should be allowed to use
-l
and others with a default selector.The text was updated successfully, but these errors were encountered: