From: Jeff King <peff@peff.net>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Patrick Higgins <patrick133t@yahoo.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: wishlist: git gui not listing untracked files in unstaged list
Date: Wed, 10 Mar 2010 17:32:10 -0500 [thread overview]
Message-ID: <20100310223210.GC4223@sigill.intra.peff.net> (raw)
In-Reply-To: <20100310221403.GF21994@spearce.org>
On Wed, Mar 10, 2010 at 02:14:03PM -0800, Shawn O. Pearce wrote:
> Jeff King <peff@peff.net> wrote:
> > This is an inconsistency in the way that tilde-expansion is handled. The
> > core.excludesfile config variable is expanded internally with the
> > "pathname" magic (git_config_pathname). But handing the filename
> > directly to ls-files --exclude-from does not do that expansion.
> >
> > So either there is a bug in ls-files, which should expand from the
> > command line, or one in git-gui, which should be using "git config
> > --path core.excludesfile" to get the path.
>
> I'd say its git-gui, yes? Doesn't my shell automatically do
> --exclude-from=~/my.list for me? Its not the command's job
> to do that expansion.
It depends on the shell. Bash will expand it in _some_ cases (but not
this one). Dash never will:
$ echo $BASH_VERSION
4.1.0(1)-release
$ echo foo=~/foo ;# expands
foo=/home/peff/foo
$ echo --foo=~/foo ;# does not
--foo=~/foo
$ dash -c 'echo foo=~/foo' ;# does not
foo=~/foo
That being said, my gut feeling is for git-gui to fix it, too. Shell
callers can use $HOME if they want.
-Peff
next prev parent reply other threads:[~2010-03-10 22:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-10 19:43 wishlist: git gui not listing untracked files in unstaged list MALAISE Pascal
2010-03-10 19:59 ` Junio C Hamano
2010-03-10 20:07 ` Shawn O. Pearce
2010-03-10 20:57 ` MALAISE Pascal
2010-03-10 22:00 ` Patrick Higgins
2010-03-10 22:12 ` Jeff King
2010-03-10 22:14 ` Shawn O. Pearce
2010-03-10 22:30 ` Junio C Hamano
2010-03-10 22:32 ` Jeff King [this message]
2010-03-10 22:36 ` Jeff King
2010-03-11 7:08 ` Johannes Sixt
2010-03-11 7:11 ` Jeff King
2010-03-11 12:52 ` Andreas Schwab
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=20100310223210.GC4223@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=patrick133t@yahoo.com \
--cc=spearce@spearce.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).