On Tuesday, November 24, 2020, 03:59:19 PM EST, Thomas Wolff
wrote:
Am 24.11.2020 um 21:22 schrieb Kevin Schnitzius via Cygwin:
>> Ctrl-c is broken on mintty.
> This is a wrong statement. For a terminal, Ctrl+c is just a control
> character, nothing else. It's the pty device, shell or
---
winsup/doc/specialnames.xml | 2094 +++
1 file changed, 2094 insertions(+)
diff --git a/winsup/doc/specialnames.xml b/winsup/doc/specialnames.xml
index a1f7401e16b9..a1f9d3f5e806 100644
--- a/winsup/doc/specialnames.xml
+++ b/winsup/doc/specialnames.xml
@@
---
winsup/doc/Makefile.in | 4
1 file changed, 4 insertions(+)
diff --git a/winsup/doc/Makefile.in b/winsup/doc/Makefile.in
index cc4a1bec305b..f2a838a5dcf7 100644
--- a/winsup/doc/Makefile.in
+++ b/winsup/doc/Makefile.in
@@ -17,6 +17,7 @@ htmldir = @htmldir@
mandir = @mandir@
man1dir =
On 11/24/20 2:01 PM, sten.kristian.ivars...@gmail.com wrote:
[snip]
std::filesystem POSIX mode is common to all POSIX platforms where
backslashes are NOT directory separators. How do you make them accept
your demands? How are you going to force POSIX platforms allow
Windows specific code?
On 2020-11-24 07:31, Kristian Ivarsson via Cygwin wrote:
On 11/24/2020 4:32 AM, Kristian Ivarsson via Cygwin wrote:
all the std::filesystem implementations I've seen for Windows
The implementation on top of Cygwin is not "for Windows", it's "for
Cygwin", i.e., "for Posix". And for Cygwin
On Tue, 24 Nov 2020 13:51:59 +0100 (CET)
> QUESTION 1 : HOW TO NOW HANDLE CTRL-C in a multi threaded cygwin application
> regarless of terminal
Could you provide simple test case which can reproduce your problem?
> QUESTION 2 : HOW TO LAUNCH A MINTTY SESSION AS ADMIN
In my environment, "Run as
On 2020-11-24 00:24, Thomas Wolff wrote:
Am 19.11.2020 um 16:57 schrieb Brian Inglis:
On 2020-11-17 16:41, tealhill via Cygwin wrote:
On 2020-11-17 4:23 PM, Thomas Wolff wrote:
Am 17.11.2020 um 20:54 schrieb tealhill via Cygwin:
>>
Cygwin's /etc/profile sets the PATH.
Could /etc/profile
On 2020-07-08 14:05, Brian Inglis wrote:
wget2 is the successor of wget supplying a shared library API like curl to
build a modern, fast, multi-threaded, parallel downloader using HTTP/2, HTTP
compression and If-Modified-Since headers; see:
https://gitlab.com/gnuwget/wget2
It is
On 2020-11-24 07:48, Jon Turney wrote:
On 23/11/2020 22:11, Brian Inglis wrote:
---
winsup/doc/specialnames.xml | 2100 +++
1 file changed, 2100 insertions(+)
I'm not sure how you generated this email. But sending the patch inline (using
Am 24.11.2020 um 21:22 schrieb Kevin Schnitzius via Cygwin:
On Tuesday, November 24, 2020, 07:52:11 AM EST, aki...@free.fr
wrote:
QUESTION 1 : HOW TO NOW HANDLE CTRL-C in a multi threaded cygwin application
regarless of terminal
Ctrl-c is broken on mintty.
This is a wrong statement. For
For the specific case C:\Temp, I found this:
cygpath -ua 'C:\Temp'
-> /cygdrive/c/Temp
cygpath -ua /cygdrive/c/Temp
-> /cygdrive/c/Temp
cygpath -ua '\Temp'
-> /cygdrive/c/Temp
cygpath -ua '/Temp'
-> /Temp
Now Cygwin is open source, so you, too, could grab the code in cygpath and
On Tuesday, November 24, 2020, 07:52:11 AM EST, aki...@free.fr
wrote:
> QUESTION 1 : HOW TO NOW HANDLE CTRL-C in a multi threaded cygwin application
>regarless of terminal
Ctrl-c is broken on mintty. I use this:
D:\cygwin64\bin\mintty.exe -o "KeyFunctions=A+F5:break" -
And use alt-F5 as
On 11/24/2020 9:31 AM, Kristian Ivarsson via Cygwin wrote:
On 11/24/2020 4:32 AM, Kristian Ivarsson via Cygwin wrote:
all the std::filesystem implementations I've seen for Windows
The implementation on top of Cygwin is not "for Windows", it's "for
Cygwin", i.e., "for Posix". And for Cygwin
On 24/11/2020 10:43, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> Ignore that message, I made a silly mistake.
>
> On 24/11/2020 10:15, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
>> Well, something's gone wrong with my Cygwin install I think, because
>> even with previously working cygport
Sorry for the missing information.
https://mirrors.filigrane-technologie.fr/cygwin/x86_64/setup.ini
Actually indexing is disable on the configuration, if you need it, i
can enable it if necessary.
Cordialement,
Geoffroy Van Elsuve
114, boulevard Haussmann
75008 Paris
Tél:06 60 69 72 32
On 24/11/2020 14:52, Bill Stewart wrote:
> On Tue, Nov 24, 2020 at 12:25 AM Thomas Wolff wrote:
>
>>> and please note that SysNative appears nowhere!
>> That's because Sysnative is not a known folder. It is rather unknown
>> just because it is virtual :)
>> And that is the problem I tried to
On Tue, Nov 24, 2020 at 12:25 AM Thomas Wolff wrote:
> > and please note that SysNative appears nowhere!
>
> That's because Sysnative is not a known folder. It is rather unknown
> just because it is virtual :)
> And that is the problem I tried to address. In cygwin32, you can `cd
>
On 23/11/2020 17:35, Geoffroy Van Elsuve wrote:
Hi,
Can you add our server to mirror list.
Europe:
France: mirrors.filigrane-technologie.fr(https)
To add this mirror, I need the URL at which Cygwin files can be accessed.
'https://mirrors.filigrane-technologie.fr/' itself just gives '403
On 23/11/2020 22:11, Brian Inglis wrote:
---
winsup/doc/specialnames.xml | 2100 +++
1 file changed, 2100 insertions(+)
I'm not sure how you generated this email. But sending the patch inline
(using 'git-send-email'?), rather than as an attachment makes it
> On 11/24/2020 4:32 AM, Kristian Ivarsson via Cygwin wrote:
>
> > all the std::filesystem implementations I've seen for Windows
>
> The implementation on top of Cygwin is not "for Windows", it's "for
> Cygwin", i.e., "for Posix". And for Cygwin that's the right thing to do.
> And that's where
> > [snip]
> >
> >> std::filesystem POSIX mode is common to all POSIX platforms where
> >> backslashes are NOT directory separators. How do you make them accept
> >> your demands? How are you going to force POSIX platforms allow
> >> Windows specific code?
> >
> > I've been trying to say over and
For ease of reviewing, this patch doesn't contain changes to generated
files which would be made by running ./autogen.sh.
v2:
* Include tzmap.h in BUILT_SOURCES
* Make per-file flags appear after user-supplied CXXFLAGS, so they can
override optimization level.
* Correct .o files used to define
On 11/24/2020 4:32 AM, Kristian Ivarsson via Cygwin wrote:
all the std::filesystem implementations I've seen for Windows
The implementation on top of Cygwin is not "for Windows", it's "for Cygwin", i.e., "for Posix". And
for Cygwin that's the right thing to do. And that's where we keep
>From some months, use of a terminal with cygwin is changing and changing but
>for me with more and more difficult to use.
Prior to 3.1 version of the cygwin package, I could use two kinds of terminals
bash and mintty.
I like the bash version because I can launch with it an admin session,
On 11/24/20 11:35 AM, sten.kristian.ivars...@gmail.com wrote:
[snip]
std::filesystem POSIX mode is common to all POSIX platforms where
backslashes are NOT directory separators. How do you make them accept your
demands? How are you going to force POSIX platforms allow Windows specific
code?
[snip]
> std::filesystem POSIX mode is common to all POSIX platforms where
> backslashes are NOT directory separators. How do you make them accept your
> demands? How are you going to force POSIX platforms allow Windows specific
> code?
I've been trying to say over and over again that our code
On Nov 23 15:10, Brian Inglis wrote:
> Hacked a Cygwin proc.5 man page, by combing through fhandler_proc...,
> converted to proc-5.xml using doclifter, included after pathnames-proc
> before pathnames-proc-registry sections in specialnames.xml, and
> modified to match and create a refentry to
Ignore that message, I made a silly mistake.
On 24/11/2020 10:15, Hamish McIntyre-Bhatty via Cygwin-apps wrote:
> Well, something's gone wrong with my Cygwin install I think, because
> even with previously working cygport recipes, I can no longer produce a
> working build.
>
> The samples tend to
On 11/24/20 9:32 AM, sten.kristian.ivars...@gmail.com wrote:
That's not what Cygwin is for, you ignore everything while conveniently
claiming to be looking for "insightful thoughts". You still haven't
answered where is it in the POSIX standard requires backslashes to be used
as separator or how
Well, something's gone wrong with my Cygwin install I think, because
even with previously working cygport recipes, I can no longer produce a
working build.
The samples tend to either exit immediately or segfault, and trying to
use wxPython yields:
"
Traceback (most recent call last):
File
> On 11/23/20 8:35 AM, sten.kristian.ivars...@gmail.com wrote:
> >> On 11/20/20 8:31 AM, Kristian Ivarsson via Cygwin wrote:
> that, for me, /c works.) Likewise, I would expect the normative
> path separator to be / not \, and an absolute path to start with /.
> Windows offers
Dear cygwin.com Team,
I went to your Site cygwin.com and wanted to shoot you a quick note. If you
want I can make a few changes (aesthetically and/or SEO-wise) to make your
site convert more visitors into leads and to get it placed higher in the
organic search for a few of the select terms.
32 matches
Mail list logo
