Re: "can't create master tty" errors

Cesar Crusius: > I am using Cygwin and SSH to do automated remote builds using Visual > C++. It works for a few days, but invariably things start failing with > messages like these (this one from a build log): > > Makefile:9: MakePID: 5964 >      1 [main] env 2748 C:\cygwin\bin\env.exe: *** fatal e

Re: About mode-dependent cursor

hayate: > When I use cygwin shell or mintty wrapper I want it like real term > emulator in Linux. There isn't a Cygwin shell as such. What happens is that bash (or another shell) runs in a Windows console, whereby the Cygwin DLL provides Unix terminal functionality for the console. And mintty isn

Re: terminals getting killed on parent's termination

Andy Koppe: > Thomas Wolff wrote: >> In general, a GUI application started in the background, like a terminal, >> should detach itself from its parent process so that it survives if the >> parent is terminated. > > Says who? You can always invoke it with setsid or some s

Re: terminals getting killed on parent's termination

Thomas Wolff: > Termination of a terminal's parent. This should not abort the terminal > session, whether or not the notification mechanism is HUP. (In the case > console -> xterm you said it's due to console attachment, whatever that > means in detail.) Well, in practical terms it means that xter

Re: terminals getting killed on parent's termination

Thomas Wolff: >>> In general, a GUI application started in the background, like a terminal, >>> should detach itself from its parent process so that it survives if the >>> parent is terminated. >> >> Says who? > > Common practice in Unix/Linux/X environments. I've finally got round to trying to co

Re: Odd behavior of mintty with screen

Gary Johnson > When I execute screen, however, the mintty > window immediately shrinks from 157x49 to 80x49.  This shrinking > does not occur if I maximize the mintty window before executing > screen. I've had a quick look, and with TERM=xterm-256color I find that screen sends the DECCOLM sequence

Re: terminals getting killed on parent's termination

Thomas Wolff: > Andy Koppe: >> Mintty has default handling for SIGHUP, i.e. it exits. > > Actually (another topic but related) mintty has a great feature here: it > passed the SIGHUP to its client application and if that application catches > and handles the SIGHUP, mintt

Re: mintty colors

Gary Johnson: >> You could just make that bit conditional on the value of TERM. > > Except that mintty doesn't have its own terminfo database, so TERM > needs to be set to "xterm". Set it to 'mintty' in the options and change it back to 'xterm' (or 'xterm-256color') as part of the conditional code

Re: mintty colors

Gary Johnson: > I have downloaded mintty-0.6-beta2-cygwin15.zip and read > mintty-0.5.8.pdf, but I don't see a way to change the ANSI color > palette other than to send escape sequences. You're right, there isn't, as documented. > I could echo the > escape sequences in my ~/.bashrc, but mintty is

Re: Non-canonical mode input via tcsetattr(), under mintty console

Thomas Wolff: > Dave Lee schrieb: >> >> Hi all, >> >> I was testing a program that uses non-canonical mode input via >> tcsetattr(). >> >> ... >> Specifically, I entered the chinese character "例" (which means "rule" >> or "example"). It occupies 3 bytes in UTF-8 representation: E4, BE, 8B. >> >> On

[ANNOUNCEMENT] mintty-0.5.8-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: terminals getting killed on parent's termination

Thomas Wolff wrote: > In general, a GUI application started in the background, like a terminal, > should detach itself from its parent process so that it survives if the > parent is terminated. Says who? You can always invoke it with setsid or some such to detach it. > I've noticed the following

Re: [ANNOUNCEMENT] Updated: Unicode text editor MinEd 2000.16

Hallo Thomas, Der Link zur Standalone-Version (http://towo.net/mined/download/mined-2000.16-windows.zip) zeigt einen 404-Fehler. Hab stattdessen das Cygwin-Paket von Hand ausgepackt. Funktioniert. Der Eintrag im Explorer-Kontextmenü ist eine gute Idee, aber vielleicht sollte der besser optional s

Re: [1.7.2] change in cygpath -w behaviour?

Corinna Vinschen: >> On 1.7.1 (with C:\ as Cygwin root): >> $ cygpath -w /tmp >> C:\tmp >> >> On 1.7.2s(0.222/5/3) 20100219 12:56:31: >> $ cygpath -w /tmp >> \\?\C:\tmp >> >> The latter breaks scripts that aren't sufficiently careful about >> backslash quoting, because "\\?\C:\tmp" loses a vital ba

[1.7.2] change in cygpath -w behaviour?

It seems there's been a change in 'cygpath -w' behaviour. Is this intentional? On 1.7.1 (with C:\ as Cygwin root): $ cygpath -w /tmp C:\tmp On 1.7.2s(0.222/5/3) 20100219 12:56:31: $ cygpath -w /tmp \\?\C:\tmp The latter breaks scripts that aren't sufficiently careful about backslash quoting, bec

Re: Batch file code to launch rxvt pointed elsewhere than $HOME -- what's wrong with my code?

SJ Wright: > I'm trying to write batch scripts of the kind that start a Cygwin session in > rxvt from the desktop, with the added feature that the session starts in a > folder other than $HOME. I want to do this for two folders I use often. > > I know urxvt has a -cd command, and thought rxvt in Cy

Re: Problems with mutt & charset

Gary: >> I don't use mutt, so I can't really help here, but a mintty user >> reported that he had to rebuild mutt against ncursesw (which is now >> part of the Cygwin distribution) to get UTF-8 in mutt working: >> http://code.google.com/p/mintty/issues/detail?id=124#c28 > > Hmm. You mean to get any

Re: mintty - char encoding problems

David Balažic: >> I'm puzzled by that, because the standards and formats setting >> shouldn't have any effect on LANG, at least as far as mintty and >> Cygwin are concerned. Any idea how it might have got set to "SL"? > > As I already mentioned, it is a fresh cygwin install. > And since the problem

Re: mintty - char encoding problems

David Balažic: >>> A mismatch of Cygwin's charset and mintty's charset, probably. What >>> versions of Cygwin and mintty are you using? What are the values of >>> LC_ALL, LC_CTYPE and LANG? Is anything set in the Charset (or >>> Codepage) field on the Text pane of mintty's options? >> >>  Cygwin DL

Re: Problems with mutt & charset

Gary: > For some reason although when I send emails containing certain umlauted > characters everything looks fine, the recipient sometimes (or possibly > always, I only know because one person mentioned it) doesn't see the > characters correctly. > > I have the following environment variables set

Re: 1.7.1: unable to run the a bash script resides in chinese path using: c:\cygwin\bin\bash --login script.

Corinna Vinschen: >> Anyway, I had a look into why the dosfilewarning prints the wrong >> filename: it calls small_sprintf to print the message, and >> small_sprintf uses the ANSI version of WriteFile to write to >> STD_ERROR_HANDLE, so it ends up interpreting a UTF-8 string as GBK. >> Seems sys_mb

Re: 1.7.1: unable to run the a bash script resides in chinese path using: c:\cygwin\bin\bash --login script.

Hongyi Zhao: >>Looks like there's some sort of GBK vs UTF-8 mixup going on, because >>'鏂版煡鏂囩尞' is the same byte sequence in GBK as '新查文献' is in UTF-8: >>\xE6\x96\xB0\xE6\x9F\xA5\xE6\x96\x87\xE7\x8C\xAE > > Could you please give me some hints on the tools > used by you to obtain this conclusion? Th

Re: 1.7.1: unable to run the a bash script resides in chinese path using: c:\cygwin\bin\bash --login script.

Hongyi Zhao: > C:\cygwin\bin\bash --login "%~dp0myscript" > ... > Preferred POSIX equivalent is: "F:/zhaohs/Desktop/鏂版煡鏂囩尞/myscript" > ... > /usr/bin/bash: "F:\zhaohs\Desktop\新查文献\myscript": No such file or directory Looks like there's some sort of GBK vs UTF-8 mixup going on, because '鏂版煡鏂囩尞' is

Re: mintty - char encoding problems

On 19 February 2010 19:39, David Balažic: > Hi! > > I have few days old setup of cygwin on WinXP. > I also installed mintty. > > I worked fine on one user account, which is a member of the > Administrators group. > > Today I started mintty under another, not admin, user, and got this: > > »./.bash

Re: TTY write deadlock

On 5 April 2009 00:03, Christopher Faylor wrote: > On Sat, Apr 04, 2009 at 03:11:06PM -0700, Josh Stone wrote: >>I've discovered a deadlock in Cygwin which is pretty easy to >>reproduce.?? This seems to happen on all of the console windows I can >>find, except for running in a normal cmd.exe.  All

Re: Download site http://mirrors.kernel.org

> Also, helps you answer this for yourself > anytime. An oddity in that list: Japan appears as a continent with Asia as a country. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation:

Re: About SystemC installation in Cygwin

Mohammad Qayum: > 'configure' didn't succeed. What could be the > potential cause of configure failure Anything. Look at configure's output, it will usually tell you. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation:

Re: Changing .ini file searched for by setup-legacy.exe

Hussein Patwa: > I realise the older version of Cygwin is no longer supported, but would > anyone know if there is a way to change the setup.ini that the legacy > setup looks for on the mirror? I don't know of a way short of hacking the source. > I have to install the legacy setup as the Rockbox

Re: Can't find setup.ini in any mirror

Steve Denson: > Cygwin setup.exe can't find setup.ini in any mirror. Are using the latest setup.exe from the Cygwin homepage? Any firewalls or proxies that might be in the way? Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentat

Re: Python does not support default locale

Jurgen Defurne wrote: > This morning I started python from a new installation 1.7 installation > and I got the following warning. Python seems to be ok with C.UTF-8 here: $ python Python 2.5.2 (r252:60911, Dec 2 2008, 09:26:14) [GCC 3.4.4 (cygming special, gdc 0.12, using dmd 0.125)] on cygwin T

Re: dlclose not calling destructors of static variables.

Christopher Faylor: > Andrew West: >>O.k. I'll check out the changes on Monday, but one minor point. >>Shouldn't the atexit stuff be run after all the destructors have run? > > Not if the output from the linux version of your program is to be > believed.  I originally had the atexit stuff run after

Re: File format problem after updatin to 1.7.1

Jeremy Bopp: > DEWI - N. Zacharias: >> i have just updated to 1.7.1 an run in trouble.  During the previous >> installations there was a switch which sets the used file format Dos/Unix. >> This switch did not only disappear also the former uses file format (DOS) >> was set to Unix underhand . Th

Re: Please support CP932. (I have problem using subversion with SJIS)

Kazuhiro Fujieda: > Andy Koppe: >> Another example is X11, which has its own locale system independent >> from Cygwin's. There, "ja_JP" implies eucJP already. This means that >> with LANG=ja_JP, xterm uses eucJP, while filenames and programs >> currently

Re: [1.7] Recent build failures (grap and nano) and strange characters in error log

2010/1/27 Fergus: > Q2 I attach the error log (only 6 lines) when attempting "make" after a > successful "./configure" of grap v.1.43. I am particularly surprised at and > bothered by the intrusive strange characters. It's due to using rxvt with a UTF-8 locale, which rxvt does not support. > Shou

Re: Please support CP932. (I have problem using subversion with SJIS)

2010/1/27 Kazuhiro Fujieda: > Andy said `Seems SJIS really isn't suited for Unix command line > use.' I said there is no problem, no difference with EUC-JP, and > no need to change the default. That comment primarily referred to standard SJIS, with its mappings of the ASCII backslash and tilde cod

Re: Please support CP932. (I have problem using subversion with SJIS)

2010/1/26 Corinna Vinschen: >> Any users of Japanese version of Windows don't use eucJP as >> typical euncoding scheme. It will cause unnecessary confusion. > > Well, you can always use "ja_JP.SJIS". > > As for the default charset, now > that we get extended NLS support, there are packages out ther

[ANNOUNCEMENT] Updated: mintty-0.5.7-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: Compiling strings with nonascii chars.

2010/1/25 Ed Keith: > > I am trying to build ocaml on cygwin and I hit the following error: > > > make[1]: Entering directory `/usr/src/ocaml-3.08.1/ocamldoc' > ../ocamlcomp.sh -pp './remove_DEBUG' -I ../parsing -I ../utils -I ../typing > -I . > ./driver -I ../bytecomp -I ../tools -I ../toplevel/

Re: Please support CP932. (I have problem using subversion with SJIS)

2010/1/24 Corinna Vinschen: >> Something's going seriously wrong with this, and I'd suspect it's to >> do with turning backslashes into yen symbols. > > Right.  It occured to me tonight that this will not work from a > filesystem point-of-view.  The people who decided to overload backslash > and ti

Re: Please support CP932. (I have problem using subversion with SJIS)

Corinna Vinschen: > I applied a patch which handles the characters 0x5c and 0cfe differently > if the charset is set to "SJIS" Something's going seriously wrong with this, and I'd suspect it's to do with turning backslashes into yen symbols. C:\Users\Andy>set LANG=C.SJIS C:\Users\Andy>\bin\bash -

Re: Setup.exe 2.674 does not work properly if retry is used

On 23 January 2010 12:02, Christian Franke: >>> Current setup.exe does not work properly if retry is used. >> >> Known regression.  Somebody has to fix this. > > This is apparently fixed in setup.exe 2.677 Yep, cgf braved the innards of setup.exe and hunted down that bug. Andy -- Problem reports

Re: Please support CP932. (I have problem using subversion with SJIS)

On 23 January 2010 15:07, Corinna Vinschen: > Ouch.  I understand now.  Standard SJIS is *really* different from > Microsoft CP932 in two code points: > >  CP932 0x5c == U+005E >  SJIS  0x5c == U+00A5 > >  CP932 0x7e == U+007E >  SJIS  0x7e == U+203E Aargh! I wonder what that would do to DOS paths

Re: Why require ps -W and kill -f

2010/1/22 Don Beusee: > ps -e on Unix displays “every process running on the system”.  This command > doesn't do that under cygwin.  Why should it be necessary to supply -W to > see all processes running on the system? Because those processes are not Cygwin/Unix processes. In particular, they do n

Re: path not found - fstab problem?

2010/1/21 Russ: > Hello, > > I have cygwin installed in the default c:\cygwin location... > > I cannot get cygwin to see an executable in my path  -- unless I > change dirs down to the application location or run it with the > absolute path. > > This works: > r...@mycomputer  ~ > $  /c/Apps/apache-

Re: highlight keywords

2010/1/20 indrek: > I'm using make/gcc for compiling applications. It generates a lot of output. > I need to highlight some keywords (show red text), in example "error". > Is it possible with Cygwin. Have a look at the colorgcc package as well. (Unfortunately its default config is broken, looking

Re: rxvt ctrl-c killing process

Sven Köhler: > David Smiley: >> I have been fed-up with the default GUI shell on Cygwin, being used to the >> great Terminal that comes with Mac OS X.  Some googling around uncovered >> that I should try "rxvt".  My experience with rxvt is pretty good, after >> reading online some basic configurati

Re: How to print textfiles in Cygwin 1.7?

2010/1/15 Niklaus Kuehnis: >> If you want to >> be sure to use UTF-8, then say so:  export LANG=de_CH.UTF-8. > > I set this variable (and also LC_CTYPE and LC_ALL), and printing with > umlauts with bare a2ps works fine now. Thanks! I can't confirm that. Sure you were printing a UTF-8 file there?

Re: Bag LANG setting?

2010/1/14 Jason Pyeron : > When doing man grep it blurted out many <##> hex codes. If I unset LANG, > LANGVAR I get extended ascii. I am using teraterm to connect via ssh. What's 'extended ascii'? You need to ensure that your terminal is set to the same character set as Cygwin. The second of you

Re: Should LANG be set or left unset?

Corinna Vinschen: > aputerguy: >> Is it best to leave it that way or would it be better to set it to something >> like LANG=en-US.UTF-8 (or even C) > > Not necessary.  As described in the User's Guide, the default locale > in the absence of a LC_ALL/LC_CTYPE/LANG variable is "C.UTF-8". I'd still r

Re: Strange case of missing XWin

2010/1/14 Fergus: > I installed portable Cygwin to a low-capacity USB stick by "picking" Base > and then extras from the selection menu. Amongst other things I picked up > xterm, Lyx, TeX. (I've done this item-by-item selection a few times in the > past but not recently; and never with 1.7.) > Some

Re: Fresh installation issues Cygwin 1.7

2010/1/14 Manish Agarwal: > These are the packages/commands/features which I have been using with > cygwin. I am unable to install them through a "fresh" setup.Reason for > not being able to install: they no longer exist in the package select > window. > > xdvi (I _have_ installed and using tetex,

Re: Tried out cygwin-inst-20100111.tar.bz2

2010/1/13 Corinna Vinschen: > That only occurs in CYGWIN=tty mode.  The problem was that in tty mode a > piece of code reset all termios settings of the console to 0.  That was > no problem so far, but now that the VERASE key from the termios settings > is used to delete chars in the console, it hu

Re: various problems resulting from version 1.7.1

2010/1/13 Cyrille Lefevre: > give a try to puttycyg which support both ssh, telnet as well cygwin. The OP is insisting on running the Windows versions of telnet and ftp, and those won't work in puttycyg either. Same in any other terminal based on 'pseudo terminal' (pty) devices. Andy -- Problem

Re: How to print textfiles in Cygwin 1.7?

2010/1/12 Niklaus Kuehnis: > I've upgraded to Cygwin 1.7 (release version, clean install) and now am > unable to print text files with non-ascii characters (i.e. German umlauts) > from commandline. > > On Cygwin 1.5 printing used to work with a2ps but now all umlauts are > replaced by strange ch

Re: various problems resulting from version 1.7.1

2010/1/12 Nellis, Kenneth: > Thank you, Jeremy. BTW, I deal with legacy machines that don't > know from SSH. :-( > > Well this gets more interesting, at least to me... > With LANG=UTF-8, man uses the Unicode HYPHEN character (U+2010) > to break long words at the right margin, and uses the Unicode >

Re: Running Cygwin from an NFS drive (symlinks with system attribute)

2010/1/12 sbremal > I am afraid the winsymlinks option is an installation time setting, is it? : No, but it only affects newly created symlinks. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/

Re: ntEmacs has trouble with cygwin terminal...

2010/1/11 aputerguy > > Here is the situation: > > Running from a cygwin 1.7 bash terminal: > $ emacs -nw > > > $emacsclient -nw > *ERROR*: Not using an ASCII terminal now; cannot make a new ASCII frame > > $echo $TERM > cygwin > > Running from within screen within cygwin: > $ emacs -nw > emacs: s

Re: HOME environment variable set in Windows

> Hi, > I discovered that the HOME variable is set in windows. I therefore get the > cygwin HOME path set to this window path instead of the path set in passwd > as I would like it. I tried to delete the windows HOME path, but I can't > find it. Where is it set or what does set it? I have HOME, HOM

Re: [ANNOUNCEMENT] updated: orpie-1.5.1-2

2010/1/8 Andrew Schulman: > * In order for lapack to work, you have to have /usr/lib/lapack in your > $PATH.  IMO that's a bug I agree, and I shudder to think what the path would look like if every library did that. I don't see why the lapack DLLs can't go into /usr/bin like everything else. Than

Re: [ANNOUNCEMENT] updated: orpie-1.5.1-2

2010/1/8 Thomas Wolff: > Andrew Schulman wrote: >> >> A new version of orpie, 1.5.1-2, is now available in the Cygwin >> distribution. >> >> This release is a Cygwin-only update.  The package has been rebuilt for >> Cygwin >> 1.7, removing dependence on some obsolete packages.  I recommend that all

Re: How do I disable old SSH protocol

2010/1/7 raytheman: > > My cygwin supports all the old SSH protocol, I need to disable them in order > to meeting the security requirement, please help. > > - 1.33 > - 1.5 > - 1.99 > - 2.0 RTFM: man ssh -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin

Re: obsolete Windows registry keys

2010/1/7 David Arnstein: > I have finished upgrading from  1.5.x to 1.7.x and I don't intend to > go back. Now I would like to delete the entries some entries from my > Windows registry. What are the keys that were used in 1.5.x, but are > no longer used in 1.7.x? HKLM\Software\Cygnus Solutions -

Re: Cygwin 1.7.1-1: problem with pipe to windows programs

2010/1/6 RH: > echo "select * from mytable" | unix2dos | sqlcmd -S server -U sa -P mypassword > -d myDatabase > > As you can see I'm trying to force the data hitting sqlcmd to be in dos mode > but > somehow I suspect it is getting put into linux-mode line endings before > hitting > sqlcmd.  The e

Re: Weird characters in man pages

2010/1/6 Wes Barris: > I just installed Cygwin 1.7.1 and Puttycyg 20091228.  When I viewed > a man page I saw the letter 'a' with two dots above it instead of > '-' characters.  So, knowing that Cygwin 1.7 now used UTF-8, I changed > my character translation set in Puttycyg to UTF-8 for my Cygwin >

Re: Cygwin 1.7.1-1: problem with pipe to windows programs

2010/1/6 RH: > KJ writes: >> within a cygwin shell I used to pipe some data into a windows program >> (sqlcmd.exe) which used to work pretty well. Since upgrading to version >> 1.7 I get the following error: >> $ echo "select @@version" | sqlcmd >> Sqlcmd: Error: Internal error at ReadTextLine (Rea

Re: setup*exe for legacy and current versions

2010/1/6 Fergus: >>> Something wrong somewhere? > >>  No. > > O .. K .. thanks for that ... > So how does the same executable differing only in name trigger two entirely > different installations? It checks its own name using argv[0] and acts accordingly. Andy -- Problem reports: http://cy

Re: [Fwd: Blue screen when running installation *.sh]

2010/1/5 Paul Keusemann: >> I have previously used Cygwin 1.5 successfully, but thought I should >> report a possible issue with the newer 1.7.1 version. >> >> My XP workstation blue screens reliably when doing the final steps of the >> Cygwin 1.7.1 installation somewhere in the /etc/postinstall/*.

Re: git stopped working with 1.7.1

2010/1/5 Vadim Zeitlin: >  Exactly the same thing happens here with 1.7.1 under 64-bit Windows 7. > However my Cygwin is not a new install but an upgrade of a previous 1.5 > installation -- in which Git worked just fine. Does the locale setting make a difference? For example, try it with the follo

Re: rxvt and strange characters from man

2010/1/4 tim richardson: > I've setup rxvt, and take the default term settings. > This is the latest cygwin as of today, Vista host. > > when I do man x, I get odd characters: mis-interpreted control characters. > The default cygwin terminal works fine. > > for example, if I do > man man > > I get

Re: Cygwin 1.7.1 sprintf() with format string having 8th bit set

2010/1/4 Joseph Quinsey: > 1) In my bad test, I already had my LOCALE set to C.ASCII: > >   env | grep LC >   LC_ALL=C.ASCII To use the locale set in the environment you need to invoke setlocale(LC_CTYPE, ""), i.e. with an empty string as the second parameter. Without a setlocale call, your progra

Re: Cygwin 1.7.1 sprintf() with format string having 8th bit set

2010/1/4 Thomas Wolff: > My assumption has been that *printf should be byte-transparent unless where > it uses explicit wide character arguments. What's that assumption based on? > After all, legacy applications that do not care about locales at all may > legitimately assume this since a C char

Re: Cygwin 1.7.1 sprintf() with format string having 8th bit set

2010/1/4 Joseph Quinsey > In Cygwin 1,7.1, sprintf() with the format string having an 8th bit set > appears to be broken. Sample code (where I've indicated the backslashes in > the comments, in case they are stripped out by the mailer): > > #include > > int main (void) > { >    unsigned char foo[3

Re: cygwin_create_path

2010/1/3 Andy Koppe: > I'm having a spot of trouble changing mkshortcut to use the > wchar_t-enabled cygwin_create_path instead of the deprecated > cygwin_conv_to_full_win32_path & co. When converting to a Windows path > using CCP_POSIX_TO_WIN_W, the result is a path starti

cygwin_create_path

I'm having a spot of trouble changing mkshortcut to use the wchar_t-enabled cygwin_create_path instead of the deprecated cygwin_conv_to_full_win32_path & co. When converting to a Windows path using CCP_POSIX_TO_WIN_W, the result is a path starting with "\\?\", e.g. "\\?\C:\cygwin\bash.exe". Yet un

Re: [ANNOUNCEMENT] New: Updated: {ncursesw/libncursesw10/libncursesw-devel/ncursesw-demo}-5.7-18

2010/1/2 Charles Wilson: > ncurses is a package that provides character and terminal handling > libraries, including 'gui-like' panels and menus.  It is often used > instead of termcap. ncursesw provides a version of this library and > related tools compiled to support wide characters (that is, wch

Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt

Lee Rothstein: >> Will Windows junctions (for the path; plus the file name) work, here? Don't think so, afaik junction points (introduced in Win2000, and different from Vista/7 symlinks) work correctly for directories only. Hard links, however, should work just fine for the problem at hand. tul

Re: Help on configuring keyboard on Cygwin/x on Windows XP

2010/1/1 Gunnar Vestergaard: > I prefer that Emacs accepts input from my Faroese keyboard, or at least > Danish if need be. Whatever I do, the US keyboard mapping is in effect > always. How do I change that? I mean, for every X11 application? X questions should go to the cygwin-xfree list. The X

Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt

2009/12/30 Larry Hall (Cygwin): >> I've been using gcc and other tools in older versions of cygwin with >> 32-bit Windows XP and Vista from windows command prompt (cmd.exe) >> without problems. But now I'm using 64-bit Windows 7, and some command >> line tools like gcc.exe do not work anymore (from

Re: Alt key not recognized as Meta in xterm

2010/1/1 Thomas Dickey: > On Fri, 1 Jan 2010, Andy Koppe wrote: > >>>    XTerm*vt100.metaSendsEscape: true >> >> Actually that's not a hack, but the correct solution. I think this >> needs to be part of the default config in /etc/X11/app-defaults/XTerm. &g

Re: Alt key not recognized as Meta in xterm

2009/12/30 Gary Carvell: X issues including xterm ones should go to the cygwin-xfree list. I'm sending this to both lists, but please respond on cygwin-xfree only. > With the upgrade to Cygwin 1.7, I found that the Alt key is no longer > recognized as a Meta key in xterm. This means the Alt based

Re: gcc4[1.7] printf treats differently a string constant and a character array

> Some comments: > 1- I think that printf(string_constant) and printf(char_array) should give > the same > output in any circumstance. > 2- In absence of a call to setlocale printf((string_constant) writes > according to > the locale of the environment, but  printf(char_array)  does not, even > tho

Re: [ANNOUNCEMENT] Updated: cygutils-1.4.2-1

2009/12/29 Charles Wilson: > TODO (call for patches): > > * Update lpr.cc and mkshortcut.c to use cygwin-1.7 cygwin_conv_path >  instead of deprecated cygwin_conv_to_win32_path. I'll have a go at mkshortcut. Andy -- Problem reports: http://cygwin.com/proble

Re: gcc4[1.7] printf treats differently a string constant and a character array

2009/12/29 Eric Blake: >> I couldn't find specific text about invalid bytes in the POSIX printf >> spec, > > http://www.opengroup.org/onlinepubs/9699919799/functions/fprintf.html > > "all forms of fprintf() shall fail if: > > [EILSEQ] >    [CX] A wide-character code that does not correspond to a va

Re: gcc4[1.7] printf treats differently a string constant and a character array

2009/12/29 Rodrigo Medina: >>Ah, the problem actually is that your program is missing a call to >>setlocale(LC_CTYPE, "") to switch to the locale and character set >>specified in the environment... > > That worked!, but what that means is that if one wants to > use any locale other than C.UTF-8, on

[ANNOUNCEMENT] Updated: mintty-0.5.6-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: gcc4[1.7] printf treats differently a string constant and a character array

2009/12/28 Andy Koppe: > 2009/12/28 Rodrigo Medina: >> Hi, >> I am moving from cygwin-1.5 and gcc3.4 to cygwin1.7 and gcc4. >> Some simple programs of mine fail. >> >> I am using LC_ALL=es_VE.ISO-8859-15. >> >> I have reduced the problem to this exam

Re: gcc4[1.7] printf treats differently a string constant and a character array

2009/12/28 Rodrigo Medina: > Hi, > I am moving from cygwin-1.5 and gcc3.4 to cygwin1.7 and gcc4. > Some simple programs of mine fail. > > I am using LC_ALL=es_VE.ISO-8859-15. > > I have reduced the problem to this example > > -- > #include > main() > { > static char* line1 = > " This l

Re: rsync no longer preserves extended ASCII characters after 1.7 upgrade

> On 2009/12/27 7:56 PM, Adam Rosi-Kessel wrote: >> But when I >> view them from the linux box, they have scrambled accents -- either just >> ?'s if I use ls (must be a terminal issue) You probably haven't got a charset configured on the Linux box. In that case, ASCII is assumed, and 'ls' prints a

Re: No go after update to 1.7.1

2009/12/27 Bernd Bartmann: >> What does: >> >> c:\cygwin\bin\cygcheck c:\cygwin\bin\bash.exe >> >> show?  It will probably show that you're missing some basic dlls >> which, for some reason, will need to be (re)installed. >> >> You can find the packages which hold the missing dlls by going to >> ht

Re: New 1.7 release setup does not run on WinNT

2009/12/27 Jerry DeLisle: > I am going to try a completely fresh install.  I have nothing to lose. No point in that. I'm afraid you'll need to wait for a setup.exe fix. Andy -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation:

Re: New 1.7 release setup does not run on WinNT

2009/12/27 Jerry DeLisle: > I have been using the 1.7 beta without any issues up until the official > release.  I try to run 1.7.1 setup and nothing happens, it just exits > without even opening a window. > > Trying to run the previous version of setup works until it encounters > setup.ini which no

Re: run2.exe segfaults when GDI and X11 elements are present

2009/12/26 Charles Wilson: > There's one remaining problem with your scenario: when the Xserver is > not available, and the option is used: > >   >     >     >     >      -e /bin/bash >     >   > > mintty *IS* launched: it shows up in the process list, but the window is > not visible. I'm not sure

Re: need workaround for backspace change in 1.7

2009/12/25 Andy Koppe: > 2009/12/25 Ric Anderson: >> For a  variety of reasons, I need a way to switch the character sent by the >> Console Window Backspace key from ASCII \177 to ASCII \008 (that is, make >> the backspace key send the ASCII backspace character like it d

Re: putty isn't displaying correctly with 1.7

2009/12/26 Wes S : > Below is excerpt from man file on touch.  Highlighted text is showing > strange characters when I use putty to ssh in.  It was working fine > before the 1.7 upgrade. > > How do I fix this? > > Thanks, > > Wes > > >       âd, ââdate=STRING >              parse STRING and use it

Re: need workaround for backspace change in 1.7

2009/12/25 Ric Anderson: > For a  variety of reasons, I need a way to switch the character sent by the > Console Window Backspace key from ASCII \177 to ASCII \008 (that is, make > the backspace key send the ASCII backspace character like it did in older > cygwin versions). Can't be done at the mo

Re: can some one please help me fix compiling errors related to winsock and sys/types and fd_set...etc

2009/12/25 Mark Geisert: > Josh writes: > [...a bunch of detailed stuff...] > > If this were really a Cygwin program you likely wouldn't be #include-ing > winsock.h.  Is this a native Windows program you're just trying to build with > gcc?  If so, you likely don't want Cygwin, you want MinGW, a sep

Re: Problem with RightAlt key in mintty

2009/12/24 Andy Koppe: > 2009/12/24 Ken Brown: >> In the latest mintty (0.5.5-1), RightAlt plus f (or b) doesn't move the >> cursor one word forward (or backward) when editing the command line. The >> LeftAlt key still works as expected. > > Confirmed. As a workar

Re: BIG Issue with 1.7 install.... multiple utils missing: mount, cygcheck, mkpasswd, etc

2009/12/24 Linda Walsh: >        It appears several files are missing. > I have no mkpasswd or group, no mount.  Don't know what else is missing. > I do have 'sed', but it might have been there from before (I didn't > reinstall > it). > > I've done a cygcheck -c to see if any packages had missing f

Re: Problem with RightAlt key in mintty

2009/12/24 Ken Brown: > In the latest mintty (0.5.5-1), RightAlt plus f (or b) doesn't move the > cursor one word forward (or backward) when editing the command line. The > LeftAlt key still works as expected. Confirmed. As a workaround, switch on the Ctrl+LeftAlt is AltGr option on the Keyboard p

Re: Problems with SSHD service partially resolved (Other problem not resolved.)

2009/12/24 Gregg Levine: > My other problems are the typically idiotic Windows problems > concerning removing a directory (or a directory of directories). The > system refuses to believe that I have the rights to remove that > directory. Use 'rm -rf' from your new Cygwin install. Much faster than

<    1   2   3   4   5   6   7   8   9   10   >