Marc Khouzam c6929ff239 completion: handle path completion and colon for tcsh script
Recent enhancements to git-completion.bash provide intelligent path
completion for git commands.  Such completions do not provide the
'/' at the end of directories for recent versions of bash; instead,
bash itself will add the trailing slash to directories to the result
provided by git-completion.bash.  However, the completion for tcsh
uses the result of the bash completion script directly, so it either
needs to add the necessary slash itself, or needs to ask the bash
script to keep the trailing slash.

Adding the slash itself is difficult because we have to check the
each path in the output of the bash script to see if it is meant to
be a directory or something else.  For example, assuming there is a
directory named 'commit' in the current directory, then, when
completing

  git add commit<tab>

we would need to add a slash, but for

  git help commit<tab>

we should not.

Figuring out such differences would require adding much intelligence
to the tcsh completion script.  Instead, it is simpler to ask the
bash script to keep the trailing slash.  This patch does this.

Also, tcsh does not handle the colon as a completion separator so we
remove it from the list of separators.

Signed-off-by: Marc Khouzam <marc.khouzam@ericsson.com>
2013-02-03 18:59:34 -08:00
2012-12-13 11:13:56 -08:00
2012-12-11 15:51:14 -08:00
2012-12-15 11:19:02 -08:00
2012-10-25 06:42:02 -04:00
2012-09-03 16:24:23 -07:00
2011-03-17 15:30:49 -07:00
2012-10-25 06:42:02 -04:00
2012-10-25 06:42:02 -04:00
2012-11-09 12:42:25 -05:00
2012-10-29 03:08:30 -04:00
2012-10-29 03:08:30 -04:00
2011-10-21 16:04:32 -07:00
2012-10-29 03:08:30 -04:00
2012-03-07 12:12:59 -08:00
2012-08-15 11:01:55 -07:00
2012-10-29 03:08:30 -04:00
2010-05-07 09:34:27 -07:00
2012-11-09 12:42:25 -05:00
2012-09-11 11:36:05 -07:00
2012-09-07 11:09:04 -07:00
2012-08-21 15:27:15 -07:00
2012-08-23 21:30:51 -07:00
2012-12-15 11:19:02 -08:00
2012-10-29 03:08:30 -04:00
2012-04-06 10:15:11 -07:00
2012-07-25 11:08:59 -07:00
2012-05-03 15:13:31 -07:00
2011-12-19 16:06:41 -08:00
2012-09-11 11:36:05 -07:00
2011-08-20 22:33:57 -07:00
2011-05-19 18:23:17 -07:00
2012-01-06 12:44:07 -08:00
2010-04-01 23:58:30 -07:00
2012-09-11 11:23:54 -07:00
2012-10-17 22:42:40 -07:00
2011-11-06 20:31:28 -08:00
2011-12-16 22:33:40 -08:00
2012-10-29 03:08:30 -04:00
2012-08-03 12:11:07 -07:00
2011-12-12 16:09:38 -08:00
2011-11-07 22:12:19 -08:00
2012-04-10 15:55:55 -07:00
2012-11-28 13:40:02 -08:00
2012-09-18 14:37:46 -07:00
2012-09-10 15:31:06 -07:00
2012-07-22 12:55:07 -07:00
2012-11-04 06:46:55 -05:00
2011-03-22 10:16:54 -07:00
2011-12-11 23:16:25 -08:00
2011-10-17 21:37:15 -07:00
2012-09-16 21:54:47 -07:00

////////////////////////////////////////////////////////////////

	GIT - the stupid content tracker

////////////////////////////////////////////////////////////////

"git" can mean anything, depending on your mood.

 - random three-letter combination that is pronounceable, and not
   actually used by any common UNIX command.  The fact that it is a
   mispronunciation of "get" may or may not be relevant.
 - stupid. contemptible and despicable. simple. Take your pick from the
   dictionary of slang.
 - "global information tracker": you're in a good mood, and it actually
   works for you. Angels sing, and a light suddenly fills the room.
 - "goddamn idiotic truckload of sh*t": when it breaks

Git is a fast, scalable, distributed revision control system with an
unusually rich command set that provides both high-level operations
and full access to internals.

Git is an Open Source project covered by the GNU General Public License.
It was originally written by Linus Torvalds with help of a group of
hackers around the net. It is currently maintained by Junio C Hamano.

Please read the file INSTALL for installation instructions.

See Documentation/gittutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands, and
Documentation/git-commandname.txt for documentation of each command.
If git has been correctly installed, then the tutorial can also be
read with "man gittutorial" or "git help tutorial", and the
documentation of each command with "man git-commandname" or "git help
commandname".

CVS users may also want to read Documentation/gitcvs-migration.txt
("man gitcvs-migration" or "git help cvs-migration" if git is
installed).

Many Git online resources are accessible from http://git-scm.com/
including full documentation and Git related tools.

The user discussion and development of Git take place on the Git
mailing list -- everyone is welcome to post bug reports, feature
requests, comments and patches to git@vger.kernel.org (read
Documentation/SubmittingPatches for instructions on patch submission).
To subscribe to the list, send an email with just "subscribe git" in
the body to majordomo@vger.kernel.org. The mailing list archives are
available at http://marc.theaimsgroup.com/?l=git and other archival
sites.

The messages titled "A note from the maintainer", "What's in
git.git (stable)" and "What's cooking in git.git (topics)" and
the discussion following them on the mailing list give a good
reference for project status, development direction and
remaining tasks.
Description
No description provided
Readme 279 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%