| Issue 527: | gerrit mangles pasted log input onto one line | |
| 21 people starred this issue and may be notified of changes. | Back to list |
Affected Version: What steps will reproduce the problem? 1. paste output from "adb logcat" into the "review" text area. 2. hit "Publish Comments". What is the expected output? What do you see instead? the log output should preserve its line breaks. in the mail that gerrit sends out, it does. but when gerrit shows this on the web, it's all mangled onto one line. Please provide any additional information below. see my 2010-04-07 11:13 comment on this bug: https://android-git.corp.google.com/g/47862 this has bitten me in the past, this is just the straw that made me file a bug. plus in this case, manual reformatting (even if i'd realized in advance) would have been impractical.
Apr 8, 2010
#1
sop@google.com
Status:
Accepted
Apr 8, 2010
my vote would be "never reflow"... this is 2010, not 1972, and this is a web app, not
vi/emacs. there's no reason for people to be manually inserting meaningless line
breaks (and if they do, preserving them shouldn't be harmful).
if you do want to consider the input as markup rather than "i repeat exactly what i
was given", how about code.google.com wiki syntax? then i'd have to put {{{ and }}}
around this, but the behavior would be consistent and predictable, and mildly useful
for inline code snippets too.
Oct 7, 2011
I second that, this is really annoying. The lack of markup is too, or rather its simplicity. I don't mind which markup is to be used, but please chose one that doesn't reflow, it's PAINFUL.
Oct 9, 2012
GitHub flavored Markdown (or some slight variation) would be easy to implement and is consistent with other tools. GFM also retains hard-wrapped paragraphs. http://github.github.com/github-flavored-markdown/
Jul 8, 2014
(No comment was entered for this change.)
Status:
Submitted
Labels: FixedIn-2.10
Jan 27, 2015
(No comment was entered for this change.)
Status:
Released
Jul 2, 2015
Issue 1031 has been merged into this issue. |
|
| ► Sign in to add a comment |