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

docu issue multiply(#ff6600, #0000ff); #1649

Closed
soliton4 opened this issue Nov 9, 2013 · 5 comments
Closed

docu issue multiply(#ff6600, #0000ff); #1649

soliton4 opened this issue Nov 9, 2013 · 5 comments

Comments

@soliton4
Copy link

soliton4 commented Nov 9, 2013

the result is obv. not #ff6600. this is a typo and a pretty confusing one.

@Synchro
Copy link
Member

Synchro commented Dec 17, 2013

Moving this issue to docs. When you know what the output is supposed to be, please can you say what it is in case the person reading your report doesn't know. "obv. not" is not helpful; it would have taken less typing to provide the correct output.

@Synchro Synchro closed this as completed Dec 17, 2013
@Soviut
Copy link

Soviut commented Dec 18, 2013

Agreed. The way to report an issue is to show what you tried, show what you expected, show what you got instead.

@soliton4
Copy link
Author

are you guys kidding me?
the result is #000000

how are you supposed to write a doc if you cant see that and rather discuss about proper bug reporting?

@Synchro
Copy link
Member

Synchro commented Dec 18, 2013

There's nothing wrong with my ability to write docs, and I could indeed see exactly what the answer should have been as soon as I looked at it, no thanks to your bug report. If your'e going to help, be helpful. We're "discuss about proper bug reporting" because you apparently need some guidance in that area.

@Soviut
Copy link

Soviut commented Dec 19, 2013

Saying "shit's broken" doesn't help anyone. The people contributing, documenting and providing help here are doing it in their free time. You doing a minimum of proper reporting results in less of their time taken to reproduce your issue and far greater likelihood they'll look at your issue sooner, rather than later.

For example, the solution might have been as simple as updating to a different version but you didn't even mention what version of LESS you were using.

This issue was closed.
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

3 participants