I can confirm - I get this same error. I'm guessing the patch for
this (which is cygwin specific) was accidentally skipped for this
build.
On Sat, Aug 6, 2016 at 4:25 PM, David Rothenberger wrote:
> On 8/6/2016 6:13 AM, Eric Blake (cygwin) wrote:
>>
>> 7b. completion_strip_exe - using 'shopt -s
On Aug 9, 2016, at 7:16 PM, Andrey Repin wrote:
>
>>> As i understand Cygwin will soon no longer support Windows XP resp.
>>> 2003. This means that only Windows versions with native symbolic link
>>> functionality will be supported after that. Would it be possible to use
>>> only native symbolic l
Greetings, David Macek!
>> As i understand Cygwin will soon no longer support Windows XP resp.
>> 2003. This means that only Windows versions with native symbolic link
>> functionality will be supported after that. Would it be possible to use
>> only native symbolic links throughout esp. during se
On Aug 9, 2016, at 7:01 PM, Andrey Repin wrote:
>
>> PATHEXT looks for *executable* files, not file association. I warned
>> previously in this thread about getting the two confused.
>
> Your statement is confusing. If not contradictory.
> PATHEXT tells the shell to consider these file extension
Greetings, Erik Soderquist!
> PATHEXT looks for *executable* files, not file association. I warned
> previously in this thread about getting the two confused.
Your statement is confusing. If not contradictory.
PATHEXT tells the shell to consider these file extensions executable.
If you create a
Greetings, Corinna Vinschen!
>> As for PATHEXT we can do the following scenario instead.
>>
>> export PATHEXT="$PATHEXT;.TXT"
>> vi foo.txt
>> :set ff=dos
>> i
>> a
>> b
>> c
>>
>> :wq
>> cmd /c foo
> As you show here, the PATHEXT definition is so that it also contains
> file suffixes which req
On Aug 4, 2016, at 5:43 PM, Michel LaBarre wrote:
>
> Well my first foray into the world of CYGWIN mailing lists has been a lot of
> fun so far.
You can’t expect to come into a well-established community and expect no
push-back when you insist that they make a wide-reaching change just to suit
The following packages have been updated in the Cygwin distribution:
* mkvtoolnix-9.3.1-2
* mkvtoolnix-gui-9.3.1-2
MKVToolNix is a set of tools to create, alter and inspect Matroska
files (*.mkv, *.mka).
This has been rebuilt with boost-1.60.
Dave.
--
Problem reports: http://cygwin.com/
The following packages have been updated in the Cygwin distribution:
* doxygen-1.8.11-3
* doxygen-doxywizard-1.8.11-3
Doxygen is a documentation system for C++, C, Java, Objective-C, IDL
(Corba and Microsoft flavours) and to some extent PHP, C#, and D.
This has been rebuilt with libclang3.8 and
The following packages have been updated in the Cygwin distribution:
* cppcheck-1.75-1
* cppcheck-gui-1.75-1
Cppcheck is a static analysis tool for C/C++ code. Unlike C/C++
compilers and many other analysis tools it does not detect syntax
errors in the code. Cppcheck primarily detects the types
The following packages have been updated in the Cygwin distribution:
* libtinyxml2-devel-4.0.1-1
* libtinyxml2_4-4.0.1-1
TinyXML-2 is a simple, small, efficient, C++ XML parser that can be
easily integrated into other programmes.
This is an update to the latest upstream release.
Dave.
--
Prob
On Aug 8, 2016, at 8:00 AM, Erik Soderquist wrote:
>
> On Mon, Aug 8, 2016 at 9:52 AM, Erik Soderquist wrote:
>> On Sun, Aug 7, 2016 at 4:11 AM, Herbert Stocker wrote:
code required to handle .exe and .lnk extensions you don't *want*
PATHEXT support anymore.
>>>
>>> Moreso, this
>
> On Aug 9, 2016, at 3:41 PM, Warren Young wrote:
>
> On Aug 9, 2016, at 2:07 AM, Herbert Stocker wrote:
>>
>> On 8/9/2016 2:45 AM, Michel LaBarre wrote:
>>> It could very well be that, as one response to me on this thread
>>> alluded, CYGWIN's role is to provide the equivalent of an isolate
On Aug 9, 2016, at 2:07 AM, Herbert Stocker wrote:
>
> On 8/9/2016 2:45 AM, Michel LaBarre wrote:
>> It could very well be that, as one response to me on this thread
>> alluded, CYGWIN's role is to provide the equivalent of an isolated
> > POSIX VM under Windows without the VM.
>
> ...CYGWIN is
Brent writes:
> I recently encountered a very similar problem, and I think that I have
> a simple solution, so I wanted to followup.
I don't think you've solved your problem.
> --this morning, however, some R code failed that worked just 2 days ago (and
> was not changed in the interim...)
>
On Tue, Aug 9, 2016 at 11:15 AM, cyg Simple wrote:
> On 8/9/2016 10:13 AM, Erik Soderquist wrote:
>> On Tue, Aug 9, 2016 at 8:58 AM, cyg Simple wrote:
>>> I tried "chmod +x foo.txt; ./foo.txt" but that results in Cygwin
>>> assuming the text file is a script and executing each line of the file.
>>>
---
> file. I'm not satisfied that we should continue with the .exe
> artificial symlink for the same reasons we shouldn't use PATHEXT.
> Because of the amount of time to port scripts and software to use the
> .exe suffix for executable files it shou
On 8/9/2016 10:13 AM, Erik Soderquist wrote:
> On Tue, Aug 9, 2016 at 8:58 AM, cyg Simple wrote:
>> I tried "chmod +x foo.txt; ./foo.txt" but that results in Cygwin
>> assuming the text file is a script and executing each line of the file.
>> If PATHEXT were used only to determine that the file sho
On Tue, Aug 9, 2016 at 8:58 AM, cyg Simple wrote:
> I tried "chmod +x foo.txt; ./foo.txt" but that results in Cygwin
> assuming the text file is a script and executing each line of the file.
> If PATHEXT were used only to determine that the file should be passed to
> ShellExecute instead it might b
On 8/9/2016 9:07 AM, Marco Atzeri wrote:
> On 09/08/2016 14:58, cyg Simple wrote:
>>
>>> So, if we actually implement PATHEXT, its usage would be limited to
>>> suffixes of binary files and files starting with #!, or we
>>> would have to use a way to start an application which doesn't work well
>
On 8/8/2016 10:03 AM, Corinna Vinschen wrote:
> On Aug 8 09:43, cyg Simple wrote:
>> On 8/8/2016 7:23 AM, Corinna Vinschen wrote:
>>> On Aug 7 10:11, Herbert Stocker wrote:
On 05.08.2016 17:29, Corinna Vinschen wrote:
If you see the
> code required to handle .exe and .lnk extension
On 09/08/2016 14:58, cyg Simple wrote:
So, if we actually implement PATHEXT, its usage would be limited to
suffixes of binary files and files starting with #!, or we
would have to use a way to start an application which doesn't work well
in a POSIX scenario, or we would have to search the regis
On 8/8/2016 9:43 AM, cyg Simple wrote:
> Maybe we don't want the artificial
> symlink of foo == foo.exe all the time. Maybe it is time we drop the
> artificial symlink altogether in preference for modifying the scripts
> and programs to use .exe when on Windows including Cygwin or perhaps
> creati
On 8/8/2016 10:33 AM, Corinna Vinschen wrote:
> On Aug 8 09:43, cyg Simple wrote:
>> As for PATHEXT we can do the following scenario instead.
>>
>> export PATHEXT="$PATHEXT;.TXT"
>> vi foo.txt
>> :set ff=dos
>> i
>> a
>> b
>> c
>>
>> :wq
>> cmd /c foo
>
> As you show here, the PATHEXT definition
On Mon, Aug 8, 2016 at 7:04 PM, Tobias Zawada wrote:
> Dear all,
> For your information:
>
> I've just compiled
>
> GNU Emacs 25.1.50.1 (x86_64-unknown-cygwin, GTK+ Version 2.24.30) of
> 2016-08-08
>
> from
>
> git clone -b master git://git.sv.gnu.org/emacs.git
>
(snip)
> The only issue I had wit
On 8/9/2016 2:45 AM, Michel LaBarre wrote:
It could very well be that, as one response to me on this thread
alluded, CYGWIN's role is to provide the equivalent of an isolated
> POSIX VM under Windows without the VM.
Having used Cygwin for a long time, maybe 10 or 13 years, i see
that CYGWIN is
26 matches
Mail list logo
