git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: David Scurrah <D.Scurrah@bom.gov.au>
To: "avarab@gmail.com" <avarab@gmail.com>
Cc: "spearce@spearce.org" <spearce@spearce.org>,
	"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Patch for git-completion.bash [SEC=UNCLASSIFIED]
Date: Mon, 16 Aug 2010 15:45:21 +1000	[thread overview]
Message-ID: <0E3686EB9FA8AA409AFA0A25468DCE4301309C3DE86C@BOM-VMBX-HO.bom.gov.au> (raw)
In-Reply-To: <AANLkTi=QY+3M9jpuwXVcH1-yFhNQrjTfL9epTL-OYGMY@mail.gmail.com>

Thanks reading the list showed running as sh instead of bash was my problem

I am trying to combine the very useful git-prompt
(http://volnitsky.com/project/git-prompt/) and git-completion.bash
scripts as each had something the other lacked.

The problem is that while git-prompt suggests you start it from .bashrc
via 
[[ $- == *i* ]]   &&   . /path/to/git-prompt.sh

Using . to execute git-completion.bash runs sh which runs bash in sh
emulation mode which makes it fail in several places.

I did see a thread about an attempt to make the script zsh compliant as
well, I wonder if it would be better to just make it sh compliant so
that it is more portable, I guess that's too hard

regards

David Scurrah
> >
> > On Mon, 2010-08-16 at 04:14 +0000, Ævar Arnfjörð Bjarmason wrote:
> >> On Mon, Aug 16, 2010 at 04:09, David Scurrah <D.Scurrah@bom.gov.au> wrote:
> >> > Hi,
> >> >
> >> > On Mon, 2010-08-16 at 01:09 +0000, Ævar Arnfjörð Bjarmason wrote:
> >> >> On Mon, Aug 16, 2010 at 00:53, David Scurrah <D.Scurrah@bom.gov.au> wrote:
> >> >>
> >> >> Thanks for not sending a classified patch.
> >> >
> >> > Ha ha - the Australian Government has to have email classifications for
> >> > every email sent - classified I believe just means I do not wish you to
> >> > share it not that it is a state secret (see one implementation
> >> > http://www.janus.net.au/janusSEAL/Outlook/features)
> >> >
> >> >
> >> >> Have you seen the "[bash-completion] syntax error near unexpected
> >> >> token '<' on line 123 in bash_completion.d/git" thread recently on
> >> >> this list? It probably describes the problem you're having.
> >> >
> >> > I'll looked hard and can't find the thread you mentioned
> >> > and the current version on my Fedora system does not complete first
> >> > level commands like checkout ...
> >>
> >> http://comments.gmane.org/gmane.comp.version-control.git/151723
> >>
> >> > Maybe there is something I am missing.
> >>
> >> You're probably executing the completion file in bash's sh compatibility mode.



      parent reply	other threads:[~2010-08-16  5:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-16  0:53 Patch for git-completion.bash [SEC=UNCLASSIFIED] David Scurrah
2010-08-16  1:09 ` Ævar Arnfjörð Bjarmason
     [not found]   ` <0E3686EB9FA8AA409AFA0A25468DCE4301309C3DE869@BOM-VMBX-HO.bom.gov.au>
     [not found]     ` <AANLkTi=cKVeDNqP018ottyB0xW3xp1yosO1AY6CQbnUY@mail.gmail.com>
     [not found]       ` <0E3686EB9FA8AA409AFA0A25468DCE4301309C3DE86A@BOM-VMBX-HO.bom.gov.au>
     [not found]         ` <AANLkTi=QY+3M9jpuwXVcH1-yFhNQrjTfL9epTL-OYGMY@mail.gmail.com>
2010-08-16  5:45           ` David Scurrah [this message]

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=0E3686EB9FA8AA409AFA0A25468DCE4301309C3DE86C@BOM-VMBX-HO.bom.gov.au \
    --to=d.scurrah@bom.gov.au \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).