From: Chris Brannon <chris@the-brannons.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] jdb redirect
Date: Sun, 17 Sep 2017 04:22:54 -0700 [thread overview]
Message-ID: <877ewxwovl.fsf@prgmr.com> (raw)
In-Reply-To: <20170817052128.eklhad@comcast.net> (Karl Dahlke's message of "Sun, 17 Sep 2017 05:21:28 -0400")
Karl Dahlke <eklhad@comcast.net> writes:
> 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's also not distinct in some speech adapters. Why not
> file EXPRESSION
That would only allow filenames without whitespace; no great loss.
It would be as easy to parse, if a little unintuitive.
-- Chris
next prev parent reply other threads:[~2017-09-17 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-17 9:21 Karl Dahlke
2017-09-17 11:22 ` Chris Brannon [this message]
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=877ewxwovl.fsf@prgmr.com \
--to=chris@the-brannons.com \
--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).