-
Notifications
You must be signed in to change notification settings - Fork 219
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
Make stderr output more copy-friendly #840
Comments
I did try to help with that case but was requested to stop. |
This can be done by the user by using "Paste and Match Style" or the equivalent browser / OS options. |
I agree that this is a case of "the browser and GH being too smart by half", but I'm seeing the effects it's having on our tickets. Sadly any solution that relies on users being proactive will never have perfect compliance.
That seems to be related but not quite the same thing I was thinking of when I opened this. People that file issues will link to the playground and manually copy paste things. To be honest, I haven't seen the spammy tickets originated in the playground :) |
I was curious to see some examples of this problem and searched the Rust issues list: A small handful: rust-lang/rust#101972 Interestingly, even though the filename/line combos (e.g. |
When copying the stderr output from the compiler, it seems the clipboard now contains markdown for the link around error codes in the main message (or maybe it's HTML and pasting in GH turns it into markdown). This is causing unnecessarily verbose output in reports. I believe that in most cases people desire just the textual representation of errors, the link structure being either redundant or unnecessary. I would love it if we could capture the on copy event and only push the bare textual output to the clipboard.
The text was updated successfully, but these errors were encountered: