All of lore.kernel.org
 help / color / mirror / Atom feed
From: solsTiCe d'Hiver <solstice.dhiver@gmail.com>
To: Andrew Sayers <andrew-git@pileofstuff.org>
Cc: git <git@vger.kernel.org>
Subject: Re: [bash-completion] syntax error near unexpected token '<' on line 123 in bash_completion.d/git
Date: Mon, 26 Jul 2010 00:19:28 +0200	[thread overview]
Message-ID: <1280096368.7211.2.camel@soho.example.org> (raw)
In-Reply-To: <4C4C982C.20904@pileofstuff.org>

Le dimanche 25 juillet 2010 à 21:01 +0100, Andrew Sayers a écrit : 
> bash 4.1.5 always prepends "bash: "
> to such errors for me:
> 
> $ while false ; do echo foo ; done < ;
> bash: syntax error near unexpected token `;'
> 
bash 4.1.7 does that too here.

> If this is the complete error text, then I suspect you may have somehow
> got bash completion in a non-bash shell.
> 
the complete message is:
/etc/bash_completion.d/git: line 123: syntax error near unexpected token
'<'
/etc/bash_completion.d/git: line 123: done < <(git config -z
--get-regexp '^(svn-remote\..*\.url|bash > \.showupstream)$' 2>/dev/null
| tr '\0\n' '\n ')

> Could you add this on line 98 and let me know what it says:
> echo $BASH_VERSION $BASHOPTS

When I add the above command at line 98, it shows it is really bash
running:
4.1.7(2)-release
cmdhist:expand_aliases:extglob:extquote:force_fignore:interactive_comments:progcomp:promptvars:sourcepath 

  reply	other threads:[~2010-07-25 22:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-25 11:12 [bash-completion] syntax error near unexpected token '<' on line 123 in bash_completion.d/git solsTiCe d'Hiver
2010-07-25 11:49 ` Ævar Arnfjörð Bjarmason
2010-07-25 20:01 ` Andrew Sayers
2010-07-25 22:19   ` solsTiCe d'Hiver [this message]
2010-07-26 21:39     ` Andrew Sayers
2010-07-27  9:24       ` solsTiCe d'Hiver
2010-07-27 10:43       ` solsTiCe d'Hiver

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=1280096368.7211.2.camel@soho.example.org \
    --to=solstice.dhiver@gmail.com \
    --cc=andrew-git@pileofstuff.org \
    --cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.