I didn't, but I read the script and understand what it does. For me, the kind of things they do are better served by custom search engine shortcuts in modern browsers, e.g., `w` for a direct `http://en.wikipedia.org/w/index.php?title=Special:Search&search=%s` Wikipedia search which most of the time brings me right to the entry, with no intermediate state, sort of like lucky, but with the benefit of browser suggestions. Of course, that's not in the command line, but I use what is most productive for me given the circumstances.
By the way, your case is strange because according to [docs](https://docs.python.org/3/library/sys.html#sys.stdout)
> The character encoding is platform-dependent. Under Windows, if the stream is interactive (that is, if its isatty() method returns True), the console codepage is used, otherwise the ANSI code page. Under other platforms, the locale encoding is used (see locale.getpreferredencoding()).
If you followed my advice of `chcp 65001` then your output encoding should be `cp65001` (that is, Windows UTF-8, or `CP_UTF8`). So either
- You didn't `chcp 65001` (but you said you did...) or somehow it didn't take effect; IIRC you can check the code page in PowerShell's preference pane. Or
- The docs are inaccurate. In that case... Well, I'm not interested enough to read the Windows branches of CPython source code.
Not sure why you deleted your comment and closed the issue, but since you got
```python-traceback
File "googler.py", line 757, in
results = fetch_results()
File "googler.py", line 741, in fetch_results
r.print_entry()
File "googler.py", line 341, in print_entry
print(w, end=' ')
File "C:\Users\lhais\AppData\Local\Programs\Python\Python35-32\lib\encodings\cp850.py", line 19, in encode
return codecs.charmap_encode(input,self.errors,encoding_map)[0]
UnicodeEncodeError: 'charmap' codec can't encode character '\u2022' in position 0: character maps to
```
apparently your output encoding is `cp850` Western Europe. Setting `PYTHONIOENCODING` to `utf-8` should probably fix it.
I'm already checking this in #152, but I excluded Windows in that PR because I simply don't know enough about Windows to make sure I don't screw up and totally bust it for Windows users.
Please follow the issue template and provide additional information, which is vital for troubleshooting:
---
Before opening an issue, please try to reproduce on [the latest development version](https://github.com/jarun/googler#installing-from-this-repository) first. The bug you noticed might have already been fixed.
If the issue can be reproduced on master, then please make sure you provide the following:
- Output of `googler -d`;
- Link to the response body (you should see a line like `[DEBUG] Response body written to '/Volumes/ramdisk/googler-response-xxxxxxxx'` in the output of `googler -d`; please upload the file to a [gist](https://gist.github.com/) and include the gist's URL in the issue);
- Details of operating system, Python version used, terminal emulator and shell;
- `locale` output, if relevant. It's a good idea to set your locale to UFT-8. Please refer to [Buku #30](https://github.com/jarun/Buku/issues/30).
@lhaisrs Anyway, if you need additional help, please open a new issue (and follow the instructions in the template). This thread is hardly related to running googler on Windows.
@lhaisrs When I have to use Windows I use [ConEmu](https://conemu.github.io/) which supports ANSI colors. See #70 (where I made googler Windows-compatible) for screenshot.
Adding environment variables in Windows (either globally or in shell profiles) is easy. Google is your friend.