-
Notifications
You must be signed in to change notification settings - Fork 74
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
no result #200
Comments
when I type "I want to call" in smokin, I get the error no result |
same, except literally nothing works |
Hi, this script is kind of abandoned, there were a number of other bugs before this broke it altogether. I have made a fork of this in rust that you can find here sorry about this, if you want to carry on using this script, changing line 886 from:
to:
might get it working again (you could also try different user agents, that is the root of the problem) |
i did, but I'm still getting the same error |
aight i'll just try them i guess |
i finally did it, thank you, it was like you said, it comes when I restart the computer |
Rip that this project got abandoned |
@PureArtistry your fix did the trick for me, was not outputting any results before that change. Most functionalities seem to be working but items that you'd expect a list are not working. Examples queries like:
Outputs the definitions of "Iron Man" and "NYC", respectively. Also language queries, like I'll make a PR with your change so those who attempt to download this command at least get some functionalities to work. |
@PureArtistry Any chance you could archive this repo (possibly after @ej-sanmartin's fix is merged)? Seems like a good idea at this point to avoid frustrating new users... |
Easy Fix: replace in the shell tuxi script the (unique) call to "curl" with any of the binaries provided at https://github.com/lwthiker/curl-impersonate In particular I have used "curl_chrome99" and now it works. |
shell
Operating system/version
:Terminal name/version
:Location
:$TERM
Steps to Reproduce the Problem
Expected Behavior
Actual Behavior
Log
The text was updated successfully, but these errors were encountered: