All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Pavlic <ted@tedpavlic.com>
To: "Boyd Stephen Smith Jr." <bss@iguanasuicide.net>
Cc: Junio C Hamano <gitster@pobox.com>,
	"Shawn O. Pearce" <spearce@spearce.org>,
	git <git@vger.kernel.org>
Subject: Re: [PATCH] Simple update to bash completions to prevent unbound variable errors.
Date: Mon, 12 Jan 2009 23:34:40 -0500	[thread overview]
Message-ID: <496C19E0.6060308@tedpavlic.com> (raw)
In-Reply-To: <200901122157.03658.bss@iguanasuicide.net>

> While I dislike emacs and use vim pretty much exclusively, I don't really see
> the need for a vim modeline.  On top of that, fdm=marker is a bit silly since
> there aren't any markers.  ff=unix and ft=sh are redundant, as any vim should
> detect these properly, given the filename.

Without the modeline, the vim I was using didn't set ft=sh. It seemed 
like the original authors were careful to use tabs everywhere, which was 
the major reason I used the modeline. I added the fdm=marker just in 
case someone would want to clean up the code someday and do some folding.

> So, I'm slightly negative on the modeline hunk.

It was just a suggestion.

>> 	local one=${1-} two=${2-} cur=${3-} four=${4-}
>
> Even better to use variable names that match the usage, if possible.

I don't know much about bash completion. It would be nice if the 
original authors could add some semantics, as I was just trying to come 
up with scripts that would actually work with set -u.

--Ted

-- 
Ted Pavlic <ted@tedpavlic.com>

   Please visit my ALS association page:
         http://web.alsa.org/goto/tedpavlic
   My family appreciates your support in the fight to defeat ALS.

  reply	other threads:[~2009-01-13  4:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-13  2:44 [PATCH] Simple update to bash completions to prevent unbound variable errors Ted Pavlic
2009-01-13  3:14 ` Junio C Hamano
2009-01-13  3:56   ` Boyd Stephen Smith Jr.
2009-01-13  4:34     ` Ted Pavlic [this message]
2009-01-13  4:50       ` Ted Pavlic
2009-01-13  6:35         ` Teemu Likonen
2009-01-13  8:01         ` Junio C Hamano
2009-01-13  4:30   ` Ted Pavlic
2009-01-13  5:37     ` Junio C Hamano

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=496C19E0.6060308@tedpavlic.com \
    --to=ted@tedpavlic.com \
    --cc=bss@iguanasuicide.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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 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.