From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] jdb redirect
Date: Sun, 17 Sep 2017 05:21:28 -0400 [thread overview]
Message-ID: <20170817052128.eklhad@comcast.net> (raw)
Anticipating the work that Kevin is doing, it occurs to me that we want a way to dump long output into a file.
This will typically be document.scripts[7].data
the deminimized version of javascript, which could easily be 100K.
Use tab to dump it into a file.
expression tab file
Then edit the file and go to the offending line number.
I didn't want to use > cause that's a valid js operator, but I still hit > almost by force of habit.
tab is truly unused, and it's a single character, but I realized, after I pushed,
that this can be trouble for those of you who use readline.
It might try to do tab completion or some such.
I could perhaps disable readline mode when running in jdb mode,
or maybe there is a better character than tab.
Any thoughts?
Karl Dahlke
next reply other threads:[~2017-09-17 9:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 9:21 Karl Dahlke [this message]
2017-09-17 11:22 ` Chris Brannon
2017-09-17 11:33 ` Karl Dahlke
2017-09-17 23:56 ` Kevin Carhart
2017-09-18 9:52 ` Kevin Carhart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170817052128.eklhad@comcast.net \
--to=eklhad@comcast.net \
--cc=Edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).