Skip to content
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

Closed
matthandlersux opened this issue Nov 27, 2012 · 3 comments
Closed

colors #4

matthandlersux opened this issue Nov 27, 2012 · 3 comments

Comments

@matthandlersux
Copy link

for readability, it might be nice to colorize the output that is code vs text. additionally, you could make keyword matches bold.

@roryokane
Copy link

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 howdoi calendar rails (the first query I found whose answer is text and not code):

I have doing some sort of similar project with Rails event calendar. As my knowledge there are no specific GEM or plug-in for your requirement.But you can customize the event calendar. So you need to add that by manually.

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 -l flag.)

@anthonypt87
Copy link
Contributor

Also of note, syntax highlighting! #20

@gleitz
Copy link
Owner

gleitz commented Jan 31, 2013

Going to close this issue in light of #20.

@gleitz gleitz closed this as completed Jan 31, 2013
gleitz pushed a commit that referenced this issue Jun 26, 2020
gleitz pushed a commit that referenced this issue Apr 14, 2021
# 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants