-
Notifications
You must be signed in to change notification settings - Fork 867
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
colors #4
Comments
Colorizing code differently from text sounds good. Howdoi could have code be all blue, and text be black. Or it could even syntax highlight the code – either highlighting the code itself using Pygments or somehow copying Stack Overflow’s span tags and converting those to color codes. I oppose the idea of bolding keyword matches. Usually, what I have searched for is everywhere in the answer, and I don’t have any trouble finding where in the answer my query is discussed. This is what keyword bolding would look like for
The bolding doesn’t help me read the answer; it’s just distracting. That answer demonstrates another place where color might be useful: links. In the answer above, “Rails event calendar” is a link. The answer text would be more understandable if it were blue in the howdoi output while the surrounding text was black. (Of course, you still wouldn’t be able to click on the link in the command line, but at least you would know that you should follow the answer link for more information, using the |
Also of note, syntax highlighting! #20 |
Going to close this issue in light of #20. |
# This is the 1st commit message: move from print_err to logging # This is the commit message #2: change sanity check message # This is the commit message #3: flake8 linting # This is the commit message #4: flake8 linting # This is the commit message #5: pylint updates # This is the commit message #6: pylint updates # This is the commit message #7: pylint updates for errors.py # This is the commit message #8: update changes from #344 # This is the commit message #9: update formatting # This is the commit message #10: update formatting # This is the commit message #11: add consuructor to class # This is the commit message #12: refactor logging levels and messages # This is the commit message #13: refactor logging levels and messages # This is the commit message #14: pylint recomendations # This is the commit message #15: flake8 formating # This is the commit message #16: flake8 formating # This is the commit message #17: change logging to print
for readability, it might be nice to colorize the output that is code vs text. additionally, you could make keyword matches bold.
The text was updated successfully, but these errors were encountered: