Re: RFU: cppcheck-1.52-1
On Dec 10 22:31, Chris Sutcliffe wrote: Please upload: --- wget -x -nH --cut-dirs=1 \http://emergedesktop.org/cygwin/cppcheck/cppcheck-1.52-1.tar.bz2 \http://emergedesktop.org/cygwin/cppcheck/cppcheck-1.52-1-src.tar.bz2 --- Uploaded. Btw., your wget statement is broken for the thid time. The backslash at the start of the line is not very helpful :} Please leave 1.51-1 as previous and feel free to remove older releases. Done. Thanks, Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat
Re: RFU: cppcheck-1.52-1
On 12 December 2011 04:09, Corinna Vinschen wrote: On Dec 10 22:31, Chris Sutcliffe wrote: Please upload: --- wget -x -nH --cut-dirs=1 \http://emergedesktop.org/cygwin/cppcheck/cppcheck-1.52-1.tar.bz2 \http://emergedesktop.org/cygwin/cppcheck/cppcheck-1.52-1-src.tar.bz2 --- Uploaded. Btw., your wget statement is broken for the thid time. The backslash at the start of the line is not very helpful :} Ugh, sorry, it seems like the GMail web interface is messing up the spacing (it looks fine when I send it). I'll try to correct it next time. Thank you, Chris -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d
src/winsup/cygwin ChangeLog dcrt0.cc init.cc
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2011-12-12 10:16:54 Modified files: winsup/cygwin : ChangeLog dcrt0.cc init.cc Log message: * dcrt0.cc (wow64_respawn): New static variable. (wow64_started_from_native64): New function to check if a WOW64 process got started from a native 64 bit process. (respawn_wow64_process): New function to respawn process. (dll_crt0_0): When started from a native parent, check if parent is a 64 bit process. If so, return early. (_dll_crt0): Respawn WOW64 process here if required. * init.cc (respawn_wow64_process): Remove. (dll_entry): Rename wow64_test_stack_marker to test_stack_marker. Drop WOW64 test here. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.5613r2=1.5614 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/dcrt0.cc.diff?cvsroot=srcr1=1.414r2=1.415 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/init.cc.diff?cvsroot=srcr1=1.88r2=1.89
src/winsup/cygwin ChangeLog mount.cc
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2011-12-12 11:03:01 Modified files: winsup/cygwin : ChangeLog mount.cc Log message: * mount.cc (fs_info::update): Set has_buggy_reopen for Netapps as well. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.5614r2=1.5615 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/mount.cc.diff?cvsroot=srcr1=1.82r2=1.83
src/winsup/cygwin ChangeLog fhandler_process.cc
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2011-12-12 17:27:18 Modified files: winsup/cygwin : ChangeLog fhandler_process.cc Log message: * fhandler_process.cc (dos_drive_mappings::dos_drive_mappings): Fully resolve symbolic links returned by QueryDosDeviceW. Explain why. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.5615r2=1.5616 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/fhandler_process.cc.diff?cvsroot=srcr1=1.112r2=1.113
src/winsup/w32api ChangeLog Makefile.in lib/Ma ...
CVSROOT:/cvs/src Module name:src Changes by: keithmarsh...@sourceware.org2011-12-12 20:02:34 Modified files: winsup/w32api : ChangeLog Makefile.in winsup/w32api/lib: Makefile.in Log message: Correct makefile error; remove unnecessary FLAGS_TO_PASS macro Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/w32api/ChangeLog.diff?cvsroot=srcr1=1.1088r2=1.1089 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/w32api/Makefile.in.diff?cvsroot=srcr1=1.55r2=1.56 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/w32api/lib/Makefile.in.diff?cvsroot=srcr1=1.49r2=1.50
src/winsup/cygwin ChangeLog fhandler_process.cc
CVSROOT:/cvs/src Module name:src Changes by: cori...@sourceware.org 2011-12-12 21:38:08 Modified files: winsup/cygwin : ChangeLog fhandler_process.cc Log message: * fhandler_process.cc (dos_drive_mappings): Partially rewrite to handle volumes mounted into juntion points correctly. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/ChangeLog.diff?cvsroot=srcr1=1.5616r2=1.5617 http://sourceware.org/cgi-bin/cvsweb.cgi/src/winsup/cygwin/fhandler_process.cc.diff?cvsroot=srcr1=1.113r2=1.114
winsup/doc ChangeLog faq-using.xml new-feature ...
CVSROOT:/cvs/uberbaum Module name:winsup Changes by: c...@sourceware.org 2011-12-13 03:55:00 Modified files: doc: ChangeLog faq-using.xml new-features.sgml setup-net.sgml Log message: * faq-using.xml: Remove obsolete entry about the standard console window. * new-features.sgml: Remove obsolete entry which references cygwin.bat. * setup-net.sgml: Clarify new shortcut behavior for the Cygwin Terminal. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/winsup/doc/ChangeLog.diff?cvsroot=uberbaumr1=1.368r2=1.369 http://sourceware.org/cgi-bin/cvsweb.cgi/winsup/doc/faq-using.xml.diff?cvsroot=uberbaumr1=1.38r2=1.39 http://sourceware.org/cgi-bin/cvsweb.cgi/winsup/doc/new-features.sgml.diff?cvsroot=uberbaumr1=1.93r2=1.94 http://sourceware.org/cgi-bin/cvsweb.cgi/winsup/doc/setup-net.sgml.diff?cvsroot=uberbaumr1=1.27r2=1.28
[patch,1.7.10] clock_setres returns zero
Hi folks,
I actually noticed this in 1.7.9, but looking at the source in CVS I can see
it's still present in 1.7.10. Here's the STC:
$ cat clockres.c
#include stdio.h
#include time.h
#include errno.h
int main (int argc, const char **argv)
{
struct timespec ts;
if (clock_getres (CLOCK_MONOTONIC, ts) 0)
{
fprintf (stderr, Bad: %d\n, errno);
return -1;
}
printf (%ld sec, %ld nanos\n, ts.tv_sec, ts.tv_nsec);
return 0;
}
$ gcc-4 clockres.c -o clockres -W -Wall -Wextra
clockres.c: In function 'main':
clockres.c:6:15: warning: unused parameter 'argc'
clockres.c:6:34: warning: unused parameter 'argv'
$ ./clockres.exe
0 sec, 0 nanos
$
This happens because on my PC, QueryPerformanceFrequency returns 251160,
so the following code in times.cc#hires_ns::prime()
freq = (double) ((double) 10. / (double) ifreq.QuadPart);
calculates freq correctly(*) as 0.39815257206561555. This means that the
resolution is less than a nanosecond, so hires_ns::resolution(), which is
where clock_getres gets the result from, ...
LONGLONG
hires_ns::resolution ()
{
if (!inited)
prime ();
if (inited 0)
{
set_errno (ENOSYS);
return (long long) -1;
}
return (LONGLONG) freq;
}
... truncates it to zero. (The libgfortran testsuite barfs on this.)
Although the resolution is too small to express in integer nanoseconds,
that's ok when it's used to calculate the actual time, because that is all
done in double precision before being truncated to integer, in
hires_ns::nsecs() here:
// FIXME: Use round() here?
now.QuadPart = (LONGLONG) (freq * (double) (now.QuadPart -
primed_pc.QuadPart));
return now.QuadPart;
So we'll calculate the correct time to the nearest nanosecond anyway. Since
that's the maximum resolution that we can return in a timespec from
clock_gettime anyway, I think we should just round up resolutions less than
1ns to pretend they're exactly 1ns.
winsup/cygwin/ChangeLog:
* times.cc (hires_ns::resolution): Don't return less than 1.
Tested by building the clean sources, copying the DLL and test executable
into a temp dir on their own and invoking it from cmd.exe, patching the source
and rebuilding the DLL, copying the new DLL into the temp dir and rerunning
the testcase to see 0 sec, 1 nanos. Didn't do a full install though. OK?
cheers,
DaveK
--
(*) - Apart from the fact that it's a period, not a frequency!
Index: winsup/cygwin/times.cc
===
RCS file: /cvs/src/src/winsup/cygwin/times.cc,v
retrieving revision 1.112
diff -p -u -r1.112 times.cc
--- winsup/cygwin/times.cc 3 Dec 2011 21:43:27 - 1.112
+++ winsup/cygwin/times.cc 12 Dec 2011 08:23:20 -
@@ -718,7 +718,7 @@ hires_ns::resolution ()
return (long long) -1;
}
- return (LONGLONG) freq;
+ return (freq = 1.0) ? 1ll : (LONGLONG) freq;
}
UINT
Re: Latest cygwin.bat - need one
On Mon, Dec 12, 2011 at 01:13:02AM -0600, Tim McDaniel wrote: On Mon, 12 Dec 2011, Mike Brown wrote: Doing some more digging I found the following posting (via google): Does changing 'bash' to '/bin/bash' make a difference? Answering my own question: yes. There was a change in execvp()'s behaviour to no longer look up an executable in the current working directory, wasn't there? I can't find it in the ChangeLog though. You've got to be kidding. Why was the looking into CWD removed? PATH specifies the list of directories to search for executables. So if execvp() ever used . unconditionally regardless of PATH, then it violated one of the most long-standing UNIXy rules. Yes, I know all about the . security hole and have cleaned many things that used it. Even if execvp() was changed to no longer use ., it should still use the default path for system executables. Cygwin does have a default, does it not? It would seem not, otherwise the absolute path to the shell wouldn't be required. Funny thing is that the rxvt program was found. Ya, I know, Windblows found it, because it does look in the CWD. But, once rxvt was started, wouldn't the default cygwin PATH be brought in so that executables can be found? Therefore execvp() shouldn't have an issue finding system executables. So, based upon what actually happens and the user doc, it seems that at startup, cygwin is deaf, dumb and blind regarding the executables in /bin. You'd think that cygwin would at least know that when it starts. Any particular reason why cygwin can't build itself a default PATH for system executables? MB -- e-mail: vid...@vidiot.com | vid...@vidiot.net/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ | http://vidiot.net/ / \ HTML Email -- 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: [ANNOUNCEMENT] CALL FOR TESTING: Cygwin 1.7.10
On Dec 11 21:32, Samuel Thibault wrote: Corinna Vinschen, le Thu 08 Dec 2011 09:47:45 +0100, a écrit : Too bad. In that case, Samuel, can you please have a closer look to see what broke brltty? The switch to mintty, simply. Brltty uses ReadConsoleOutputCharacter() to get the text from consoles, I bet mintty does not implement this. Lars thus needs cygwin to be able to run from a standard windows console too. Lars wrote in http://cygwin.com/ml/cygwin/2011-12/msg00124.html that he always starts Cygwin from cmd.exe. 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: Another call for filesystem testing
On Dec 12 05:56, Heiko Elger wrote: Here's a test from Win7/64 SP1 with MVFS version 7.1.1.7 (Wed Aug 3 22:33:34 2011). ente59@PCFX061 /cygdrive/c/MyDevelopment/cygwin/test-qfif $ ./test- qfif.exe /cygdrive/v/Stg_V5.108_ente59_iv/stg2/steuerung /cygdrive/v/Stg_V5.108 _ente59_iv/stg2/steuerung/makefile NtQueryFullAttributesFile(\??\V:\Stg_V5.108_ente59_iv\stg2\steuerung) by name works NtQueryFullAttributesFile(\??\V:\Stg_V5.108_ente59_iv\stg2\steuerung) by handle works NtQueryFullAttributesFile(\??\V:\Stg_V5.108_ente59_iv\stg2\steuerung\makefile) by name works NtQueryFullAttributesFile(\??\V:\Stg_V5.108_ente59_iv\stg2\steuerung\makefile) by handle works Thanks David, thanks Heiko. So MVFS works fine apparently. Does anybody have access to more filesystems to run my little test? Thanks, 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: Another call for filesystem testing
XP Pro SP3 I get the following failure whether I use the current cygwin1.dll CYGWIN_NT-5.1 lunatick 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin or today's test cygwin1.dll CYGWIN_NT-5.1 lunatick 1.7.10s(0.255/5/3) 20111212 01:22:59 i686 Cygwin (as not certain what you were asking). Assume unimportant, but I have ~ mount -m none / cygdrive binary,user 0 0 so /cygdrive/q/ shorthands to /q/. Just checking, where Q: is FAT32 ~ ./test-qfif.exe /q/wrk NtQueryFullAttributesFile(\??\Q:\wrk) by name works NtQueryFullAttributesFile(\??\Q:\wrk) by handle works ~ ./test-qfif.exe /q/wrk/Wording.txt NtQueryFullAttributesFile(\??\Q:\wrk\Wording.txt) by name works NtQueryFullAttributesFile(\??\Q:\wrk\Wording.txt) by handle works all ok, as expected. BUT X: is ext2, made accessible to Windows using the software at http://www.fs-driver.org/. There is a failure as follows: ~ ./test-qfif.exe /x/wrk NtQueryFullAttributesFile(\??\X:\wrk) by name works NtQueryFullAttributesFile(\??\X:\wrk) by handle works ~ ./test-qfif.exe /x/wrk/Wording.txt NtQueryFullAttributesFile(\??\X:\wrk\Wording.txt) by name works NtQueryFullAttributesFile(\??\X:\wrk\Wording.txt) by handle failed, status code 0xc03a Fergus -- 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: Another call for filesystem testing
On Dec 12 09:57, Fergus wrote: XP Pro SP3 I get the following failure whether I use the current cygwin1.dll CYGWIN_NT-5.1 lunatick 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin or today's test cygwin1.dll CYGWIN_NT-5.1 lunatick 1.7.10s(0.255/5/3) 20111212 01:22:59 i686 Cygwin (as not certain what you were asking). The testcase only tests direct calls to native NT functions. The Cygwin version really doesn't matter. Assume unimportant, but I have ~ mount -m none / cygdrive binary,user 0 0 so /cygdrive/q/ shorthands to /q/. Just checking, where Q: is FAT32 ~ ./test-qfif.exe /q/wrk NtQueryFullAttributesFile(\??\Q:\wrk) by name works NtQueryFullAttributesFile(\??\Q:\wrk) by handle works ~ ./test-qfif.exe /q/wrk/Wording.txt NtQueryFullAttributesFile(\??\Q:\wrk\Wording.txt) by name works NtQueryFullAttributesFile(\??\Q:\wrk\Wording.txt) by handle works all ok, as expected. BUT X: is ext2, made accessible to Windows using the software at http://www.fs-driver.org/. There is a failure as follows: ~ ./test-qfif.exe /x/wrk NtQueryFullAttributesFile(\??\X:\wrk) by name works NtQueryFullAttributesFile(\??\X:\wrk) by handle works ~ ./test-qfif.exe /x/wrk/Wording.txt NtQueryFullAttributesFile(\??\X:\wrk\Wording.txt) by name works NtQueryFullAttributesFile(\??\X:\wrk\Wording.txt) by handle failed, status code 0xc03a Thanks for the test. YA driver which implements by handle operation only for directories. Oh well. Btw., can you please provide the output from /usr/lib/csih/getVolInfo /x/wrk I never saw the volume information returned by this ext2 driver yet. Thanks, 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
[ANNOUNCEMENT] Updated: cppcheck-1.52-1
Version 1.52-1 of cppcheck has been uploaded, following the upstream release. cppcheck is a tool for static C/C++ code analysis. It tries to detect bugs that your C/C++ compiler doesn't see. The goal is no false positives. cppcheck is versatile. You can check non-standard code that includes various compiler extensions, inline assembly code, etc. For a list of changes see: https://sourceforge.net/news/?group_id=195752id=305040 *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain.com at cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read*all* of the information on unsubscribing that is available starting at this URL. -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d -- 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: Another call for filesystem testing
The results for NcFsd (with NovellClient 2 SP2): $ uname -s CYGWIN_NT-6.1-WOW64 $ /usr/lib/csih/getVolInfo //OESI2/VOL_MISC1 Device Type: 7 Characteristics: 30 Volume Name: VOL_MISC1 Serial Number : 1549160268 Max Filenamelength : 255 Filesystemname : NcFsd Flags : a2 FILE_CASE_SENSITIVE_SEARCH : FALSE FILE_CASE_PRESERVED_NAMES : TRUE FILE_UNICODE_ON_DISK: FALSE FILE_PERSISTENT_ACLS: FALSE FILE_FILE_COMPRESSION : FALSE FILE_VOLUME_QUOTAS : TRUE FILE_SUPPORTS_SPARSE_FILES : FALSE FILE_SUPPORTS_REPARSE_POINTS: TRUE FILE_SUPPORTS_REMOTE_STORAGE: FALSE FILE_VOLUME_IS_COMPRESSED : FALSE FILE_SUPPORTS_OBJECT_IDS: FALSE FILE_SUPPORTS_ENCRYPTION: FALSE FILE_NAMED_STREAMS : FALSE FILE_READ_ONLY_VOLUME : FALSE FILE_SEQUENTIAL_WRITE_ONCE : FALSE FILE_SUPPORTS_TRANSACTIONS : FALSE $ ./test-qfif.exe /cygdrive/j/FRA/ /cygdrive/j/FRA/xyz.tst NtQueryFullAttributesFile(\??\J:\FRA) by name works NtQueryFullAttributesFile(\??\J:\FRA) by handle works NtQueryFullAttributesFile(\??\J:\FRA\xyz.tst) by name works NtQueryFullAttributesFile(\??\J:\FRA\xyz.tst) by handle works and for NWFS (with NovellClient 4.91 SP5 IR1 + followup patches): $ uname -s CYGWIN_NT-5.1 $ /usr/lib/csih/getVolInfo.exe //oesi2/vol_misc1 Device Type: 7 Characteristics: 30 Volume Name: VOL_MISC1 Serial Number : 167772417 Max Filenamelength : 255 Filesystemname : NWFS Flags : 2 FILE_CASE_SENSITIVE_SEARCH : FALSE FILE_CASE_PRESERVED_NAMES : TRUE FILE_UNICODE_ON_DISK: FALSE FILE_PERSISTENT_ACLS: FALSE FILE_FILE_COMPRESSION : FALSE FILE_VOLUME_QUOTAS : FALSE FILE_SUPPORTS_SPARSE_FILES : FALSE FILE_SUPPORTS_REPARSE_POINTS: FALSE FILE_SUPPORTS_REMOTE_STORAGE: FALSE FILE_VOLUME_IS_COMPRESSED : FALSE FILE_SUPPORTS_OBJECT_IDS: FALSE FILE_SUPPORTS_ENCRYPTION: FALSE FILE_NAMED_STREAMS : FALSE FILE_READ_ONLY_VOLUME : FALSE FILE_SEQUENTIAL_WRITE_ONCE : FALSE FILE_SUPPORTS_TRANSACTIONS : FALSE $ ./test-qfif.exe /cygdrive/j/FRA/ /cygdrive/j/FRA/xyz.txt NtQueryFullAttributesFile(\??\J:\FRA) by name works NtQueryFullAttributesFile(\??\J:\FRA) by handle failed, status code 0xc008 NtQueryFullAttributesFile(\??\J:\FRA\xyz.txt) by name failed, status code 0xc034 NtOpenFile(\??\J:\FRA\xyz.txt) failed, status code 0xc034 Franz. -- 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: Another call for filesystem testing
On Dec 12 14:03, Franz Sirl wrote: The results for NcFsd (with NovellClient 2 SP2): Thanks, but... NtQueryFullAttributesFile(\??\J:\FRA\xyz.tst) by name works NtQueryFullAttributesFile(\??\J:\FRA\xyz.tst) by handle works and for NWFS (with NovellClient 4.91 SP5 IR1 + followup patches): [...] NtQueryFullAttributesFile(\??\J:\FRA\xyz.txt) by name failed, status code 0xc034 NtOpenFile(\??\J:\FRA\xyz.txt) failed, status code 0xc034 This was apparently the result of a typo. The file in the NcFsd test was called xyz.tst, not xyz.txt. But it doesn't matter, I know the result for NWFS already from a private mail I got. It will be 0xc008 for by handle as well. Thanks, 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: [ANNOUNCEMENT] CALL FOR TESTING: Cygwin 1.7.10
On Dec 8 14:31, Enrico Forestieri wrote: Enrico Forestieri writes: However, I experimented a bit with the last snapshot, and even using Greek or Japanese characters in file names, lyx seems to be working fine. Sorry, it was a cursory test. Actually, cygwin_conv_path is only called for absolute paths. Using an absolute Windows path containing any nonascii character, makes lyx fail miserably. I know this is a no-no for you (even if absolute Windows paths can sneak in by opening a document created by a Windows version), so I will not insist, but knowlingly breaking backward compatibility is not nice. I'm not sure what to do here. Breaking backward compatibility is not nice, you're right, but the current behaviour really doesn't make much sense. The easiest way to handle this is to revert the change, but still... Would it be ok if it works the old way (WIN_A uses the Cygwin codeset) for applications built under 1.7.9 and earlier, and the new way (WIN_A uses Win32 ANSI/OEM codepage) for applications built under 1.7.10 and later? That means the current lyx continues to work and you can patch lyx upstream accordingly to follow the new behaviour. 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
it seems a bug inside cygwin in parsing command line with double quotes and backslashes
hi
when launching cygwin's programs from within windows's cmd
if the command line parameter has two backslashes and is double quoted (e.g. a
path to local network drive)
then inside cygwin's program the corresponding ARGV element has single
backslash only
but without double quotes all is ok - both backslashes are kept
simple testcase
C:\Documents and Settings\bdimychcmd
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimychc:\cygwin\bin\bash -c set -x; : $* --
\\blabla
+ : '\blabla'
C:\Documents and Settings\bdimychc:\cygwin\bin\bash -c set -x; : $* --
\\blabla
+ : '\\blabla'
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimychc:\Perl\bin\perl.exe -e print $ARGV[0]
\\blabla
\\blabla
C:\Documents and Settings\bdimychc:\cygwin\bin\perl.exe -e print $ARGV[0]
\\blabla
\blabla
C:\Documents and Settings\bdimychc:\cygwin\bin\perl.exe -e print $ARGV[0]
\\blabla
\\blabla
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimychc:\Ruby192\bin\ruby.exe -e print ARGV[0]
\\blabla
\\blabla
C:\Documents and Settings\bdimychc:\cygwin\bin\ruby.exe -e print ARGV[0]
\\blabla
\blabla
C:\Documents and Settings\bdimychc:\cygwin\bin\ruby.exe -e print ARGV[0]
\\blabla
\\blabla
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
it seems a bug somewhere inside cygwin libraries
PS
cygwin version
bdimych@bolshakovxp ~
$ uname -a
CYGWIN_NT-5.1 bolshakovxp 1.7.9(0.237/5/3) 2011-03-29 10:10 i686 Cygwin
PPS
whoops, tcl occured has no this bug
it has some initialization problems but the value has two backslashes
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimychecho puts $argv | c:\Tcl\bin\tclsh.exe -
\\blabla
- {\\blabla}
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimychecho puts $argv | c:\cygwin\bin\tclsh84.exe -
\\blabla
application-specific initialization failed: Can't find a usable init.tcl in the
following directories:
c:/cygwin/share/tcl8.4 c:/cygwin/share/tcl8.4 c:/cygwin/usr/share/tcl8.4
c:/share/tcl8.4 c:/cygwin/library c:/library c:/../tcl8.4.1/library
This probably means that Tcl wasn't installed properly.
- {\\blabla}
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimychecho puts $argv | c:\cygwin\bin\tclsh84.exe -
\\blabla
application-specific initialization failed: Can't find a usable init.tcl in the
following directories:
c:/cygwin/share/tcl8.4 c:/cygwin/share/tcl8.4 c:/cygwin/usr/share/tcl8.4
c:/share/tcl8.4 c:/cygwin/library c:/library c:/../tcl8.4.1/library
This probably means that Tcl wasn't installed properly.
- {\\blabla}
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
PPPS
gawk has
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimychc:\cygwin\bin\gawk.exe BEGIN {print ARGV[1]; exit}
\\blabla
\blabla
C:\Documents and Settings\bdimychc:\cygwin\bin\gawk.exe BEGIN {print ARGV[1];
exit} \\blabla
\\blabla
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
C:\Documents and Settings\bdimych
--
With best regards
Dmitry Bolshakov
--
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: Another call for filesystem testing
Btw., can you please provide the output from /usr/lib/csih/getVolInfo /x/wrk I never saw the volume information returned by this ext2 driver yet. ~ /usr/lib/csih/getVolInfo.exe /x/wrk Device Type: 7 Characteristics: 20 Volume Name: Serial Number : 2548180820 Max Filenamelength : 255 Filesystemname : Ext2 Flags : 7 FILE_CASE_SENSITIVE_SEARCH : TRUE FILE_CASE_PRESERVED_NAMES : TRUE FILE_UNICODE_ON_DISK: TRUE FILE_PERSISTENT_ACLS: FALSE FILE_FILE_COMPRESSION : FALSE FILE_VOLUME_QUOTAS : FALSE FILE_SUPPORTS_SPARSE_FILES : FALSE FILE_SUPPORTS_REPARSE_POINTS: FALSE FILE_SUPPORTS_REMOTE_STORAGE: FALSE FILE_VOLUME_IS_COMPRESSED : FALSE FILE_SUPPORTS_OBJECT_IDS: FALSE FILE_SUPPORTS_ENCRYPTION: FALSE FILE_NAMED_STREAMS : FALSE FILE_READ_ONLY_VOLUME : FALSE FILE_SEQUENTIAL_WRITE_ONCE : FALSE FILE_SUPPORTS_TRANSACTIONS : FALSE ~ -- 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: Latest cygwin.bat - need one
On 12/12/2011 1:31 AM, Mike Brown wrote: On Sun, Dec 11, 2011 at 11:48:01PM -0600, Mike Brown wrote: Suggestions for document improvement: FAQ addition to show how to modify the cygwin.bat file, or a copied file for modification, in order to be able to run rxvt to start a better terminal. This would solve the issue of users upgrading and their BAT file being broken. Be sure to explain that /bin/ is now required. Same thing with the main documention. There are pieces about starting the shell, but absolutely nothing about using a better terminal (rxvt) and how to start/configure it. Hell, why not make the use of rxvt standard in the default BAT file. The rxvt terminal is many times superior to the Windblows cmd terminal. There is no longer a default BAT file, and the Windows console is no longer the default terminal. The default terminal is now mintty. The current setup.exe creates desktop and start menu shortcuts to start it. This was announced in http://cygwin.com/ml/cygwin-announce/2011-11/msg00043.html 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: it seems a bug inside cygwin in parsing command line with double quotes and backslashes
Greetings, Dmitry Bolshakov! when launching cygwin's programs from within windows's cmd if the command line parameter has two backslashes and is double quoted (e.g. a path to local network drive) then inside cygwin's program the corresponding ARGV element has single backslash only but without double quotes all is ok - both backslashes are kept You can start right there: http://sourceware.org/ml/cygwin/2011-06/msg00246.html simple testcase Mine's simpler. -- WBR, Andrey Repin (anrdae...@freemail.ru) 12.12.2011, 21:08 Sorry for my terrible english... -- 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: Latest cygwin.bat - need one
On Mon, Dec 12, 2011 at 10:45:12AM -0500, Ken Brown wrote: There is no longer a default BAT file, and the Windows console is no longer the default terminal. The default terminal is now mintty. The current setup.exe creates desktop and start menu shortcuts to start it. This was announced in http://cygwin.com/ml/cygwin-announce/2011-11/msg00043.html From the user guide: Icons You may choose to install shortcuts on the Desktop and/or Start Menu to start a bash shell. If you prefer to use a different shell or terminal emulator such as mintty or xterm, you can use these shortcuts as a guide to creating your own. Console Programs Alternatively, the optional mintty package provides a terminal emulator similar to such X11 programs as xterm (it is not necessary to set CYGWIN=tty with mintty nor is it necessary to be running /Cygwin/X). Using mintty.exe provides the most Unix-like environment, but expect some compatibility problems with Windows programs. Overview You may wish to specify settings of several important environment variables that affect Cygwin's operation. 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; all Windows environment variables are imported when Cygwin starts. Such settings can be placed in a .bat file. An initial file is named Cygwin.bat and is created in the Cygwin root directory that you specified during setup. Note that the Cygwin option of the Start Menu points to Cygwin.bat. Edit Cygwin.bat to your liking or create your own .bat files to start Cygwin processes. From the FAQ: 4.38. Is there a better alternative to the standard console window? Yes! Use mintty instead. mintty is an optional packages in Cygwin Setup. mintty is a Cygwin application providing a native GUI without the need of X11 In other words, no where in the documentation is it stated that mintty is now the default startup. It all leans toward cygwin.bat as being the way things are started. So, just what is a user supposed to think when reading the documentation. When I did the install, I told it not to install the desktop shortcut, as I already have one. There was no indication during the install to inform the user that mintty is now the default startup, instead of cygwin.bat. At this point in time, I have no clue as to how to set up cygwin to use it, just to see what it is like. The rxvt program has been working for me. MB -- e-mail: vid...@vidiot.com | vid...@vidiot.net/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ | http://vidiot.net/ / \ HTML Email -- 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: Another call for filesystem testing
On 12/9/2011 3:35 PM, Corinna Vinschen wrote: I have a well-known problem. I just don't have all filesystems available for testing. What I need are testers for a certain, very simple functionality on any filesystem you can get hold of. I've got a variety of file systems here. netapp: Device Type: 6 Characteristics: 10 Volume Name: DFS Serial Number : 2961258662 Max Filenamelength : 255 Filesystemname : NTFS Flags : c700ff FILE_CASE_SENSITIVE_SEARCH : TRUE FILE_CASE_PRESERVED_NAMES : TRUE FILE_UNICODE_ON_DISK: TRUE FILE_PERSISTENT_ACLS: TRUE FILE_FILE_COMPRESSION : TRUE FILE_VOLUME_QUOTAS : TRUE FILE_SUPPORTS_SPARSE_FILES : TRUE FILE_SUPPORTS_REPARSE_POINTS: TRUE FILE_SUPPORTS_REMOTE_STORAGE: FALSE FILE_VOLUME_IS_COMPRESSED : FALSE FILE_SUPPORTS_OBJECT_IDS: TRUE FILE_SUPPORTS_ENCRYPTION: TRUE FILE_NAMED_STREAMS : TRUE FILE_READ_ONLY_VOLUME : FALSE FILE_SEQUENTIAL_WRITE_ONCE : FALSE FILE_SUPPORTS_TRANSACTIONS : FALSE NtQueryFullAttributesFile(\??\S:\General\AIP_IRD\Tools) by name works NtQueryFullAttributesFile(\??\S:\General\AIP_IRD\Tools) by handle works NtQueryFullAttributesFile(\??\S:\General\AIP_IRD\Tools\bin\ct_lspriv) by name works NtQueryFullAttributesFile(\??\S:\General\AIP_IRD\Tools\bin\ct_lspriv) by handle works mvfs (7.1) Device Type: 7 Characteristics: 10 Volume Name: CCase Serial Number : 36984713 Max Filenamelength : 255 Filesystemname : MVFS Flags : 3 FILE_CASE_SENSITIVE_SEARCH : TRUE FILE_CASE_PRESERVED_NAMES : TRUE FILE_UNICODE_ON_DISK: FALSE FILE_PERSISTENT_ACLS: FALSE FILE_FILE_COMPRESSION : FALSE FILE_VOLUME_QUOTAS : FALSE FILE_SUPPORTS_SPARSE_FILES : FALSE FILE_SUPPORTS_REPARSE_POINTS: FALSE FILE_SUPPORTS_REMOTE_STORAGE: FALSE FILE_VOLUME_IS_COMPRESSED : FALSE FILE_SUPPORTS_OBJECT_IDS: FALSE FILE_SUPPORTS_ENCRYPTION: FALSE FILE_NAMED_STREAMS : FALSE FILE_READ_ONLY_VOLUME : FALSE FILE_SEQUENTIAL_WRITE_ONCE : FALSE FILE_SUPPORTS_TRANSACTIONS : FALSE NtQueryFullAttributesFile(\??\M:\view\VOB\tools) by name works NtQueryFullAttributesFile(\??\M:\view\VOB\tools) by handle works NtQueryFullAttributesFile(\??\M:\view\VOB\tools\lib\python2.5\killableprocess.py) by name works NtQueryFullAttributesFile(\??\M:\view\VOB\tools\lib\python2.5\killableprocess.py) by handle works samba: Device Type: 7 Characteristics: 10 Volume Name: homeshare Serial Number : 73210969 Max Filenamelength : 255 Filesystemname : NTFS Flags : 1000f FILE_CASE_SENSITIVE_SEARCH : TRUE FILE_CASE_PRESERVED_NAMES : TRUE FILE_UNICODE_ON_DISK: TRUE FILE_PERSISTENT_ACLS: TRUE FILE_FILE_COMPRESSION : FALSE FILE_VOLUME_QUOTAS : FALSE FILE_SUPPORTS_SPARSE_FILES : FALSE FILE_SUPPORTS_REPARSE_POINTS: FALSE FILE_SUPPORTS_REMOTE_STORAGE: FALSE FILE_VOLUME_IS_COMPRESSED : FALSE FILE_SUPPORTS_OBJECT_IDS: TRUE FILE_SUPPORTS_ENCRYPTION: FALSE FILE_NAMED_STREAMS : FALSE FILE_READ_ONLY_VOLUME : FALSE FILE_SEQUENTIAL_WRITE_ONCE : FALSE FILE_SUPPORTS_TRANSACTIONS : FALSE NtQueryFullAttributesFile(\??\X:\bin) by name works NtQueryFullAttributesFile(\??\X:\bin) by handle works NtQueryFullAttributesFile(\??\X:\bin\.cshrc) by name failed, status code 0xc034 NtOpenFile(\??\X:\bin\.cshrc) failed, status code 0xc034 but that is wierd, so I checked again using a different fn: NtQueryFullAttributesFile(\??\X:\bin) by name works NtQueryFullAttributesFile(\??\X:\bin) by handle works NtQueryFullAttributesFile(\??\X:\bin\config.guess) by name works NtQueryFullAttributesFile(\??\X:\bin\config.guess) by handle works $ ls -l /x/.cshrc -rw-r--r-- 1 4.2K Nov 17 2010 /x/.cshrc $ ls -l /x/bin/config.guess -rwxr-xr-x 1 41K Jan 17 2005 /x/bin/config.guess* There's one more filesystem (another netapp flavor) I can test, but the server is down for repair today so I'll test it tomorrow. -- Chuck -- 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: Latest cygwin.bat - need one
On 12/12/2011 11:44 AM, Mike Brown wrote: snipped doc references... In other words, no where in the documentation is it stated that mintty is now the default startup. It all leans toward cygwin.bat as being the way things are started. So, just what is a user supposed to think when reading the documentation. When I did the install, I told it not to install the desktop shortcut, as I already have one. There was no indication during the install to inform the user that mintty is now the default startup, instead of cygwin.bat. Those are good points about the documentation. The change to mintty happened fairly recently though, so I'm sure the documentation will be updated sometime soon to reflect the current reality. You may be able to contribute patches for the documentation if that interests you enough. At this point in time, I have no clue as to how to set up cygwin to use it, just to see what it is like. I would try installing fresh to a new directory and taking all the defaults, from package selection to shortcut creation. Leave your current installation alone since it probably has some settings you don't want to lose or that may interfere with a fresh Cygwin experience. Once you figure out what your original installation needs, you can copy those changes over either manually or by re-running setup.exe as necessary. The rxvt program has been working for me. I used to use rxvt a long time ago, but it's dead upstream from what I last heard. Don't expect much help if it doesn't work in Cygwin. Urxvt is probably your only option if you *must* use something like rxvt for some reason. It requires X to be running though... Mintty is a big improvement over the Windows terminal and rxvt, so give it a try. If you don't let setup.exe create the shortcut for you, it's as easy as creating a shortcut that runs mintty as follows from within the bin directory of your Cygwin installation: mintty - That will start a login shell for you using the shell you have configured in /etc/passwd. From there you can configure mintty by right clicking to open a context menu and opening the the configuration dialog. You can find more documentation by reading mintty's manpage. Good luck. -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: Latest cygwin.bat - need one
On 12/12/2011 12:44 PM, Mike Brown wrote: On Mon, Dec 12, 2011 at 10:45:12AM -0500, Ken Brown wrote: There is no longer a default BAT file, and the Windows console is no longer the default terminal. The default terminal is now mintty. The current setup.exe creates desktop and start menu shortcuts to start it. This was announced in http://cygwin.com/ml/cygwin-announce/2011-11/msg00043.html [...] So, just what is a user supposed to think when reading the documentation. You're right, the documentation is out of date. I'll try to submit some patches within the next couple weeks if no one beats me to it. (Much of the documentation has already been updated in CVS.) By the way, I was wrong when I said there is no longer a default BAT file. setup.exe still creates /Cygwin.bat if it doesn't already exist. But setup.exe no longer creates a shortcut to start it. When I did the install, I told it not to install the desktop shortcut, as I already have one. There was no indication during the install to inform the user that mintty is now the default startup, instead of cygwin.bat. At this point in time, I have no clue as to how to set up cygwin to use it, just to see what it is like. The rxvt program has been working for me. There's nothing to set up. You just click on the start menu shortcut. You can then right click in the mintty window and select Options if you want to change some of the defaults. 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: Latest cygwin.bat - need one
On Mon, Dec 12, 2011 at 03:28:39PM -0500, Ken Brown wrote: There's nothing to set up. You just click on the start menu shortcut. You can then right click in the mintty window and select Options if you want to change some of the defaults. In my case that is a no go. That is because, as mentioned, I told the installer not to create the desktop shortcut or the start menu option, as I already had them. So, the start menu currently points to the BAT file. If there is an example of what the desktop shortcut has for the properties, I can create one to see what mintty looks like. I've never used mintty under Solaris or Linux. MB -- e-mail: vid...@vidiot.com | vid...@vidiot.net/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ | http://vidiot.net/ / \ HTML Email -- 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: Latest cygwin.bat - need one
On 12/12/2011 03:23 PM, Mike Brown wrote: In my case that is a no go. That is because, as mentioned, I told the installer not to create the desktop shortcut or the start menu option, as I already had them. So, the start menu currently points to the BAT file. Hmm, it seems that my messages aren't getting through since I mentioned how to create such a shortcut just a little while ago, but I'll try one more time... Create a shortcut that starts in the bin directory of your Cygwin installation. Have it run: mintty - That's it as far as I remember. Of course, the easy way is to just run setup.exe again and let it create the shortcut for you. Then you know you have the right settings. If there is an example of what the desktop shortcut has for the properties, I can create one to see what mintty looks like. I've never used mintty under Solaris or Linux. Mintty doesn't exist under Solaris or Linux, only Cygwin. -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
Documentation patches
The attached patches address some of the documentation problems mentioned in http://cygwin.com/ml/cygwin/2011-12/msg00277.html . I think the other problems have already been fixed in CVS. Ken --- faq-using.xml.orig 2011-12-08 16:42:26.0 -0500 +++ faq-using.xml 2011-12-12 16:40:59.381579400 -0500 @@ -939,16 +939,6 @@ /para /answer/qandaentry -qandaentry id=faq.using.console-window -questionparaIs there a better alternative to the standard console window?/para/question -answer - -paraYes! Use commandmintty/command instead. commandmintty/command is an optional packages in -Cygwin Setup. commandmintty/command is a Cygwin application providing a native GUI without -the need of X11. -/para -/answer/qandaentry - qandaentry id=faq.using.symlinkstoppedworking questionparaWhy do some of my old symlinks don't work anymore?/para/question answer --- new-features.sgml.orig 2011-12-08 16:42:26.0 -0500 +++ new-features.sgml 2011-12-12 16:34:16.077511700 -0500 @@ -497,14 +497,8 @@ having a valid representation of their filename in the current character set. To always have a valid string, use the UTF-8 charset by setting the environment variable $LANG, $LC_ALL, or $LC_CTYPE to a valid -POSIX value, for instance in Cygwin.bat like this: -/para - -screen -set LC_CTYPE=en_US.UTF-8 -/screen - -/listitem +POSIX value, such as en_US.UTF-8. +/para/listitem listitempara PATH_MAX is now 4096. Internally, path names can be as long as the --- setup-net.sgml.orig 2011-08-04 15:11:43.0 -0400 +++ setup-net.sgml 2011-12-12 16:06:51.929471800 -0500 @@ -223,13 +223,12 @@ /para /sect2 -sect2 id=setup-iconstitleIcons/title +sect2 id=setup-iconstitleShortcuts/title para -You may choose to install shortcuts on the Desktop and/or Start Menu -to start a literalbash/literal shell. If you prefer to use a different -shell or terminal emulator such as literalmintty/literal or -literalxterm/literal, you can use these shortcuts as a guide to -creating your own. +You may choose to install Cygwin Terminal shortcuts on the Desktop +and/or Start Menu. These shortcuts run commandmintty/command, +which will start your default shell as specified +in filename/etc/passwd/filename. /para /sect2 -- 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: [ANNOUNCEMENT] CALL FOR TESTING: Cygwin 1.7.10
Corinna Vinschen writes: Would it be ok if it works the old way (WIN_A uses the Cygwin codeset) for applications built under 1.7.9 and earlier, and the new way (WIN_A uses Win32 ANSI/OEM codepage) for applications built under 1.7.10 and later? That means the current lyx continues to work and you can patch lyx upstream accordingly to follow the new behaviour. This would certainly preserve backward compatibility, so it is Ok. However, may I suggest to add two other enums, namely, CCP_WIN_TO_POSIX and CCP_POSIX_TO_WIN, that preserve encoding? This is also useful, as not always one has to convert to/from Windows style paths for calling native APIs. Thanks, -- Enrico -- 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: Latest cygwin.bat - need one
On 2011-12-12, Jeremy Bopp wrote: On 12/12/2011 03:23 PM, Mike Brown wrote: In my case that is a no go. That is because, as mentioned, I told the installer not to create the desktop shortcut or the start menu option, as I already had them. So, the start menu currently points to the BAT file. Hmm, it seems that my messages aren't getting through since I mentioned how to create such a shortcut just a little while ago, but I'll try one more time... Create a shortcut that starts in the bin directory of your Cygwin installation. Have it run: mintty - That's it as far as I remember. Of course, the easy way is to just run setup.exe again and let it create the shortcut for you. Then you know you have the right settings. I just ran the new setup.exe a few weeks ago and haven't changed the new Cygwin Terminal shortcut's properties. These are the most important ones. General [Name:] Cygwin Terminal Shortcut Target: C:\cygwin\bin\mintty.exe -i /Cygwin-Terminal.ico - Start in: [empty] Shortcut key: None Run: Normal window [Icon:] C:\cygwin\Cygwin-Termina.ico HTH, Gary -- 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: Latest cygwin.bat - need one
On Mon, Dec 12, 2011 at 04:11:48PM -0800, Gary Johnson wrote: General [Name:] Cygwin Terminal Shortcut Target: C:\cygwin\bin\mintty.exe -i /Cygwin-Terminal.ico - Start in: [empty] Shortcut key: None Run: Normal window [Icon:] C:\cygwin\Cygwin-Termina.ico Thanks, I created a shortcut with the above info and it is close. It starts and it finds my shell and my config files. But $SHELL is empty and the terminal has no clue as to where any of the Cygwin programs are. The PATH that is created before any of my files are read contains info on Windblows program locations, but nowhere is /usr/bin or /bin, or any of the long path names to the Cygwin binaries. When started from the cygwin.bat file, /usr/local/bin:/usr/bin:/bin: prefice the Windblows paths. So, a PATH that includes the needed info to the cygwin binaries is built when BAT is run, but not when mintty is started. Is there a reason why Cygwin is not building a PATH with the needed info? I've modified my environment resource file to look for $TERM == xterm and added the needed Cygwin paths. BTW, what is with white text on a black background? UGGHH! :-) MB -- e-mail: vid...@vidiot.com | vid...@vidiot.net/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ | http://vidiot.net/ / \ HTML Email -- 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: mintty
On Mon, Dec 12, 2011 at 07:37:46PM -0600, Mike Brown wrote: Is there a reason why Cygwin is not building a PATH with the needed info? Not only that, it doesn't start out in the user's home directory. MB -- e-mail: vid...@vidiot.com | vid...@vidiot.net/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ | http://vidiot.net/ / \ HTML Email -- 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: Latest cygwin.bat - need one
[Sorry, I again accidentally replied to the OP instead of to the list.] On 12/12/2011 8:37 PM, Mike Brown wrote: On Mon, Dec 12, 2011 at 04:11:48PM -0800, Gary Johnson wrote: General [Name:] Cygwin Terminal Shortcut Target: C:\cygwin\bin\mintty.exe -i /Cygwin-Terminal.ico - Start in: [empty] Shortcut key: None Run: Normal window [Icon:] C:\cygwin\Cygwin-Termina.ico Thanks, I created a shortcut with the above info and it is close. It starts and it finds my shell and my config files. But $SHELL is empty and the terminal has no clue as to where any of the Cygwin programs are. The PATH that is created before any of my files are read contains info on Windblows program locations, but nowhere is /usr/bin or /bin, or any of the long path names to the Cygwin binaries. When started from the cygwin.bat file, /usr/local/bin:/usr/bin:/bin: prefice the Windblows paths. So, a PATH that includes the needed info to the cygwin binaries is built when BAT is run, but not when mintty is started. Is there a reason why Cygwin is not building a PATH with the needed info? Are you sure you didn't forget the `-' at the end of the target? That's what tells mintty to start your shell as a login shell, in which case the commands in /etc/profile should get executed. One of the commands in the default /etc/profile adds /usr/local/bin and /usr/bin to PATH. Have you modified /etc/profile? 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: Latest cygwin.bat - need one
On 12/12/2011 07:37 PM, Mike Brown wrote: On Mon, Dec 12, 2011 at 04:11:48PM -0800, Gary Johnson wrote: General [Name:] Cygwin Terminal Shortcut Target: C:\cygwin\bin\mintty.exe -i /Cygwin-Terminal.ico - Start in: [empty] Shortcut key: None Run: Normal window [Icon:] C:\cygwin\Cygwin-Termina.ico Thanks, I created a shortcut with the above info and it is close. It starts and it finds my shell and my config files. But $SHELL is empty and the terminal has no clue as to where any of the Cygwin programs are. The PATH that is created before any of my files are read contains info on Windblows program locations, but nowhere is /usr/bin or /bin, or any of the long path names to the Cygwin binaries. When started from the cygwin.bat file, /usr/local/bin:/usr/bin:/bin: prefice the Windblows paths. So, a PATH that includes the needed info to the cygwin binaries is built when BAT is run, but not when mintty is started. Is there a reason why Cygwin is not building a PATH with the needed info? As I recall, all of the PATH settings are handled in /etc/profile and files in /etc/profile.d. It sounds like you have a problem somewhere in there. Maybe you made local changes that prevented the package that provides /etc/profile from updating it when you upgraded Cygwin. Try installing a fresh instance of Cygwin to a different directory and see if things behave better there. You can leave your current installation where it is without much risk of interference, assuming your shell startup scripts don't have any hard coded paths to the original location. I've modified my environment resource file to look for $TERM == xterm and added the needed Cygwin paths. That shouldn't be necessary once you get the real problem sorted out. BTW, what is with white text on a black background? UGGHH! :-) To each his own. Hopefully, you found all the configuration options so that you can change it as you please. :-) -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: Documentation patches (gold star)
On Mon, Dec 12, 2011 at 04:57:10PM -0500, Ken Brown wrote: The attached patches address some of the documentation problems mentioned in http://cygwin.com/ml/cygwin/2011-12/msg00277.html . I think the other problems have already been fixed in CVS. Patch applied along with a ChangeLog. Thanks very much for being proactive about this. It's much appreciated. Gold star please? 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: Latest cygwin.bat - need one
On Mon, Dec 12, 2011 at 10:07:23PM -0500, Ken Brown wrote: [Sorry, I again accidentally replied to the OP instead of to the list.] Easy to do the way this mail list is set up. Are you sure you didn't forget the `-' at the end of the target? That's what tells mintty to start your shell as a login shell, in which case the commands in /etc/profile should get executed. One of the commands in the default /etc/profile adds /usr/local/bin and /usr/bin to PATH. Have you modified /etc/profile? Oops, the cut-n-paste missed the '-' at the end. All is well now. Got the other stuff set up as well, like getting rid of the white on black :-) Thanks. All that is left is ssh :-( MB -- e-mail: vid...@vidiot.com | vid...@vidiot.net/~\ The ASCII [I've been to Earth. I know where it is. ] \ / Ribbon Campaign [And I'm gonna take us there.Starbuck 3/25/07] X Against Visit - URL: http://vidiot.com/ | http://vidiot.net/ / \ HTML Email -- 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: SIGHUP on pty closure
On Mon, Jul 25, 2011 at 07:27:23PM +0200, Marco Atzeri wrote: On 25/07/2011 19.05, Christopher Faylor wrote: sleeping and waiting for signal would mean that bash is not waiting for input. If bash isn't waiting for input that would explain the problem. However, I would expect that bash, in this scenario, to be waiting for input. I was hoping you'd provide insight into whether that was the case or not. cgf Sorry, I will try to be more clear, for what I understood of mc. With CTRL-O the foreground is switched between mc and bash (or viceversa) , so when mc is on foreground bash is not waiting for input, but for a signal to wake up again. Mc exits following F10 key press and bash should follow when it receives SIGHUP. I tracked down a place where SIGHUP was not getting sent correctly so I may have fixed this in recent snapshots. No guarantees though. 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
Updated: cppcheck-1.52-1
Version 1.52-1 of cppcheck has been uploaded, following the upstream release. cppcheck is a tool for static C/C++ code analysis. It tries to detect bugs that your C/C++ compiler doesn't see. The goal is no false positives. cppcheck is versatile. You can check non-standard code that includes various compiler extensions, inline assembly code, etc. For a list of changes see: https://sourceforge.net/news/?group_id=195752id=305040 *** CYGWIN-ANNOUNCE UNSUBSCRIBE INFO *** If you want to unsubscribe from the cygwin-announce mailing list, look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-announce-unsubscribe-you=yourdomain.com at cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read*all* of the information on unsubscribing that is available starting at this URL. -- Chris Sutcliffe http://emergedesktop.org http://www.google.com/profiles/ir0nh34d
