From: Kevin Carhart <kevin@carhart.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] showscripts() (fwd)
Date: Wed, 7 Feb 2018 21:21:26 -0800 (PST) [thread overview]
Message-ID: <alpine.LRH.2.03.1802072115290.23531@carhart.net> (raw)
I'm going back a few days to ask about showscripts(1). Hooray for the
recent explosion of functionality - feels like longer than a few days,
doesn't it?
> The resulting list is left in document.scripts2,
So the indexes need not correspond, but document.scripts2 is a superset
that includes all of document.scripts and more, correct? So it seems
like there would be no drawback to just always using scripts2 from
now on. I don't rely on those indices staying the same anyway, since
the website developers can move things around at any time.
thanks
Kevin
next reply other threads:[~2018-02-08 5:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-08 5:21 Kevin Carhart [this message]
2018-02-08 5:38 ` Karl Dahlke
2018-02-08 6:04 ` 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=alpine.LRH.2.03.1802072115290.23531@carhart.net \
--to=kevin@carhart.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).