From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] console.log
Date: Wed, 01 Feb 2017 15:18:40 -0500 [thread overview]
Message-ID: <20170101151840.eklhad@comcast.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 519 bytes --]
As more js starts to work, we get more console.log() messages. Example cartercenter.org. These just print, but could be annoying / unnecessary for the average user. What should we do?
Direct them to a file in the user's temp directory?
Direct them somewhere as per the user's config file?
Print them only at debug level 2 or higher?
I would opt for the latter - just not sure if it should be level 2 or 3.
This way they would be in the debug stream, if you were trying to figure something out.
Karl Dahlke
next reply other threads:[~2017-02-01 20:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 20:18 Karl Dahlke [this message]
2017-02-01 23:04 ` Kevin Carhart
2017-02-21 18:34 ` [Edbrowse-dev] the cache and other pushes are very exciting 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=20170101151840.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).