RESOLVED FIXED115987
think about how auto-NLs in console can be improved 
https://bugs.webkit.org/show_bug.cgi?id=115987
Summary think about how auto-NLs in console can be improved
Paul Miller
Reported 2013-05-12 10:45:56 PDT
Been trying to use webkit.app as main browser, my main concern is new auto-creation of newlines instead of executing the statement. When it indeed allows to improve readability, it’s often that devs write some boilerplate code like `list.filter(function() {})` and then write code inside function and press enter. With current implementation, I need to press additionally ⌘→ to move to the end of current string and execute the command. Any ideas on how can this be improved? I write a lot of code in inspector every day and this can be annoying (maybe I ain’t used to it yet tho)
Attachments
Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2013-05-12 10:46:14 PDT
<rdar://problem/13870951>
Timothy Hatcher
Comment 2 2013-05-12 10:56:55 PDT
Command-Return always executes. Does that work for you?
Paul Miller
Comment 3 2013-05-12 19:04:31 PDT
I guess no as it will also trigger auto-complete (it does currently). Otherwise, yep, probably. Still more annoying than before, but anyway. In some cases, like strings ('<enter>') the syntax is also invalid.
Timothy Hatcher
Comment 4 2013-05-13 06:46:22 PDT
(In reply to comment #3) > I guess no as it will also trigger auto-complete (it does currently). Otherwise, yep, probably. Still more annoying than before, but anyway. > > In some cases, like strings ('<enter>') the syntax is also invalid. It triggering autocomplete is a bug I will fix. Thanks! You make a good point that enter in the middle of some expressions is not desired and would result in a syntax error. That would be a good improvement. Right now we always insert a newline if the cursor is not at the end of the prompt.
Timothy Hatcher
Comment 5 2013-06-14 07:34:40 PDT
Was fixed 5/14/13 5:12 PM
Note You need to log in before you can comment on or make changes to this bug.