[RFU] monotone-1.0-1
http://lapo.it/cygwin/monotone/monotone-1.0-1.tar.bz2 http://lapo.it/cygwin/monotone/monotone-1.0-1-src.tar.bz2 http://lapo.it/cygwin/whois/setup.hint (unchanged) % sha256sum monotone*bz2 5c530bc4652b2c08b5291659f0c130618a14780f075f981e947952dcaefc31dc monotone-1.0.tar.bz2 5e9b409cf5ab0ff0302b66ae55b072d9776f0df0308fbf26cfbfb6925ea2e1c3 monotone-1.0-1.tar.bz2 c2b2bbd868514c734150f0372fc89067c6800f3c5b73b1dd277bd5b7609a56db monotone-1.0-1-src.tar.bz2 -- Lapo Luchini - http://lapo.it/ “Digital files cannot be made uncopyable, any more than water can be made not wet.” (Bruce Schneier, 2001-05-15) signature.asc Description: OpenPGP digital signature
Re: [RFU] monotone-1.0-1
On May 9 13:26, Lapo Luchini wrote: http://lapo.it/cygwin/monotone/monotone-1.0-1.tar.bz2 http://lapo.it/cygwin/monotone/monotone-1.0-1-src.tar.bz2 Uploaded. What about all the old versions? Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
src/winsup/doc ChangeLog new-features.sgml
CVSROOT:/cvs/src Module name:src Changes by: yselkow...@sourceware.org 2011-05-09 03:59:00 Modified files: winsup/doc : ChangeLog new-features.sgml Log message: * new-features.sgml (ov-new1.7.10): Document clock_settime. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/ChangeLog.diff?cvsroot=srcr1=1.343r2=1.344 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/doc/new-features.sgml.diff?cvsroot=srcr1=1.79r2=1.80
Re: [PATCH] Fix /proc/meminfo and /proc/swaps for 4GB
Hi Yaakov, On May 6 14:03, Yaakov (Cygwin/X) wrote: As promised, this patch ports the /proc/meminfo code to use sysinfo(2), and fixes the case where RAM or swap space totals more than 4GB. It also fixes the /proc/swaps code for paging files larger than 4GB. For example: $ cat /proc/meminfo total: used: free: Mem: 429305856018281512962464907264 Swap: 12884901888 14680064 12870221824 MemTotal:4192440 kB MemFree: 2407136 kB MemShared: 0 kB HighTotal: 0 kB HighFree: 0 kB LowTotal:4192440 kB LowFree: 2407136 kB SwapTotal: 12582912 kB SwapFree: 12568576 kB I'm not sure I understand this new format. Why do you keep the Mem: and Swap: lines? Linux doesn't have them and top appears to work without them. And then, why do you print MemShared, HighTotal, and HighFree, even though they are always 0, but not all the other ~40 lines Linux' meminfo has, too? Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: [PATCH] clock_settime
Hi Yaakov, On May 8 17:48, Yaakov (Cygwin/X) wrote: This implements the POSIX clock_settime function, on top of settimeofday: http://pubs.opengroup.org/onlinepubs/9699919799/functions/clock_settime.html http://www.kernel.org/doc/man-pages/online/pages/man3/clock_gettime.3.html http://www.kernel.org/doc/man-pages/online/pages/man2/settimeofday.2.html The fixes to settimeofday are necessary both to match BSD and Linux behaviour, and to provide the errnos and return status for clock_settime required by POSIX. I also fixed posix.sgml WRT clock_setres. Patches for winsup/cygwin and winsup/doc, plus test programs for both functions, attached. Thanks for the patch. Index: times.cc === RCS file: /cvs/src/src/winsup/cygwin/times.cc,v retrieving revision 1.107 diff -u -r1.107 times.cc --- times.cc 2 May 2011 15:28:35 - 1.107 +++ times.cc 8 May 2011 17:55:34 - @@ -111,6 +111,12 @@ tz = tz; /* silence warning about unused variable */ + if (tv-tv_usec 0 || tv-tv_usec = 100) Not your fault, but what I'm missing in settimeofday is an EFAULT handler. Could you please add one, just like in the times() function a couple of lines earlier? The `tz = tz;' line can go away, the usage is covered by the syscall_printf at the end of the function. Other than that, please apply. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: Fwd: octave updated to 3.4.0-3. Please test (strcat error)
0 [main] gnuplot 5204 exception::handle: Exception: STATUS_ACCESS_VIOLATION 1450 [main] gnuplot 5204 open_stackdumpfile: Dumping stack trace to gnuplot.exe.stackdump This error message is not repetitive... Here are my script: perfo.sh: #!/bin/bash gnuplot -persist ../script_gnuplot/puissance_local.gnu gnuplot -persist ../script_gnuplot/couple_local.gnu gnuplot -persist ../script_gnuplot/force_local.gnu puissance_local.gnu: set view map set xlabel 'Envergure [%]' set ylabel 'Puissance [W]' plot grep '400.0' performance/rotor1/performance_local.dat using 10:5 w lines title Aero, \ grep '400.0' performance/rotor1/performance_local.dat using 10:8 w lines title Meca set term postscript enhanced color set output performance/rotor1/puissance_local_400RPM.eps replot -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
unknown command diff
I am trying to run what is a basic diff of 2 tags in a repo, to see what changes have occurred between the 2. But whenever I attempt to in cygwin I get the below error. Is this a known issue, or do I need to set something up specially to get this working. Sorry I am newish to cygwin as use Ubuntu normally. $ svn diff --summarize http://svn./tags/x/public http://svn./tags/y/public Unknown command: 'diff' Type 'svn help' for usage. Thankyou for your help, Dan -- View this message in context: http://old.nabble.com/unknown-command-diff-tp31575949p31575949.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: unknown command diff
retrodans wrote, On 9.5.2011 13:26: I am trying to run what is a basic diff of 2 tags in a repo, to see what changes have occurred between the 2. But whenever I attempt to in cygwin I get the below error. Is this a known issue, or do I need to set something up specially to get this working. Sorry I am newish to cygwin as use Ubuntu normally. $ svn diff --summarize http://svn./tags/x/public http://svn./tags/y/public Unknown command: 'diff' Type 'svn help' for usage. My guess is that you have not installed the diffutils package. I would know for sure had you followed problem reporting procedure at http://cygwin.com/problems.html. -- VH -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: unknown command diff
diffutils appears to be there, so I went to run cygcheck for you as per the link you sent, but that doesn't appear to create a file on my c: amd just returns several warnings along the lines of: OpenService failed for This is for things such as: DcomLaunch, odserv, ose, pla,QWAVE, RpcEptMapper, RpcSs Do I need to install a specific package for this to work? Václav Haisman wrote: retrodans wrote, On 9.5.2011 13:26: I am trying to run what is a basic diff of 2 tags in a repo, to see what changes have occurred between the 2. But whenever I attempt to in cygwin I get the below error. Is this a known issue, or do I need to set something up specially to get this working. Sorry I am newish to cygwin as use Ubuntu normally. $ svn diff --summarize http://svn./tags/x/public http://svn./tags/y/public Unknown command: 'diff' Type 'svn help' for usage. My guess is that you have not installed the diffutils package. I would know for sure had you followed problem reporting procedure at http://cygwin.com/problems.html. -- VH -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple -- View this message in context: http://old.nabble.com/unknown-command-diff-tp31575949p31576087.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: unknown command diff
On Mon, May 9, 2011 at 1:52 PM, retrodans d...@retrobadger.net wrote: diffutils appears to be there, so I went to run cygcheck for you as per the link you sent, but that doesn't appear to create a file on my c: amd just returns several warnings along the lines of: OpenService failed for This is for things such as: DcomLaunch, odserv, ose, pla,QWAVE, RpcEptMapper, RpcSs Do I need to install a specific package for this to work? No, you just need to follow the procedure as described in: Problem reports: http://cygwin.com/problems.html Did you redirect the output, as in: cygcheck -s -v -r cygcheck.out If yes, the output should be in the current directory. If you can't find the file, try (from a Cygwin prompt) cygcheck -s -v -r `cygpath -D`/cygcheck.out That would put the output on the desktop. The warnings about OpenService are harmless. Hope this helps, Csaba -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ The Tao of math: The numbers you can count are not the real numbers. Life is complex, with real and imaginary parts. Ok, it boots. Which means it must be bug-free and perfect. -- Linus Torvalds People disagree with me. I just ignore them. -- Linus Torvalds -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: unknown command diff
Okay, that seems much better, for some reason the file wasn't going onto the root of c, but running it directly to desktop worked a treat, so have attached the file now. As a note, I had installed cygwin some time ago, but did not use it back then, so if a fresh re-install is required, then I can do so. Csaba Raduly-2 wrote: On Mon, May 9, 2011 at 1:52 PM, retrodans d...@retrobadger.net wrote: diffutils appears to be there, so I went to run cygcheck for you as per the link you sent, but that doesn't appear to create a file on my c: amd just returns several warnings along the lines of: OpenService failed for This is for things such as: DcomLaunch, odserv, ose, pla,QWAVE, RpcEptMapper, RpcSs Do I need to install a specific package for this to work? No, you just need to follow the procedure as described in: Problem reports: http://cygwin.com/problems.html Did you redirect the output, as in: cygcheck -s -v -r cygcheck.out If yes, the output should be in the current directory. If you can't find the file, try (from a Cygwin prompt) cygcheck -s -v -r `cygpath -D`/cygcheck.out That would put the output on the desktop. The warnings about OpenService are harmless. Hope this helps, Csaba -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ The Tao of math: The numbers you can count are not the real numbers. Life is complex, with real and imaginary parts. Ok, it boots. Which means it must be bug-free and perfect. -- Linus Torvalds People disagree with me. I just ignore them. -- Linus Torvalds -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple http://old.nabble.com/file/p31576638/cygcheck.out cygcheck.out -- View this message in context: http://old.nabble.com/unknown-command-diff-tp31575949p31576638.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: unknown command diff
On Mon, May 9, 2011 at 3:11 PM, retrodans d...@retrobadger.net wrote: Okay, that seems much better, for some reason the file wasn't going onto the root of c, but running it directly to desktop worked a treat, so have attached the file now. If you run from the command prompt, then your current directory is /home/dan, in other words, C:\cygwin\home\dan You should find cygcheck.out from your earlier run, there. As a note, I had installed cygwin some time ago, but did not use it back then, so if a fresh re-install is required, then I can do so. If there is no C:\cygwin\bin\diff.exe then reinstalling the diffutils package may help. Run the Cygwin setup, find diffutils under Utils, and click on the circular arrows until it says Reinstall. Hope this helps, Csaba -- GCS a+ e++ d- C++ ULS$ L+$ !E- W++ P+++$ w++$ tv+ b++ DI D++ 5++ The Tao of math: The numbers you can count are not the real numbers. Life is complex, with real and imaginary parts. Ok, it boots. Which means it must be bug-free and perfect. -- Linus Torvalds People disagree with me. I just ignore them. -- Linus Torvalds -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: difficulties with snapshots
Hello,
This one is a follow-up of http://cygwin.com/ml/cygwin/2011-05/msg00042.html
On 2011-05-05 11:19:56 -0400, Christopher Faylor wrote:
On Thu, May 05, 2011 at 10:47:39AM +0200, EXCOFFIER Denis wrote:
2) More importantly, i was not able to compile snapshots since about
beginning of May, with an error: wchar.h not found (in lsaauth).
The snapshot 20110420 has compiled correctly at that time (say: 21/4);
but i was not able to recompile it recently. You must know that
i update the cygwin packages every day, therefore the problem probably
comes from a recently added package.
Snapshots are provided as-is. If you can't compile it then PTC.
Please consider this hideous patch thoughtfully, it solves my wchar.h not
found problem in lsaauth, and the full cygwin tree now compiles ok
like before.
diff -cNr cygwin-snapshot-20110506-1/winsup/lsaauth/Makefile.in
cygwin-snapshot-20110506-2/winsup/lsaauth/Makefile.in
*** cygwin-snapshot-20110506-1/winsup/lsaauth/Makefile.in
2011-04-07 08:09:27.0 +0159
--- cygwin-snapshot-20110506-2/winsup/lsaauth/Makefile.in
2011-05-09 15:44:13.476681300 +0159
***
*** 29,35
CC := @CC@
CC_FOR_TARGET := $(CC)
! override CC := @NO_CYGWIN@ $(firstword ${CC})
CFLAGS := @CFLAGS@
--- 29,35
CC := @CC@
CC_FOR_TARGET := $(CC)
! #override CC := @NO_CYGWIN@ $(firstword ${CC})
CFLAGS := @CFLAGS@
Regards,
Denis Excoffier.
This message was sent using IMP, the Internet Messaging Program.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Re: GNU screen on Cygwin: Cannot seem to reattach, no matter what I try
On 11:59 AM, Andrew Schulman wrote: snip * Read /usr/share/doc/screen/README.Cygwin - there are descriptions there of known problems with reattachment. But mostly it has to do with using screen in a DOS terminal. snip Any suggestions from other screen users? Based on my experience, I'd add mintty to the list of terminals that work out of the box for reattaching screen. Easy to install from setup.exe and test. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Who's using CYGWIN=tty and why?
Hi, Chris and I are wondering how many people are using the Windows console as local console window in CYGWIN=tty mode and why. Here's why we ask: We are both not sure why anybody would use it voluntarily, given that it's I/O is extremly slow, compared to using a Windows console window in the default CYGWIN=notty mode or, even better, mintty. Actually, we only keep the console tty mode up because it was always there, 14 years or so. So, if you're using a console in tty mode, why are doing that? Did you ever notice that it's much slower? Did you ever consider to switch to mintty or any other terminal emulator instead? If not, why? Would anybody really *miss* the CYGWIN=tty mode? If so, why? What does this mode have which isn't covered by notty mode or another terminal emulator? Please enlighten us, otherwise we will just rip out this terminal mode for good. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Who's using CYGWIN=tty and why?
Corinna Vinschen writes: Chris and I are wondering how many people are using the Windows console as local console window in CYGWIN=tty mode and why. I am one such. Here's why we ask: We are both not sure why anybody would use it voluntarily, given that it's I/O is extremly slow, compared to using a Windows console window in the default CYGWIN=notty mode or, even better, mintty. Actually, we only keep the console tty mode up because it was always there, 14 years or so. Um, history is sticky, is I guess the answer. When I started using cygwin (a _long_ time ago), CYGWIN=tty was the recommended setting (and isn't it still there in cygwin/cygwin.bat ?). So I have faithfully copied that into my Windows environment initialisation ever since. Is it time to remove it? I do use a windows console occasionally for pure Windows activities---what change(s) will I see? ht -- Henry S. Thompson, School of Informatics, University of Edinburgh 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 651-1426, e-mail: h...@inf.ed.ac.uk URL: http://www.ltg.ed.ac.uk/~ht/ [mail from me _always_ has a .sig like this -- mail without it is forged spam] -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Who's using CYGWIN=tty and why?
Chris and I are wondering how many people are using the Windows console as local console window in CYGWIN=tty mode and why. /usr/share/doc/screen/README.Cygwin says: In a DOS console, screen works, but in order to be able to reattach detached sessions, you must set tty in the CYGWIN environment variable If you use screen in a DOS console without CYGWIN=tty, you will be able to detach sessions, but reattaching to them later is likely to fail. Then you'll have to use 'screen -wipe' to clear out your old unusable sessions, and you may have to manually kill their child processes. So it seems that screen users who are still using a DOS console need CYGWIN=tty. I have no idea how many such people there are. If CYGWIN=tty is going away, then we could simply tell screen users that the DOS console is no longer supported in screen, since reattaching there is likely to fail. Andrew. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Who's using CYGWIN=tty and why?
On May 9 17:21, Henry S. Thompson wrote: Corinna Vinschen writes: Chris and I are wondering how many people are using the Windows console as local console window in CYGWIN=tty mode and why. I am one such. Here's why we ask: We are both not sure why anybody would use it voluntarily, given that it's I/O is extremly slow, compared to using a Windows console window in the default CYGWIN=notty mode or, even better, mintty. Actually, we only keep the console tty mode up because it was always there, 14 years or so. Um, history is sticky, is I guess the answer. When I started using cygwin (a _long_ time ago), CYGWIN=tty was the recommended setting (and isn't it still there in cygwin/cygwin.bat ?). So I have No, it's not the default, and it never was, actually. faithfully copied that into my Windows environment initialisation ever since. Is it time to remove it? I do use a windows console occasionally for pure Windows activities---what change(s) will I see? I don't quite understand, if you use the Windows console for pure Windows stuff, why do you use tty mode at all? And what do you use to run Cygwin apps? Many native Windows tools don't work well in tty mode anyway. For non-Cygwin tools, the default notty mode is the most compatible one. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Who's using CYGWIN=tty and why?
On 5/9/2011 12:10 PM, Corinna Vinschen wrote: Chris and I are wondering how many people are using the Windows console as local console window in CYGWIN=tty mode and why. I'm not but there's various references to it it the web about it being requires for Emacs. eg. http://blog.arithm.com/2007/12/01/killing-cygwin-emacs/ I hope that these references are outdated with Cygwin 1.7? The other references to it I see are about requiring tty mode for sshd. This is also for historical reasons but I'm not sure if we still need it in Cygwin 1.7. -Edward -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Who's using CYGWIN=tty and why?
On 5/9/2011 12:39 PM, Edward Lam wrote: On 5/9/2011 12:10 PM, Corinna Vinschen wrote: Chris and I are wondering how many people are using the Windows console as local console window in CYGWIN=tty mode and why. I'm not but there's various references to it it the web about it being requires for Emacs. eg. http://blog.arithm.com/2007/12/01/killing-cygwin-emacs/ I hope that these references are outdated with Cygwin 1.7? This is still the case: emacs does not work well in the console unless CYGWIN=tty is set. But I don't see this as a reason to keep the CYGWIN=tty mode for the console. I see it as a reason for emacs users to use a different terminal emulator, such as mintty. Ken -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Who's using CYGWIN=tty and why?
Corinna Vinschen writes: On May 9 17:21, Henry S. Thompson wrote: Corinna Vinschen writes: Chris and I are wondering how many people are using the Windows console as local console window in CYGWIN=tty mode and why. I am one such. Here's why we ask: We are both not sure why anybody would use it voluntarily, given that it's I/O is extremly slow, compared to using a Windows console window in the default CYGWIN=notty mode or, even better, mintty. Actually, we only keep the console tty mode up because it was always there, 14 years or so. Um, history is sticky, is I guess the answer. When I started using cygwin (a _long_ time ago), CYGWIN=tty was the recommended setting (and isn't it still there in cygwin/cygwin.bat ?). So I have No, it's not the default, and it never was, actually. Well, I guess I misunderstood the earlier version of this prose (from [1]): The CYGWIN variable is used to configure many global settings for the Cygwin runtime system. Initially you can leave CYGWIN unset or set it to tty (e.g. to support job control with ^Z etc...) using a syntax like this in the DOS shell, before launching bash. plus the prose further up Some of these settings need to be in effect prior to launching the initial Cygwin session (before starting your bash shell, for instance). They should therefore be set in the Windows environment to mean that CYGWIN=tty was recommended. I followed what I understood that recommendation to be at the time, and have faithfully copied that into my Windows environment initialisation ever since. I don't quite understand, if you use the Windows console for pure Windows stuff, why do you use tty mode at all? Because I thought that having job control might be useful, and so I followed the recommendation above. . . I clearly didn't understand, at the time, that the console as such, vs. the console running bash as from cygwin.bat, were not the same thing. And what do you use to run Cygwin apps? mintty, of course :-) Many native Windows tools don't work well in tty mode anyway. For non-Cygwin tools, the default notty mode is the most compatible one. OK, I hear that as answers along the lines of yes, and only good things to my questions: Is it time to remove it? I do use a windows console occasionally for pure Windows activities---what change(s) will I see? The Wayback machine [2] suggests that the prose quoted above hasn't changed for nearly 11 years -- perhaps it's due for an update? ht [1] http://cygwin.com/cygwin-ug-net/setup-env.html [2] http://replay.web.archive.org/2829065425/http://sources.redhat.com/cygwin/cygwin-ug-net/setup-env.html -- Henry S. Thompson, School of Informatics, University of Edinburgh 10 Crichton Street, Edinburgh EH8 9AB, SCOTLAND -- (44) 131 650-4440 Fax: (44) 131 651-1426, e-mail: h...@inf.ed.ac.uk URL: http://www.ltg.ed.ac.uk/~ht/ [mail from me _always_ has a .sig like this -- mail without it is forged spam] -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Who's using CYGWIN=tty and why?
Hi all, At the risk of exciting the contempt avalanche all too pervasive in this list (never at any time by Corinna--THANKS): I'm not sure I understand the difference between the DOS console and the Windows console. And, truth to tell, I've been around here for a good long time and never heard of CYGWIN=notty. However: BRLTTY is a screen reading system that enables the use of refreshable braille devices (see below). It works on Linux and other unixes both in console mode and as an adjunct to the Unix GUI screen reader (Orca). It also works at the DOS command prompt, and gloriously beautifully in Cygwin. I tried mintty once and brltty would not read that window. Whether this can be changed by the developers I don't know. I've sporadically tried things like rxvt and when they didn't work right off the bat I didn't bother anymore since brltty is really splendid. For what it's worth, here's my cygwin.bat. Exactly how much of it is necessary and what the costs of what changes might be I don't know: @echo off c: chdir c:\cygwin\bin set HOME=c:\cygwin\home\me set LANG=en_US.UTF-8 set CYGWIN=tty notitle glob bash --login -i The rest of this message is for the merely curious: What's a refreshable braille device: It's a box that has a smooth wire screen on the top. There are pins below the holes in this wire screen. The pins can be pushed up through the holes (these are dots) or pulled down below them (these are non-dots). These pins are in eight rows corresponding to the eight rows of dots in a braille cell (eight on the computer, six for standard paper braille). There are from 18 to 84 of these 8-dot cells across the length of the wire screen, and there are buttons on the braille device to move this 18-to-84 character window around on the screen. What's splendid about brltty in Cygwin? Other Windows screen readers have braille, but frequently it skips blank lines for reasons I don't begin to comprehend. Brltty doesn't skip them. So it's much easier to tell the screen layout in brltty than with the braille from a Windows screen reader. Brltty is also more responsive and more accurate (it doesn't spuriously underline letters, one of the problems with braille in other screen readers). While the Windows screen reader I use (JAWS) can see the Cygwin text, not all can. Narrator is a part of the Windows OS; it's on every Windows computer. It can't see the text in Cygwin at all. I've included the brltty developers on this message and will send them Corinna's original so you may hear from somebody who knows what they're talking about. :-) Castigation, Mastication and Denigration cheerfully accepted, -- Lee Maschmeyer Wayne State University Computing Center 5925 Woodward, #281 Detroit MI 48202 USA -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Who's using CYGWIN=tty and why?
Lee Maschmeyer, le Mon 09 May 2011 13:40:57 -0400, a écrit : And, truth to tell, I've been around here for a good long time and never heard of CYGWIN=notty. As I understand it, notty is already the default, so unless you have an explicit CYGWIN=tty, it's already notty. brltty does not touch at the cygwin tty layer. It just uses native win32 interfaces to access the consoles (AttachConsole, ReadConsoleOutputCharacterW) and simulate keypresses (WriteConsoleInputW), consoles need to be windows console, but that's all. Samuel -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
strace swallows stderr?
Hi all, It seems that when strace is running an app, that app's stderr output disappears. Is this normal/expected? The problem doesn't seem to arise if strace opens the app in a different window or sends its own output to a log file, but both of those have their disadvantages. Thanks, Ryan -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Who's using CYGWIN=tty and why?
On Mon, May 09, 2011 at 12:39:47PM -0400, Edward Lam wrote: On 5/9/2011 12:10 PM, Corinna Vinschen wrote: Chris and I are wondering how many people are using the Windows console as local console window in CYGWIN=tty mode and why. I'm not but there's various references to it it the web about it being requires for Emacs. eg. http://blog.arithm.com/2007/12/01/killing-cygwin-emacs/ I hope that these references are outdated with Cygwin 1.7? The other references to it I see are about requiring tty mode for sshd. This is also for historical reasons but I'm not sure if we still need it in Cygwin 1.7. We have never needed tty mode for sshd. There is a web site which suggests (suggested?) it but it is mistaken. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Who's using CYGWIN=tty and why?
On Mon, May 09, 2011 at 07:52:05PM +0200, Samuel Thibault wrote: Lee Maschmeyer, le Mon 09 May 2011 13:40:57 -0400, a ?crit : And, truth to tell, I've been around here for a good long time and never heard of CYGWIN=notty. As I understand it, notty is already the default, so unless you have an explicit CYGWIN=tty, it's already notty. Yes, that's what Corinna meant by default CYGWIN=notty. brltty does not touch at the cygwin tty layer. It just uses native win32 interfaces to access the consoles (AttachConsole, ReadConsoleOutputCharacterW) and simulate keypresses (WriteConsoleInputW), consoles need to be windows console, but that's all. Ok, it sounds like there is no need whatsoever to set CYGWIN=tty with brltty. That is good news. I'd be pretty surprised if it was the case since if CYGWIN=tty *was* required then it seems like mintty would work too since the difference between the ptys that mintty uses and CYGWIN=tty mode is very small. Has anyone tried running brltty without setting CYGWIN=tty? cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Who's using CYGWIN=tty and why?
On Mon, May 09, 2011 at 04:00:25PM -0400, Christopher Faylor wrote: On Mon, May 09, 2011 at 12:39:47PM -0400, Edward Lam wrote: On 5/9/2011 12:10 PM, Corinna Vinschen wrote: Chris and I are wondering how many people are using the Windows console as local console window in CYGWIN=tty mode and why. I'm not but there's various references to it it the web about it being requires for Emacs. eg. http://blog.arithm.com/2007/12/01/killing-cygwin-emacs/ I hope that these references are outdated with Cygwin 1.7? The other references to it I see are about requiring tty mode for sshd. This is also for historical reasons but I'm not sure if we still need it in Cygwin 1.7. We have never needed tty mode for sshd. There is a web site which suggests (suggested?) it but it is mistaken. (was?) -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Who's using CYGWIN=tty and why?
Christopher Faylor, le Mon 09 May 2011 16:05:24 -0400, a écrit : Has anyone tried running brltty without setting CYGWIN=tty? I never set the CYGWIN variable nowadays, actually, and brltty works fine in that case. Samuel -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
RE: Who's using CYGWIN=tty and why?
Date: Mon, 9 May 2011 18:10:28 +0200 From: corinna Subject: Who's using CYGWIN=tty and why? Hi, Chris and I are wondering how many people are using the Windows console as local console window in CYGWIN=tty mode and why. Here's why we ask: We are both not sure why anybody would use it voluntarily, given that it's I/O is extremly slow, compared to using a Windows console window in the default CYGWIN=notty mode or, even better, mintty. Actually, we only keep the console tty mode up because it was always there, 14 years or so. So, if you're using a console in tty mode, why are doing that? Did you ever notice that it's much slower? Did you ever consider to switch to mintty or any other terminal emulator instead? If not, why? Would anybody really *miss* the CYGWIN=tty mode? If so, why? What does this mode have which isn't covered by notty mode or another terminal emulator? Please enlighten us, otherwise we will just rip out this terminal mode for good. I use CYGWIN=tty, and have used it forever. Back in the dark ages, I recall that there were reasons that I chose it...control character handling or formatting? It made something I cared about work properly and four M$ operating systems later... I did try rxvt and didn't like the way it looked, so I stayed with a console window and CYGWIN=tty. Thanks, ...Karl -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Who's using CYGWIN=tty and why?
On 5/9/2011 16:14, Karl M wrote: I did try rxvt and didn't like the way it looked, so I stayed with a console window and CYGWIN=tty. Hi, Karl. Have you tried mintty yet? If looks are what turned you away from rxvt, I think you'll like mintty much more. -Jeremy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Who's using CYGWIN=tty and why?
Am 09.05.2011 18:10, schrieb Corinna Vinschen: Hi, Chris and I are wondering how many people are using the Windows console as local console window in CYGWIN=tty mode and why. Here's why we ask: We are both not sure why anybody would use it voluntarily, given that it's I/O is extremly slow, compared to using a Windows console window in the default CYGWIN=notty mode or, even better, mintty. Actually, we only keep the console tty mode up because it was always there, 14 years or so. So, if you're using a console in tty mode, why are doing that? Did you ever notice that it's much slower? Did you ever consider to switch to mintty or any other terminal emulator instead? If not, why? Would anybody really *miss* the CYGWIN=tty mode? If so, why? What does this mode have which isn't covered by notty mode or another terminal emulator? I don't use it but there is one difference that I actually reported years ago: http://sourceware.org/bugzilla/show_bug.cgi?id=513 and I mentioned it again in http://cygwin.com/ml/cygwin-patches/2009-q4/msg00144.html and http://cygwin.com/ml/cygwin-patches/2009-q4/msg00155.html - later I tried to debug again and saw that with CYGWIN=tty, one fhandler_console object drives console I/O whereas with CYGWIN=notty 3 objects are created (for stdin, stdout, stderr). This is the reason for the cursor position response code getting lost because it is pushed into the wrong fhandler_console object. I tried to patch it but it got all messed up so I didn't post anything then. __ Thomas -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Who's using CYGWIN=tty and why?
On Tue, May 10, 2011 at 12:27:08AM +0200, Thomas Wolff wrote: Am 09.05.2011 18:10, schrieb Corinna Vinschen: Chris and I are wondering how many people are using the Windows console as local console window in CYGWIN=tty mode and why. Here's why we ask: We are both not sure why anybody would use it voluntarily, given that it's I/O is extremly slow, compared to using a Windows console window in the default CYGWIN=notty mode or, even better, mintty. Actually, we only keep the console tty mode up because it was always there, 14 years or so. So, if you're using a console in tty mode, why are doing that? Did you ever notice that it's much slower? Did you ever consider to switch to mintty or any other terminal emulator instead? If not, why? Would anybody really *miss* the CYGWIN=tty mode? If so, why? What does this mode have which isn't covered by notty mode or another terminal emulator? I don't use it but there is one difference that I actually reported years ago: http://sourceware.org/bugzilla/show_bug.cgi?id=513 and I mentioned it again in http://cygwin.com/ml/cygwin-patches/2009-q4/msg00144.html and http://cygwin.com/ml/cygwin-patches/2009-q4/msg00155.html - later I tried to debug again and saw that with CYGWIN=tty, one fhandler_console object drives console I/O whereas with CYGWIN=notty 3 objects are created (for stdin, stdout, stderr). This is the reason for the cursor position response code getting lost because it is pushed into the wrong fhandler_console object. I tried to patch it but it got all messed up so I didn't post anything then. We will certainly be willing to fix problems as they occur. I don't think that erroneous cursor reporting is a show stopper. cgf -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Who's using CYGWIN=tty and why?
On 5/9/11, Corinna Vinschen wrote: On May 9 17:21, Henry S. Thompson wrote: Corinna Vinschen writes: Chris and I are wondering how many people are using the Windows console as local console window in CYGWIN=tty mode and why. I am one such. Here's why we ask: We are both not sure why anybody would use it voluntarily, given that it's I/O is extremly slow, compared to using a Windows console window in the default CYGWIN=notty mode or, even better, mintty. Actually, we only keep the console tty mode up because it was always there, 14 years or so. Um, history is sticky, is I guess the answer. When I started using cygwin (a _long_ time ago), CYGWIN=tty was the recommended setting (and isn't it still there in cygwin/cygwin.bat ?). So I have No, it's not the default, and it never was, actually. faithfully copied that into my Windows environment initialisation ever since. Is it time to remove it? I do use a windows console occasionally for pure Windows activities---what change(s) will I see? I don't quite understand, if you use the Windows console for pure Windows stuff, why do you use tty mode at all? And what do you use to run Cygwin apps? You do realize cygwin apps run just fine from the regular windows console, right? You can even invoke your favorite shell to run scripts. So if you were trying to run native windows console tools while using cygwin tools as well, this might be something you would do (for instance running a batch file or sysinternals tool or something similar and using some cygwin tool like grep). I can't speak to the cygwin=tty thing though. Many native Windows tools don't work well in tty mode anyway. For non-Cygwin tools, the default notty mode is the most compatible one. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Who's using CYGWIN=tty and why?
On 09/05/2011 12:10, Corinna Vinschen wrote: Chris and I are wondering how many people are using the Windows console as local console window in CYGWIN=tty mode and why. - I am not a Cygwin Power User, and I am not sure to understand you well. - If you talk about the console that is launched when double clicking on the Cygwin shortcut (C:\cygwin\Cygwin.bat); then, I can say that I use it every day, without any modification. This make the job well for me, because most of the time I am working the old way, editing notes, scripts and code with VIM; compiling code using Makefile and make; etc. - Since I never tried the other consoles, I can not say more about that subject. Regards, Claude -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
