DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 12A7C385B835
MIME-Version: 1.0
References: <CAPOO0+Mm0Fe+7MGT-05_=gCbOKQn-XOhmqHYN96K6xiS_Hj6BQ@mail.gmail.com>
In-Reply-To: <CAPOO0+Mm0Fe+7MGT-05_=gCbOKQn-XOhmqHYN96K6xiS_Hj6BQ@mail.gmail.com>
Date: Fri, 17 Apr 2020 13:24:33 -0400
Message-ID: <CACoZoo0=QMO-YxuHF4kiO59vR1i=zv=9hyARqemFEfaw8oARdg@mail.gmail.com>
Subject: Re: What is wrong with the name excel?
To: cygwin <cygwin@cygwin.com>
From: Erik Soderquist via Cygwin <cygwin@cygwin.com>
Reply-To: Erik Soderquist <ErikSoderquist@gmail.com>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "Cygwin" <cygwin-bounces@cygwin.com>

On Fri, Apr 17, 2020 at 7:11 AM Gerlach van Beinum wrote:
>
> I made a program to read a csv file from Excel. I called it excel.c
> and it made an executable excel.exe
> If irun that executable with:
> ./excel.exe
> nothing happens, i.i. no output.
>
> If I rename it to a.exe it runs OK.
>
> What about this name excel??

I believe this is actually a Windows issue; Windows recognizes
"excel.exe" as 'a Microsoft package' and intercepts the call to launch
the program, though I would expect Microsoft Excel to launch rather
than 'nothing happening'

I've had this problem before on hosts that did not even have Cygwin
installed when the executable file name matched an existing 'Microsoft
package'

-- Erik
--
"I do not think any of us are truly sane, Caleb. Not even you. Courage
is not sanity. Being willing to die for someone else is not sanity."
... "Love is not sane, nor is faith." ... "If sanity lacks those
things, Caleb, I want no part of it."

-- Alexandria Terri in "Weaving the Wyvern" by Alexis Desiree Thorne
--
Problem reports:      https://cygwin.com/problems.html
FAQ:                  https://cygwin.com/faq/
Documentation:        https://cygwin.com/docs.html
Unsubscribe info:     https://cygwin.com/ml/#unsubscribe-simple