From: Ethan Grammatikidis <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] Surprise insertion of bind into namespace (anecdote)
Date: Fri, 13 Sep 2013 20:13:20 +0100 [thread overview]
Message-ID: <1379099600.27122.21697069.16B52850@webmail.messagingengine.com> (raw)
In-Reply-To: <1379070109.6031.21505573.042A6EE4@webmail.messagingengine.com>
On Fri, Sep 13, 2013, at 12:01 PM, Ethan Grammatikidis wrote:
> add "bind -bc $home $home" before line 4. Ns still shows the unrequested
> bind, it appears before the "bind -bc",
An unfortunate side effect of this work-around is wildcards in the shell
will give two copies of any matches. I've taken to using wildcards
instead of relying on completion, and this is proving rather intrusive.
I just added filename deduplication to my editor-launch script, which is
a little crazy.
next prev parent reply other threads:[~2013-09-13 19:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-13 11:01 Ethan Grammatikidis
2013-09-13 19:13 ` Ethan Grammatikidis [this message]
2013-09-13 19:17 ` [9front] " Ethan Grammatikidis
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=1379099600.27122.21697069.16B52850@webmail.messagingengine.com \
--to=eekee57@fastmail.fm \
--cc=9front@9front.org \
/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).