From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Uncomment
Date: Mon, 12 Feb 2018 06:18:19 -0500 [thread overview]
Message-ID: <20180112061819.eklhad@comcast.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 607 bytes --]
I addded an uncomment routine to the end of startwindow.js.
It wasn't hard to write, and is valid for either js or css, as they have the same kinds of comments and strings.
Have a look if you wish.
I'm just prepping myself; I have the feeling we will need to roll our own querySelectorAll and/or css parse.
They both currently have too many bugs and inefficiencies.
The uncomment routine says it might grow as n^2, so maybe I can't use this lazy implementation,
but then again, the css file from stackoverflow is a third of a meg, and it uncomments just like that, so maybe it's fine.
Karl Dahlke
reply other threads:[~2018-02-12 11:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180112061819.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).