mirror of
https://github.com/benbusby/whoogle-search.git
synced 2026-04-25 12:15:50 +03:00
[GH-ISSUE #308] [BUG] <brief bug description> #215
Labels
No labels
Fixed (Pending PR Merge)
Stale
bug
enhancement
enhancement
good first issue
help wanted
keep-open
needs more info
pull-request
question
theme
unfortunate
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/whoogle-search#215
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @czadikem on GitHub (May 10, 2021).
Original GitHub issue: https://github.com/benbusby/whoogle-search/issues/308
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:
Deployment Method
runexecutableVersion of Whoogle Search
Additional context
So I have been messing with this for a couple of hours trying to get the latest version or the 0.4.0 version to work but Duckduckgo bangs don't work in either (I type then and click enter or search and nothing happens). Also the 0.4.1 version seems to have a weird error when i do a search it removes the last letter from my search. So right now I am using the 0.3.2 version and would like to have the css that the 0.4.0 and 0.4.1 has but can't because of these errors. Thanks for this great project. And making it easy to use and setup.
@benbusby commented on GitHub (May 10, 2021):
The issue with the last letter of the query being cut off has just been fixed with
05995649f3.Can you elaborate on the DDG bangs not working? There are tests in the CI build of the project that verify these are working, so it sounds like there may be an issue with how they're being used. If you search using a bang (i.e.
!w wikipedia) does that not work?Closing for now as I think this is a specific use case error, but I'm happy to continue the discussion and help wherever possible.