public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: Git shows nothing in cmd.exe
Date: Tue, 10 Nov 2020 09:13:06 -0700	[thread overview]
Message-ID: <09a3fd0d-81ba-11c0-1e85-b3578f39e9f6@SystematicSw.ab.ca> (raw)
In-Reply-To: <ac62ed9c07a94ee784d47bb38041a5a8@BELBRU-EXMP101.eeas.europa.eu>

On 2020-11-10 06:35, KAVALAGIOS Panagiotis (EEAS-EXT) wrote:
>> From: Cygwin <cygwin-bounces@cygwin.com> On Behalf Of Adam
>> Dinwoodie
>> Sent: 10 November 2020 13:57
>> Subject: Re: Git shows nothing in cmd.exe
>>
>> Thoughts below partly for my own reference, and partly in case anyone else
>> – including but not limited to Panos! – manages to take things further before
>> I do.
>>
>> I can't see anything obviously wrong here. There's two key oddities that
>> might be causing problems, though:
>>
>> - Cygwin is installed in `C:\Program Files\Cygwin`; that _should_ work, but it's
>> atypical, and spaces in filenames are a common source of problems.
>>
>> - This is a relatively old installation; I've not checked anything else, but Cygwin
>> Git v2.21.0-1 was released in May 2019 and there have been a bunch of
>> updates since then. I can't remember anything with these symptoms from
>> that time, however.
>>
>> I'm also curious about the Git configuration here, as I can see a bunch of ways
>> that could cause problems. I don't have the Cygwin bin directory in my path
>> to test this immediately, but for example `git branch -a` will try to call a pager
>> – `less` by default` – so I could imagine there being a PATH problem or similar
>> that's resulting in a duff pager call that's eating the output.
> 
> Adam, thank you very much! You found our issue. It is the "less" command from GnuWin32 that caused the problem:
> 
> C:\>where less
> C:\Program Files (x86)\GnuWin32\bin\less.exe
> C:\Program Files\Cygwin\bin\less.exe
> 
> C:\>rename "C:\Program Files (x86)\GnuWin32\bin\less.exe" less-OLD.exe
> 
> C:\>cd dev\Projects\TSSO_WKS\tsso-workstation-configuration
> 
> C:\DEV\Projects\TSSO_WKS\tsso-workstation-configuration>git branch -a
> * master
>   remotes/origin/master
> 
> It now displays correctly the branches.

Gnuwin32 *latest* package updates seem to be 10 years ago, some nearly 20.
Suggest deleting those and using current *mingw64*/msys Windows tools instead as
they are maintained with recent security fixes.
You should also be careful with PATHs using different toolchains: switch them
completely, or layer them carefully, to avoid these issues.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]

  reply	other threads:[~2020-11-10 16:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-10 10:35 KAVALAGIOS Panagiotis (EEAS-EXT)
2020-11-10 12:03 ` Adam Dinwoodie
     [not found]   ` <72f4f32d00e44071afbaa74b6b77ebad@BELBRU-EXMP101.eeas.europa.eu>
2020-11-10 12:56     ` Adam Dinwoodie
2020-11-10 13:35       ` KAVALAGIOS Panagiotis (EEAS-EXT)
2020-11-10 16:13         ` Brian Inglis [this message]
2020-11-11  9:28           ` KAVALAGIOS Panagiotis (EEAS-EXT)
2020-11-11 10:43             ` Andrey Repin

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=09a3fd0d-81ba-11c0-1e85-b3578f39e9f6@SystematicSw.ab.ca \
    --to=brian.inglis@systematicsw.ab.ca \
    --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).