public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: David Karr <davidmichaelkarr@gmail.com>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Trying to figure out what is wrong in a colleague's Cygwin setup
Date: Thu, 15 Jun 2023 14:07:16 -0700	[thread overview]
Message-ID: <CAA5t8Vob5aVkJGkvFhHEkW79LUJ=WaSJQY8TmB_G5txiHxLz+g@mail.gmail.com> (raw)
In-Reply-To: <CAA5t8VpyM-pXfw4vjyTTb3Pa6HthHK+K6K3wO_OqX-TeqwOyjA@mail.gmail.com>

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

(I replied with this earlier directly to someone who I didn't realize had
only replied to me.)

I do have a couple other clues that I've noticed while continuing to debug
this.

This person also has "git bash" installed, which is certainly similar to
Cygwin, but not quite the same.  In his gitbash shell, he does not get this
error.

If it matters, here is the "uname -a" output (hostname elided):

    CYGWIN_NT-10.0-22000 ... 3.4.6-1.x86_64 2023-02-14 13:23 UTC x86_64
Cygwin

If it matters, here is the same from his gitbash shell:

    MINGW64_NT-10.0-22000 ... 3.1.7-340.x86_64 2021-03-26 22:17 UTC x86_64
Msys

He is running Windows 11 (as I am).

What else can I try to narrow this down?

On Tue, Jun 13, 2023 at 2:54 PM David Karr <davidmichaelkarr@gmail.com>
wrote:

> I have been using Cygwin for many years, although I wouldn't call myself
> an advanced user.
>
> I'm working with some much newer users.  They set up Cygwin, but I didn't
> see them do it. I ran "uname -a" and it was about the same as mine.  I
> compared the output of "env|sort" and I saw some differences, but I can't
> tell if they were significant.
>
> When I run the following command:
>
>     kubectl config use-context dev2ff
>
> It works perfectly fine, setting the correct context.  When this user I'm
> working with runs the same command, he gets this (replacing his userid with
> "..."):
>
>     error: FindFirstFile C:\cygwin64\home\.../.kube/config: The directory
> name is invalid.
>
> He did have "HOME=/c/Users/...", but I had him change it to "/home/...",
> but that didn't make any difference.
>
> I'm not sure what could be happening here.
>

  reply	other threads:[~2023-06-15 21:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-13 21:54 David Karr
2023-06-15 21:07 ` David Karr [this message]
2023-06-16 19:02   ` David Karr
2023-06-16 19:17     ` Mike Gran
2023-06-16 20:54       ` David Karr

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='CAA5t8Vob5aVkJGkvFhHEkW79LUJ=WaSJQY8TmB_G5txiHxLz+g@mail.gmail.com' \
    --to=davidmichaelkarr@gmail.com \
    --cc=cygwin@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).