This repository has been archived by the owner on Apr 22, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 7.3k
nodejs debug doesn't show current line without color support #6150
Labels
Comments
ok, it does provide a line number:
So it does tell me that I'm on line 5. It would be preferred if line 5 were annotated in some fashion other than color, however. something like:
|
Sure, I'd be ok with a |
Debugger is always printing out 5 lines with active line in the middle, right? So it isn't really that bad. An issue with printing edit: nevermind, I see now how breakpoints are shown. I'll look into it. |
rlidwka
added a commit
to rlidwka/node
that referenced
this issue
Sep 28, 2013
bnoordhuis
pushed a commit
that referenced
this issue
Oct 1, 2013
Fixed by 028e652. |
tjfontaine
added a commit
that referenced
this issue
Oct 30, 2013
* uv: Upgrade to v0.11.14 * v8: upgrade 3.21.18.3 * assert: indicate if exception message is generated (Glen Mailer) * buffer: add buf.toArrayBuffer() API (Trevor Norris) * cluster: fix premature 'disconnect' event (Ben Noordhuis) * crypto: add SPKAC support (Jason Gerfen) * debugger: count space for line numbers correctly (Alex Kocharin) * debugger: make busy loops SIGUSR1-interruptible (Ben Noordhuis) * debugger: repeat last command (Alex Kocharin) * debugger: show current line, fix for #6150 (Alex Kocharin) * dgram: send() can accept strings (Trevor Norris) * dns: rename domain to hostname (Ben Noordhuis) * dns: set hostname property on error object (Ben Noordhuis) * dtrace, mdb_v8: support more string, frame types (Dave Pacheco) * http: add statusMessage (Patrik Stutz) * http: expose supported methods (Ben Noordhuis) * http: provide backpressure for pipeline flood (isaacs) * process: Add exitCode property (isaacs) * tls: socket.renegotiate(options, callback) (Fedor Indutny) * util: format as Error if instanceof Error (Rod Vagg)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Suppose I ssh into a box and run nodejs debugger on a script... if my ssh client doesn't support coloring, then I have no idea where the debugger is executing because it gives no indication of current location other than coloring.
The text was updated successfully, but these errors were encountered: