Re: Segfault under cygwin 1.7.62

2009/10/9 Stephen J. Turnbull: > > Hang on, there is a problem with this one: Cygwin doesn't like the > > \001's and the tab at the end. > > Well, I'll be damned. I was betting on this being 100% an XEmacs bug, > but I could lose! :-) I don't think you've got anything to worry about there. ;)

Re: Segfault under cygwin 1.7.62

2009/10/9 Vin Shelton: >>  > #3  0x005151bc in Lstream_really_write (lstr=0x176ea00, >>  >     data=0x148d0c0 >>  > >> "c;C:\\cygwin\\cygwin\\tmp\\s360339.aoa\\ï\202\201Ð\201Ð\201Ð\201ï\203\22002ABFxi-string)g)Àâw\001\200ÑH\001Â\200\t", Hang on, there is a problem with this one: Cygwin doesn't li

Re: Segfault under cygwin 1.7.62

2009/10/9 Vin Shelton: >> > #9 0x0056d4d7 in qxe_realpath (path=0x22248c "", >> > resolved_path=0x22651c >> > "c:/cygwin/tmp/s360339.aoa/\201Ð\201Ð\201Ð\201Ð02ABFx", >> > links_only=0) at >> > #8 0x0056cd68 in readlink_or_correct_case (name=, >> > buf=0x21e464 >> > >> "/tmp/s

Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-62

2009/10/7 Charles Wilson: > (On Vista, you can use SetConsoleScreenBufferEx -- which is supposedly > "documented" but I couldn't find any). There's a 'SetConsoleScreenBufferInfoEx'. But another one looks more interesting: 'SetCurrentConsoleFontEx' (also ≥Vista). Andy -- Problem reports: ht

Re: [ANNOUNCEMENT] [1.7] Updated: cygwin-1.7.0-62

2009/10/6 Ken Brown: > I've tried to view the attached file (extracted from the output of fc-list) > in various ways, and here's what I've found (running XP in the U.S., with no > language-related customization): > >  - Using emacs under X, emacs recognizes the file as UTF-8 and displays the > fore

Re: snapshot 20091002 and xterm crash

2009/10/2 Corinna Vinschen: > > [Ping Yaakov] > > > On Oct  2 09:04, Marco Atzeri wrote: >> Hi, >> >> xterm abort when run in snapshot 20091002 >> reverting to 20090924 solve the issue. >> >> Run as: >> DISPLAY=127.0.0.1:0.0 xterm  -ls /usr/bin/bash.exe > > I can reproduce that.  I found the proble

Re: fc-list does not list windows system fonts under cygwin

2009/10/1 Ken Brown: > I'm cc-ing the cygwin-xfree list, which is where I think fontconfig > questions belong.  I can confirm that on my system, fc-list produces strange > output on the windows system fonts.  I'm not sure if it's the same problem > you were reporting. > > For example, I get the fol

Re: Cygwin 1.7 & mintty error - cannot run mintty more than once at a time

2009/9/30 David Antliff: >> From http://cygwin.com/problems.html: "Run 'cygcheck -s -v -r >>>cygcheck.out' and include that file as an attachment in your report. > > Done, although I've manually stripped out some company-specific info > I'd rather not publish on the Internet. Good idea. >> Also,

Re: Cygwin 1.7 & mintty error - cannot run mintty more than once at a time

2009/9/29 David Antliff: > I've been using Cygwin 1.7 alongside Cygwin 1.5 quite happily for the > last few hours, however all-of-a-sudden when I try and run mintty > (from cygstart or from a cmd.exe shell) I get a new window with this > error message: > > Failed to create child process: No such fi

Re: The C locale

2009/9/28 Corinna Vinschen >> My conclusion is as follows as a result of hearing other Japanese >> people's opinion: >> >> LANG=ja -> UTF-8 >> LANG=ja_JP -> UTF-8 >> >> Because, we specify "eucJP" explicitly when we need it. > > Hmm. > > That's an interesting point. > > In theory this sounds like a

Re: The C locale

2009/9/29 wynfield: > > Though I'm not an up on the details involved here, I will give > you feedback to the request for information about the locale issue, because > it affects the quick accessability and usage of Japanese language documents. > > Either of the two follow values would be acceptabl

Re: [1.7] "clear" missing?

2009/9/23 Larry Hall: > On 09/23/2009 12:40 PM, Gustavo Seabra wrote: >> >> Hi, >> >> I just finished a new install of cygwin-1.7. It seems to be working >> fine now, but the "clear" command seems to be missing: >> >> $ clear >> bash: clear: command not found >> >> Is this expected? Was I supposed

Re: [1.7] Invalid UTF8 while creating a file -> cannot delete?

2009/9/23 Corinna Vinschen: > I have a local patch ready to use the ANSI codepage by default in the > "C" locale.  It appears to work nicely and has the additional positive > side effect to simplify the code in a few places. > > If I only new that eastern language users could happily live with > th

Re: The C locale

2009/9/23 Lapo Luchini: >> Works for me, too. Maybe not only the codepage but also the GUI locale >> settings are involved. This is on Windows 7. > > Oh, that's interesting, it may be they improved the console in Win7? > Did you see only the euro or also the Japanese character? > > Uh, nope. I stil

Re: [1.7] Invalid UTF8 while creating a file -> cannot delete?

2009/9/22 Corinna Vinschen: >> >> Therefore, when converting a UTF-16 Windows filename to the current >> >> charset, 0xDC?? words should be treated like any other UTF-16 word >> >> that can't be represented in the current charset: it should be encoded >> >> as a ^N sequence. (I started writing thi

Re: how to let cygwin does not mount /bin /usr/bin automaticlly?

2009/9/22 ︶ㄣ無名氏: > Thanks. I want to know how to change this configuration. > > I do as follows: > > bash-3.2$ /bin/umount /usr/bin > umount: /usr/bin: Operation not permitted > > but i does not work. Any idea? /etc/fstab -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: [1.7] Invalid UTF8 while creating a file -> cannot delete?

2009/9/22 Corinna Vinschen: >> > As you might know, invalid bytes >= 0x80 are translated to UTF-16 by >> > transposing them into the 0xdc00 - 0xdcff range by just or'ing 0xdc00. >> > The problem now is that readdir() will return the transposed characters >> > as if they are the original characters.

Re: The C locale

2009/9/22 Lapo Luchini: >> For example, a Windows filename "bäh" turns into "bŤh" in the C locale, >> while it shows up correctly with explicitly set ISO-8859-1 or CP1252. > > Uh? Doesn't seem so to me: if I create "bäh" in WindowsExplorer, then > open up an UTF-8 mintty console I have a consisten

Re: The C locale

2009/9/22 Lapo Luchini: > On a second reading, I guess you meant that *ONLY for LANG=C* and leave > the current usage for LANG=xx_XX.UTF-8, is that so? Yes, this thread is solely about the C locale. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygw

Re: The C locale

2009/9/22 Lapo Luchini: > Andy Koppe wrote: >> This way, the non-ASCII needs of most users are covered >> out-of-the-box [...] >> Windows filenames show up correctly in Cygwin as long as they're >> limited to the ANSI codepage. > > I fail to see how that is a

Re: The C locale

2009/9/21 Corinna Vinschen: > Back from vacation I re-read this thread now and I have to say I just > don't know what is the best course of action here. I'm afraid I can only reiterate what I said previously. Let's use the Windows "ANSI" codepage as the character set for the C locale, for both th

Re: [1.7] Invalid UTF8 while creating a file -> cannot delete?

2009/9/21 Corinna Vinschen: >> % cat t.c >> int main() { >>     fopen("a-\xF6\xE4\xFC\xDF", "w"); //ISO-8859-1 >>     fopen("b-\xF6\xE4\xFC\xDFz", "w"); >>     fopen("c-\xF6\xE4\xFC\xDFzz", "w"); >>     fopen("d-\xF6\xE4\xFC\xDFzzz", "w"); >>     fopen("e-\xF6\xE4\xFC\xDF\xF6\xE4\xFC\xDF", "w"); >>

incorrect getpagesize() signature

/usr/include/sys/unistd.h: size_t _EXFUN(getpagesize, (void)); POSIX: int getpagesize(void); -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#uns

Re: cygdrive prefix

2009/9/17 Christopher Faylor: >>My real gripe is with setup telling me off about putting Cygwin in the >>root dir ON EVERY SINGLE UPDATE. > > My real gripe is people who COMPLAIN ABOUT FREE SOFTWARE where they > HAVE THE SOURCE CODE. Ah, that old lazy chestnut. Feedback not welcome. At least get a

Re: cygdrive prefix

2009/9/16 Dave Korn: >> whatever) prefixes when accessing stuff from the other side of the >> fence. > >  Never mind the fence, what colour are we going to paint the bikeshed? > >  This is purely a matter of taste. Exactly. I didn't mean to suggest that Cygwin should go into C:\ by default. And ye

Re: cygdrive prefix

2009/9/16 Thorsten Kampe > you shouldn't install Cygwin > directly to C:\ (but to C:\cygwin): so you don't have the Cygwin and the > Windows root folder structure mixed. And where exactly is the harm in that? Apple certainly don't see a problem with it, with the likes of /Applications and /Users l

Re: GNU screen 4.0.3-1 -- Spawns a screen.exe cmd window when launched

2009/9/14 Joel Eidsath: > When I launch screen by typing 'screen' at the basic Cygwin bash prompt, a > screen.exe cmd window launches and stays open for the entire screen session. > > I only see this behavior with Windows 7. Cygwin 1.7 has a workaround for the Windows 7 bug that causes this. It wo

Re: Cygwin 1.7 message queues - permission denied error still exists

2009/9/13 Philip Semanchuk: > I also ran 'uname -srv' didn't contain anything > that looked like a relevant version number. uname -r normally does the job: $ uname -r 1.7.0(0.212/5/3) Unfortunately that doesn't contain the package release number used to differentiate the beta releases, which is

Re: cygwin Digest 10 Sep 2009 16:45:51 -0000 Issue 6623

2009/9/11 Kit Johnson: > I've just upgraded to the beta version (1.7.0). > This is now in my cygwin.bat file (definitely > for the correct, beta, installation): > @echo off > > C: > chdir C:\cyg\bin > set LANG=th_TH.UTF-8 > bash --login -i > > And these lines in my .bashrc file (also definitely the

Re: [1.7] Invalid UTF8 while creating a file -> cannot delete?

2009/9/10 Lapo Luchini: > But the real problem with that test is not really what shows and how, > the biggest problem is that it seems that filenames created with a > "wrong" filename are quite limited in usage and can't seemingly be deleted. > > % export LANG=en_EN.UTF-8 > % cat t.c > #include >

Re: Help needed getting unicode working in bash

2009/9/10 Kit Johnson: > Thanks so much for taking the time to help.  This is the first time I've > used a mailing list so I hope I've replied correctly. Yep, except you replied to me instead of the list. ;) > I understand charactersets and locales better now.  I followed your > recommendations

Re: Help needed getting unicode working in bash

2009/9/9 Kit Johnson: > I'm just getting started with cygwin and really enjoying the linux-like > functionality under windows.  I have one major problem which is displaying > unicode filenames in bash. > > To be specific about my problem, I do not need to type unicode under bash, I > simply want to

Re: Distinguishing between XP / Vista / 7

2009/9/9 Fergus: > Now I find I need to distinguish between Vista and 7 but uname does not > provide a discriminant (CYGWIN_NT-6.1 in both cases, I think?). Vista is 6.0. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation:

Re: The C locale

ps: > Maximum 1.5 compatibility (what for and how long?) vs. maximum > default usability in the long run (at least I hope so). Compatibilty for users upgrading to 1.7, who are used to being able to use the non-ASCII chars in their ANSI codepage, which is usually all they care about. And who have

Re: The C locale

2009/9/8 Corinna Vinschen: >> Which leaves one apparently good solution for the "C" locale: >> >> - Use the default Windows codepage for filenames, console, and >> >> multibyte functions. This is what happens already if you specifiy a >> >> locale with a language but no charset, e.g. "en". Maximum

Re: The C locale

2009/9/2 IWAMURO Motonori: > I want to use UTF-8 throughout. > Because: > - a lot of UNIX tools using network (e.g. rsync, scp, ...) treat the > file name as 8bit byte array. > - default locale of modern UNIX based OS is *.UTF-8. > - The file with the filename including the character outside the >

Re: How to deploy Application compiled with QT3 in Cygwin to Windows?

2009/9/7 Pok Wilson: > Thanks for your information. How can I "make a Windows application and > user/link the Windows version of QT3"? That's not a Cygwin question and this isn't a QT support forum. > I tried to compile the same piece of code in Windows version of QT4. But I > cant compare as s

mintty 0.5-beta2

Just a quick note to say that mintty 0.5-beta2 is available for testing from http://mintty.googlecode.com. There are separate versions for Cygwin 1.5 and 1.7, whereby only the 1.7 version takes full advantage of 1.7's locale and charset support. Full announcement on the mintty discussion group, at

Re: Norton Antivirus 2010 false detects cygpath.exe, mkpasswd.exe, mkgroup.exe

2009/9/4 Robert Pendell: > During basic installation cygpath, mkpasswd, and mkgroup were all > detected by SONAR (part of NAV 2010) that it the files emitted > suspicious activiry and would be removed.  The files have not been > removed (yet) but I will be alerting Norton to this.  This does block

website

On cygwin.com: "If nothing goes overly wrong, the official 1.7.1 release goes public still within the the first half of 2009." Not sure that anything has gone overly wrong, but that sentence could do with an update. Andy -- Problem reports: http://cygwin.com/problems.html FAQ:

Re: The C locale

Eric Blake: >> A rather important exception is 'ls', which seems to have its own >> hardcoded limitation to 7 bits for the C locale: anything non-ASCII is >> shown as '? there'. > > That's only because the current build of cygwin ls pre-dates a lot of the > locale support.  I'm hoping that when I g

Re: The C locale

Christopher Faylor: >Andy Koppe: >>Trying to reply to [banned]'s post about locale issues, I got >>rather confused about the C locale. The manual and the POSIX standard >>say that it supports ASCII only, so in theory anything above 0x7F >>should be rejected. In prac

Re: [ANNOUNCEMENT] Updated: screen, now with 256-color support!

> 'term screen-256color' sets TERM=screen-256color in the > environment of programs running inside screen, hence any program or > script that recognises "screen" but not "screen-256color" will no > longer work as expected. Btw, a different approach to enabling 256 colour support by default, which

Re: [ANNOUNCEMENT] Updated: screen, now with 256-color support!

Andrew Schulman: Instead of specifying -T screen-256color every time, one can just put 'term screen-256color' into .screenrc.  I'll update the docs to show this when I make the release current. >>> >>> Is there any reason that I shouldn't put this command into the default >>> /etc/sc

Re: [ANNOUNCEMENT] Updated: screen, now with 256-color support!

Andrew Schulman: >> > TERM=xterm-256color screen -T screen-256color >> >> Instead of specifying -T screen-256color every time, one can just put >> 'term screen-256color' into .screenrc.  I'll update the docs to show this >> when I make the release current. > > Is there any reason that I shouldn't p

Re: [ANNOUNCEMENT] Updated: screen, now with 256-color support!

Andrew Schulman: > Instructions for starting screen with 256 color support are in > /usr/share/doc/screen/README.Cygwin.  In brief, you have to invoke screen > as > > TERM=screen-256color screen I don't think that's quite right. Screen needs to be told what terminal it is itself running in. This m

Re: mintty doesn't run on NT4 due to lack of GetConsoleWindow

Christopher Faylor: > I spent much of the day trying to resurrect my Windows NT4 system and > now that I finall have it back, I just tried to run mintty and noticed > that it seems to be using GetConsoleWindow.  That's not allowed on NT4. > I get an error that says: > > "The procedure entry point G

Re: default encoding (was: Re: GNU screen hangs)

Tuomo Valkonen: > I have LC_CTYPE=en_US.UTF-8, of course. And still Xlib fails. Oh well. Someone more knowledgeable about X will need to step in here. > I think the Python interpreter should call setlocale, > instead of having Python programs themselves do it, > because it is half-an-OS and does

default encoding (was: Re: GNU screen hangs)

Tuomo Valkonen: > Firstly Xlib/libc communication seems to be > broken/unimplemented. This has frequently been a > problem on Linux too, Xlib not being aware of libc > locales. (Xlib usually won't work without the .encoding > part in LC_CTYPE, which frequently isn't there, as > libc seemingly can g

The C locale

Trying to reply to Tuomo Valkonen's post about locale issues, I got rather confused about the C locale. The manual and the POSIX standard say that it supports ASCII only, so in theory anything above 0x7F should be rejected. In practice though, both Cygwin 1.5 and 1.7 do support characters above 0x7

Re: GNU screen hangs

2009/8/29 Tuomo Valkonen: > Cygwin (1.7 -- 1.5 is useless due to non-existent > locale/UTF-8 support, although 1.7 doesn't shine in > that either) Any specific problems regarding the latter? Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/f

Re: Adding packages (was: mkfs.jffs2 support in CYGWIN)

Larry Hall: > Adding a link to shouldn't be allot of work > and may help if the menu was properly named. Good idea. I'll throw a name into the ring: "Cygwin package manager". > Beyond that requires significant changes to 'setup.exe' What would be needed beyond the p

Adding packages (was: mkfs.jffs2 support in CYGWIN)

> How to install is here: > http://cygwin.com/cygwin-ug-net/setup-net.html I don't think it's terribly obvious that you simply need to run setup.exe again to add more packages after initial installation. This is not a common thing to do with other installers, and with some installers this might ev

Re: mintty and readline mapping

Vince Rice: > I'm trying to map ctrl-tab in mintty and can't seem to get it working. I've > Googled bash and key bindings, key mapping, etc., but haven't found anything > that helps with the problem. How about the mintty manual? > I'm trying to bind ctrl-tab to reverse-menu-complete. There's

Re: Changing HOME for PERL

> I installed Cygwin yesterday and when I run it and look at "pwd" my path > is set to:   /cygdrive/h > > I read the FAQ and when I type "set HOME" from a Windows CLI, it is set > to: > HOME=H:\ > > I am using Cygwin for PERL. > > I just took a PERL course and in class Cygwin was configured for: >

Re: 256 color terminal in basic (non-"X Windows") Cygwin

> 2009/8/25 Gwen Morse: >> I use a game client called Tinyfugue that can make use of ANSI 256 color >> codes. >> >> I've been running in mental circles trying to find (or patch and >> compile) a terminal that will support 256 under regular cygwin. I >> can't use XWindows because I often run my cli

Re: 256 color terminal in basic (non-"X Windows") Cygwin

2009/8/25 Gwen Morse: > I use a game client called Tinyfugue that can make use of ANSI 256 color > codes. > > I've been running in mental circles trying to find (or patch and > compile) a terminal that will support 256 under regular cygwin. I > can't use XWindows because I often run my client off

Re: mintty doesn't run on NT4 due to lack of GetConsoleWindow

2009/8/6 Christopher Faylor: >>> I spent much of the day trying to resurrect my Windows NT4 system and >>> now that I finall have it back, I just tried to run mintty and noticed >>> that it seems to be using GetConsoleWindow. ??That's not allowed on NT4. >>> I get an error that says: >>> >>> "The p

Re: KOI8

Corinna Vinschen: >> > Anyway, to help support them, the attached patch adds the KOI8 >> > charsets to newlib's Unicode conversion and ctype tables. I took the >> > conversion tables from iconv and adapted the ctype tables from the >> > CP1251 version. Since KOI8 has printable characters in the C1

KOI8

One fairly important character encoding not yet supported by Cygwin 1.7 is KOI8. Well, two actually, because there are slightly different versions for Russian and Ukrainian: KOI8-R and KOI8-U, aka Windows codepages 20866 and 21866. Apparently they're de-facto standards for Unix machines and the in

MinTTY & PuTTYcyg (was: Re: rxvt slow to get the prompt ...)

2009/8/15 Morgan Gangwere: > I realize MinTTY is a fork of PuTTYCyg It's not. It's a much modified fork of PuTTY's terminal emulation and Windows frontend parts, but it uses a different approach from PuTTYcyg for connecting to Cygwin. PuTTYcyg invokes a separate helper process that links to the Cy

Re: rxvt slow to get the prompt if another rxvt is already open on windows 7 64bit

2009/8/14 Corinna Vinschen: >> I tried it again briefly last night. It only happened when logged in >> as an administrator, not as a limited user. That's with UAC enabled. >> Didn't try disabling. Reproduced both with 'rxvt' and 'mintty -u', and >> timed the delay to about 15 seconds. >> >> Trying

Re: [ANNOUNCEMENT] Updated: run-1.1.11-1

2009/8/15 Corinna Vinschen: > Apparently `run XWin' doesn't work at all anymore, everything else seems > to work fine. A shortcut starting XWin directly w/o run works fine as well. XWin is a GUI subsystem program, hence it doesn't need 'run'. (But of course it ought to work anyway.) Andy -- Prob

Re: rxvt slow to get the prompt if another rxvt is already open on windows 7 64bit

2009/8/13 Corinna Vinschen: > I just tried that on W7 and W7 64.  I can't reproduce any specific > slowness starting with he second invocation of rxvt, incuding writing > the utmp entry.  The startup time is always the same, roughly a second, > regardless of the number of already open rxvt windows.

Re: rxvt slow to get the prompt if another rxvt is already open on windows 7 64bit

2009/8/12: > I have been using for long time cygwin on WinXP Prof 32bit and the > terminal I always use is the rxvt. Everything has always worked properly. > Now I will get a new PC and I am thinking to switch to windows 7 64bit > (the official release just released some days ago), so I am doing so

Re: version about gcc on cygwin

2009/8/11 loody: > Dear all: > When checking the devel list of cygwin install, I find the version of > gcc is 3.4. > Is this the latest or I see the wrong page? There are separate 'gcc4' packages, which are at 4.3.2. Andy -- Problem reports: http://cygwin.com/problems.html FAQ:

UTF-16 surrogate macros

w32api/winnls.h is lacking the macros for recognising UTF-16 surrogates: IS_HIGH_SURROGATE, IS_LOW_SURROGATE, IS_SURROGATE_PAIR. Here's one way to define them, which avoids evaluating the characters twice: #define IS_HIGH_SURROGATE(c) (((c) & 0xFC00) == 0xD800) #define IS_LOW_SURROGATE(c) (((c) &

Re: converting to wide characters

2009/8/8 Tony Lewis: > According to the documentation, passing an empty string to iconv denotes > locale dependent character encoding. This leads me to conclude that by > default on cygwin: > > cd = iconv_open("UTF-16LE", ""); > > should produce the same encodings as: > > cd = iconv_open("UTF-16LE"

Re: mintty doesn't run on NT4 due to lack of GetConsoleWindow

2009/8/6 Christopher Faylor: > I spent much of the day trying to resurrect my Windows NT4 system and > now that I finall have it back, I just tried to run mintty and noticed > that it seems to be using GetConsoleWindow.  That's not allowed on NT4. > I get an error that says: > > "The procedure entr

_setlocale_r

_setlocale_r isn't really reentrant, is it? It invokes loadlocale(), which writes to the global function pointers __mbtowc and __wctomb, i.e. there's a single global locale setting. Its man page needs to be corrected: `_localeconv_r' and `_setlocale_r' are reentrant versions of

Re: black console boxes still a problem for Windows 7 and X?

2009/8/4 Christopher Faylor: > I just noticed one of those annoying black boxes when running X on > Windows 7.  I don't think I ever tried to run X there before. > > The first release of Cygwin which was supposed to fix this problem > was 1.7.0-51 but I can't even run X with that version. > > Have

Re: [1.7] bash loop and mintty hung issue

2009/8/2 ERIC HO: > Hi Andy, FYI. I have tested  out on my Linux machine running bash 3.2.48 > (instead of 3.2.49 as on cygwin). I don't have this problem with bash under > xterm with set -o vi and pressing shift PF key. Does this problem happen to > you with set -o vi and pressing shift PF key

Re: Mismatch cygwin1.dll

2009/8/2 Paul McFerrin: > Yes, it seams weird.  I'm checking the Version # being extracted from the > DLL itself since I can't find any other way to get it. $ uname -r 1.7.0(0.212/5/3) Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Do

Re: [1.7] bash loop and mintty hung issue

2009/8/1 ERIC HO: > Hi Andy, yes the same happens in xterm.  I found out the cause of the > problem. I have the following statement in my .bashrc: > set -o vi > > Not sure why this would casue the problem of using  shift PF key and causing > terminal hung and bash looping. Sounds like a bug to m

Re: [1.7] Updated: cygwin-1.7.0-54

2009/8/1 Christopher Faylor: >>Still something dodgy going on with 1.7.0-55: > > Yes.  I just fixed another problem and am generating a snapshot.  Can > you download today's snapshot and confirm that this is fixed before I go > to the trouble of building a -56 release? Installed cygwin1-20090801.d

Re: [1.7] Updated: cygwin-1.7.0-54

2009/8/1 Christopher Faylor : >>> Something still not 100% correct with 1.7.0-54 >>> >>> startxwin.bat gives me this error: >>> >>> xterm: Can't execvp /usr/bin/tcsh: Invalid argument >>> xterm: Could not exec /bin/bash: Invalid argument >>> >>> I can start both shells in a DOS window, however. >>

Re: [1.7] bash loop and mintty hung issue

2009/8/1 ERIC HO: > I'm running cygwin 1.7.0(0.212/5/3), bash 3.2.49(23), mintty 0.4.4.  I use > C:\cygwin\bin\mintty.exe - and get a terminal session. I then press shift > F12. The window just lock up and the Windows Task Manager shows bash.exe > using 50% of cpu. When I close the hung window,

Re: bug in mbrtowc?

2009/7/28 Corinna Vinschen: >> >> Trouble is, the hack will also only work correctly if the whole UTF-8 >> >> sequence for the non-BMP character is passed at once. If you pass the >> >> bytes one-by-one instead, and assuming the bug above wasn't there, >> >> you'd get this: >> > >> > Yes, I know.  

wchar_t width (was: bug in mbrtowc?)

2009/7/28 Corinna Vinschen: >> Trouble is, the hack will also only work correctly if the whole UTF-8 >> sequence for the non-BMP character is passed at once. If you pass the >> bytes one-by-one instead, and assuming the bug above wasn't there, >> you'd get this: > > Yes, I know.  The real trouble i

Re: bug in mbrtowc?

2009/7/28 Corinna Vinschen: > On Jul 27 22:56, Andy Koppe wrote: >> I've encountered what looks like a bug in mbrtowc's handling of UTF-8. >> Here's an example: >> >> #include >> #include >> #include >> #include >> >> i

Re: bug in mbrtowc?

2009/7/28 Pedro Izecksohn: >  The bug is in O.P.'s code as &s is not being passed to mbrtowc. >From http://www.opengroup.org/onlinepubs/009695399/functions/mbrtowc.html: "If ps is a null pointer, the mbrtowc() function shall use its own internal mbstate_t object, which shall be initialized at prog

Re: bug in mbrtowc?

2009/7/28 Pedro Izecksohn: >> #include >> #include >> #include >> #include >> >> int main(void) { >> wchar_t wc; >> size_t ret; >> mbstate_t s = { 0 }; >> puts(setlocale(LC_CTYPE, "en_GB.UTF-8")); >> printf("%i\n", mbrtowc(&wc, "\xe2", 1, 0)); >> printf("%i\n", mbrtowc(&wc, "\x94", 1, 0))

bug in mbrtowc?

I've encountered what looks like a bug in mbrtowc's handling of UTF-8. Here's an example: #include #include #include #include int main(void) { wchar_t wc; size_t ret; mbstate_t s = { 0 }; puts(setlocale(LC_CTYPE, "en_GB.UTF-8")); printf("%i\n", mbrtowc(&wc, "\xe2", 1, 0)); printf(

Re: mingw headers and libraries missing

> 2009/7/27 Georg Troska: >> I want to compile some code with -mno-cygwin. >> Unfortunately some mingw-libs are missing (sys/select.h, sys/cdefs.h). also >> the corresponding libraries >> >> How can I get them? > > You can't, because MingW doesn't implement select(). ps: Windows itself has a selec

Re: mingw headers and libraries missing

2009/7/27 Georg Troska: > I want to compile some code with -mno-cygwin. > Unfortunately some mingw-libs are missing (sys/select.h, sys/cdefs.h). also > the corresponding libraries > > How can I get them? You can't, because MingW doesn't implement select(). Andy -- Problem reports: http://c

Re: [1.7] Alternative root directory. Sort of a regression.

2009/7/27 Corinna Vinschen: > that rootdir is only used by setup.exe, not by Cygwin. I see, sorry. So I guess / simply is the parent of the directory cygwin1.dll is in? Makes plenty of sense. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/

Re: 1.5.25-15: Why my $INITRC "set convert-meta off" seems to fail?

2009/7/27 Rodion Gorkovenko: > You suppose this is windows, who responsible for this substitution? This > thought had not visited my head... I thought substitution is performed by > cygwin... It's done by the Windows text rendering functions. It's fairly useful actually as a fallback, because at

Re: [1.7] Alternative root directory. Sort of a regression.

2009/7/26 Shaddy Baddah: > This certainly works, but as the method requires correction of the > root directory post (or during) the parse of /etc/fstab, it is not > suitable for forcing the location of the /etc/fstab through an > alternate root directory. The root directory still is in the registr

Re: 1.5.25-15: Why my $INITRC "set convert-meta off" seems to fail?

2009/7/27 Rodion Gorkovenko: > I am still try to get over my problem with ASCII 8-bit characters > translation. I now know about ~/.initrc file, readline, bind - bit more. > > But it still does not work. Look here: > > My ~/.initrc contains necessary setup: > > set meta-flag on 'meta-flag' is a s

Re: [1.7] mount -m output can contain flag 'noexec', which isn't understood in /etc/fstab

2009/7/22 Jon TURNEY: > j...@byron ~ > $ mount -m > //necker/jon /home/jon smbfs binary,noexec,noacl,user 0 0 > none /cygdrive cygdrive binary,posix=0,user 0 0 > > I want this to be permanent, so I edit /etc/fstab to add a copy of the line: > //necker/jon /home/jon smbfs binary,noexec,noacl,user 0

Incorrect codepage numbers in 1.7 guide

A couple of small mistakes in http://cygwin.com/1.7/cygwin-ug-net/setup-locale.html#setup-locale-charsetlist: ISO-8859-13 and -15 have codepage numbers 28603 and 28605, not 28563 and 28565. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq

Re: Patch to make readline parse CSI keycodes properly

2009/7/19 Eric Blake: >> It's working correctly here, including when adding bindings for longer >> keycodes: no more funny characters when accidentally hitting the wrong >> key. Please consider the patch for inclusion into the readline >> package. > > I'll play with this, and consider adding it to

Patch to make readline parse CSI keycodes properly

When pressing an unbound key or key combination in bash and other readline programs, somewhat cryptic characters are often inserted into the command line. For example, you get "~" for Insert, "4~" for F12, or ";5A" for Ctrl+Up. This can be rather confusing and annoying. The reason is that readline

[ANNOUNCEMENT] Updated: mintty-0.4.4-1

MinTTY is a terminal emulator for Cygwin with a native Windows user interface and minimalist design. Among its features are Unicode support and a graphical options dialog. Its terminal emulation is largely compatible with xterm, but it does not require an X server. MinTTY is based on code from PuTT

Re: wrong home directory

2009/7/13 hvshare: > Hello, > > I've searched all over the web for an answer to my problem but i couldn't > find one, so I decided to send a mail here. > > After I installed Cygwin, I noticed that my home directory '~' is not > /home/helvio, i.e. /cygdrive/c/cygwin/home/helvio (helvio is my user ID

[ANNOUNCEMENT] Updated: mintty-0.4.3-1

MinTTY is a terminal emulator for Cygwin with a native Windows user interface and minimalist design. Among its features are Unicode support and a graphical options dialog. Its terminal emulation is largely compatible with xterm, but it does not require an X server. MinTTY is based on code from PuTT

setup buttons (was: Re: Really dumb setup question)

2009/7/7 Dave Korn: > |---+-+-+-+--++-| > |Search |         | |Clear|       o Keep o Prev o Curr o Exp |View| Category| > |---+-+-+-+--++-| > >  "Keep" sets all the selections so

Re: [1.5.25-15] bash won't load .bashrc after i rename it as `sh.exe'.

2009/7/12 chengxianle: > Yes, .bash_profile was loaded when run bash as `bash --login'. > But still, won't load when run as `sh' or `sh --login'. Read Dave Korn's reply again. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentati

OT: gmail quoting (was Re: [OT] Re: Virus on sed.exe)

> 2009/7/10 Dave Korn <...>: Sorry for including your email address. (Does anyone know a way to switch that off in the gmail web interface?) Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs

Re: [OT] Re: Virus on sed.exe

2009/7/10 Dave Korn : > http://www.theregister.co.uk/2009/07/10/ca_rogue_av_update/ "On July 8, 2009 at 11:00am EST, a CA DAT file release contained improperly formed malware detections that errantly detected clean files from Microsoft Windows Service Pack 3 and from the commercial Cygwin applicat

<    3   4   5   6   7   8   9   10   11   >