git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Philemon GIRAUD <philemon.giraud@metrologic.group>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Git bug report CDPATH completion
Date: Mon, 11 Mar 2024 21:35:56 +0000	[thread overview]
Message-ID: <Ze95PCbwn9IE99Kb@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <AM6PR10MB28087CFD43779194563F558492242@AM6PR10MB2808.EURPRD10.PROD.OUTLOOK.COM>

[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]

On 2024-03-11 at 14:24:24, Philemon GIRAUD wrote:
> Thank you for filling out a Git bug report!
> Please answer the following questions to help us understand your issue.

Hey,

> What did you do before the bug happened? (Steps to reproduce your issue)
> This bug is about the "git bash" that comes with git for windows
> I added "export CDPATH=.:/c/some/path" to my .bashrc
> 
> What did you expect to happen? (Expected behavior)
> Given that the folder "/c/some/path/myfolder" exists,
> I expected to type (from any directory) "cd myf<TAB>" add that the autocomplete would complete to "cd myfolder"

This mailing list is for the Git project, which deals only with source
distributions of Git and doesn't distribute any associated software
(outside of contrib), such as bash.  You're reporting a problem with Git
for Windows, which should be reported to
https://github.com/git-for-windows/git/issues/.  Do be sure to search
first in case this has already been reported.
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]

      parent reply	other threads:[~2024-03-11 21:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-11 14:24 Git bug report CDPATH completion Philemon GIRAUD
2024-03-11 18:13 ` Junio C Hamano
2024-03-11 21:35 ` brian m. carlson [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

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

  git send-email \
    --in-reply-to=Ze95PCbwn9IE99Kb@tapette.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=philemon.giraud@metrologic.group \
    /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).