From: chris@the-brannons.com
To: edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] we shouldn't be letting glob() do our tilde expansion
Date: Thu, 14 May 2015 08:45:53 -0700 [thread overview]
Message-ID: <877fsbp3gu.fsf@mushroom.localdomain> (raw)
Two reasons, one can probably be surmounted, the other probably cannot.
1. musl, the libc implementation that I use for building the static
executables, lacks GLOB_TILDE_CHECK (and GLOB_TILDE for that matter).
I don't think they're in POSIX.
2. The insurmountable one is that it creates a big inconsistency in the
behavior of commands with respect to filename expansion. Look at the
following typescript to see why.
Script started on Thu 14 May 2015 08:31:42 AM PDT
[chris@mushroom ~]$ edbrowse
do not send referrer
edbrowse ready
$a
hello
.
w ~/foo
cannot create ~/foo
w /home/chris/foo
6
1c
goodbye
.
w ~/foo
8
q
[chris@mushroom ~]$ exit
exit
Script done on Thu 14 May 2015 08:32:26 AM PDT
I'd be happy to submit a patch for review to rework envFile, so that it
does its own ~ and ~username expansion.
Sorry I didn't catch this earlier.
-- Chris
next reply other threads:[~2015-05-14 15:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 15:45 chris [this message]
2015-05-14 19:15 ` Karl Dahlke
2015-05-15 15:42 ` Karl Dahlke
2015-05-16 7:54 ` chris
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=877fsbp3gu.fsf@mushroom.localdomain \
--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).