GNUPLOT in Cygwin: Terminal type set to 'unknown'
I am trying to use GNUPLOT in Cygwin, however whenever I start it up it just says the terminal type is unknown and then when I try to plot something simple like sin(x), nothing happens. $ gnuplot G N U P L O T Version 4.4 patchlevel 0 last modified March 2010 System: CYGWIN_NT-6.1-WOW64 1.7.7(0.230/5/3) Copyright (C) 1986-1993, 1998, 2004, 2007-2010 Thomas Williams, Colin Kelley and many others gnuplot home: http://www.gnuplot.info faq, bugs, etc: type "help seeking-assistance" immediate help: type "help" plot window: hit 'h' Terminal type set to 'unknown' gnuplot> plot sin(x) gnuplot> Can anyone help me? Thanks. -- View this message in context: http://old.nabble.com/GNUPLOT-in-Cygwin%3A-Terminal-type-set-to-%27unknown%27-tp31001313p31001313.html Sent from the Cygwin list mailing list archive at Nabble.com. -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Mg3a - a version of Mg2a developed on Cygwin
On Feb 23 20:36, Bengt Larsson wrote: > Andrew Schulman wrote: > >> Why not ITP it as an official package? > > > >It will need a license. Right now there's no license information anywhere > >in the tarball AFAICT. > > > >Is the code in Mg3a taken from Emacs? If so, you need to include the GPL > >in your tarball. > > No, it was taken from Mg2a, which was public domain. See the README in > the orig/ directory. The orig directory is referred to in the README in > the source directory. > > README: > "The original README and documents are in orig/. The > extensions as well as the original, with some exceptions mentioned in > the original README, are in the public domain. " > > orig/README: > "Mg 2a README May 15, 1988 > > Mg (mg) is a Public Domain EMACS style editor." > > This is perhaps not perfect disclosure, but it is there. (I did miss > wcwidth.c, but it says: > > " * Markus Kuhn -- 2007-05-26 (Unicode 5.0) > * > * Permission to use, copy, modify, and distribute this software > * for any purpose and without fee is hereby granted. The author > * disclaims all warranties with regard to this software. > " Just a hint: When on Cygwin, you might better use Cygwin's(*) wcwidth function. It's based on the same code from Markus Kuhn, but it interacts with the setlocale function to make sure that the width returned for the CJK ambiguous width characters makes sense in the given locale. Plus, it supports a Cygwin-specific locale modifier '@cjknarrow' which allows the user to modify this behaviour. When using your own wcwidth, you're giving up on this feature. Better yet, convert wide chars to wide strings and use the wcswidth function. In contrast to wcwidth, it can also handle surrogate pairs. Corinna (*) Actually newlib's wcwidth. -- 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
License conflicts in Cygwin
Hello, we would like to use Cygwin. After checking the license conditions we found two license conflicts in Cygwin, which is GPL v2 licensed in accordance with the COPYING files of Cygwin: 1) GPL v2 - GPL v3 incompatibility: (see http://gplv3.fsf.org/wiki/index.php/Compatible_licenses#GPLv3-incompatible_licenses) The following files are GPL v3 licensed: \cygwin-1.7.1-1\include\dwarf2.h \cygwin-1.7.1-1\include\lto-symtab.h \cygwin-1.7.1-1\config\warnings.m4 \cygwin-1.7.1-1\include\opcode\score-datadep.h \cygwin-1.7.1-1\include\opcode\score-inst.h \cygwin-1.7.1-1\Makefile.def \cygwin-1.7.1-1\Makefile.in \cygwin-1.7.1-1\configure.ac \cygwin-1.7.1-1\include\binary-io.h \cygwin-1.7.1-1\config\lead-dot.m4 \cygwin-1.7.1-1\Makefile.tpl \cygwin-1.7.1-1\include\gdb\sim-rx.h \cygwin-1.7.1-1\include\gdb\sim-sh.h \cygwin-1.7.1-1\include\gdb\sim-d10v.h \cygwin-1.7.1-1\include\gdb\sim-ppc.h \cygwin-1.7.1-1\include\gdb\signals.h \cygwin-1.7.1-1\include\gdb\remote-sim.h \cygwin-1.7.1-1\include\gdb\sim-h8300.h \cygwin-1.7.1-1\include\gdb\sim-m32c.h \cygwin-1.7.1-1\include\gdb\sim-arm.h \cygwin-1.7.1-1\include\gdb\fileio.h \cygwin-1.7.1-1\include\gdb\sim-frv.h \cygwin-1.7.1-1\include\gdb\sim-lm32.h \cygwin-1.7.1-1\include\gdb\callback.h \cygwin-1.7.1-1\include\gdb\sim-cr16.h \cygwin-1.7.1-1\include\elf\rx.h \cygwin-1.7.1-1\include\opcode\moxie.h \cygwin-1.7.1-1\include\opcode\moxie.h \cygwin-1.7.1-1\include\elf\lm32.h \cygwin-1.7.1-1\include\elf\mn10300.h \cygwin-1.7.1-1\include\bfdlink.h \cygwin-1.7.1-1\include\plugin-api.h \cygwin-1.7.1-1\include\elf\score.h \cygwin-1.7.1-1\include\elf\vxworks.h \cygwin-1.7.1-1\include\coff\z80.h \cygwin-1.7.1-1\config.guess 2) GPL v2 - BSD with Advertising Clause incompatibility: (see http://www.gnu.org/licenses/license-list.html section Original BSD License) The following files are BSD (with Advertising Clause) licensed \cygwin-1.7.1-1\winsup\cygserver\sysv_shm.cc \cygwin-1.7.1-1\winsup\testsuite\winsup.api\shmtest.c \cygwin-1.7.1-1\winsup\testsuite\winsup.api\semtest.c \cygwin-1.7.1-1\winsup\testsuite\winsup.api\msgtest.c In order to solve the GPL v2 - GPL v3 conflict, the GPL v2 license could be changend in a "GPL v2 or later" license. Another solution would be to change the license of the GPL v3 licensed files into the GPL v2 license. A solution of the GPL v2 - BSD with Advertising Clause conflict could be to remove the advertising clause in the BSD license. Is it possible for you to do such license changes, so that we can use Cygwin? Thank you in advance! With best regards, Uwe Denk Siemens AG Industry Sector Mobility Division Complete Transportation Engineering, Development I MO CT ED CL SAE Mozartstr. 33 B 91052 Erlangen, Germany Tel.: +49 (9131) 7-29817 Fax: +49 (9131) 7-45817 mailto:uwe.r.d...@siemens.com Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Gerhard Cromme; Managing Board: Peter Loescher, Chairman, President and Chief Executive Officer; Wolfgang Dehen, Brigitte Ederer, Joe Kaeser, Barbara Kux, Hermann Requardt, Siegfried Russwurm, Peter Y. Solmssen; Registered offices: Berlin and Munich, Germany; Commercial registries: Berlin Charlottenburg, HRB 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322 -- 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: License conflicts in Cygwin
On Feb 24 10:55, Denk, Uwe wrote: > Hello, > > we would like to use Cygwin. After checking the license conditions we > found two license conflicts in Cygwin, which is GPL v2 licensed in > accordance with the COPYING files of Cygwin: First of all, you're referring to an old version of Cygwin. Right now we're at 1.7.7 with 1.7.8 right around the bend. This has an effect on the license, too, since the BSD advertising clauses have gone way. > 1) GPL v2 - GPL v3 incompatibility: (see > http://gplv3.fsf.org/wiki/index.php/Compatible_licenses#GPLv3-incompatible_licenses) > The following files are GPL v3 licensed: > \cygwin-1.7.1-1\include\dwarf2.h > \cygwin-1.7.1-1\include\lto-symtab.h > \cygwin-1.7.1-1\config\warnings.m4 > \cygwin-1.7.1-1\include\opcode\score-datadep.h > \cygwin-1.7.1-1\include\opcode\score-inst.h > \cygwin-1.7.1-1\Makefile.def > \cygwin-1.7.1-1\Makefile.in > \cygwin-1.7.1-1\configure.ac > \cygwin-1.7.1-1\include\binary-io.h > \cygwin-1.7.1-1\config\lead-dot.m4 > \cygwin-1.7.1-1\Makefile.tpl > \cygwin-1.7.1-1\include\gdb\sim-rx.h > \cygwin-1.7.1-1\include\gdb\sim-sh.h > \cygwin-1.7.1-1\include\gdb\sim-d10v.h > \cygwin-1.7.1-1\include\gdb\sim-ppc.h > \cygwin-1.7.1-1\include\gdb\signals.h > \cygwin-1.7.1-1\include\gdb\remote-sim.h > \cygwin-1.7.1-1\include\gdb\sim-h8300.h > \cygwin-1.7.1-1\include\gdb\sim-m32c.h > \cygwin-1.7.1-1\include\gdb\sim-arm.h > \cygwin-1.7.1-1\include\gdb\fileio.h > \cygwin-1.7.1-1\include\gdb\sim-frv.h > \cygwin-1.7.1-1\include\gdb\sim-lm32.h > \cygwin-1.7.1-1\include\gdb\callback.h > \cygwin-1.7.1-1\include\gdb\sim-cr16.h > \cygwin-1.7.1-1\include\elf\rx.h > \cygwin-1.7.1-1\include\opcode\moxie.h > \cygwin-1.7.1-1\include\opcode\moxie.h > \cygwin-1.7.1-1\include\elf\lm32.h > \cygwin-1.7.1-1\include\elf\mn10300.h > \cygwin-1.7.1-1\include\bfdlink.h > \cygwin-1.7.1-1\include\plugin-api.h > \cygwin-1.7.1-1\include\elf\score.h > \cygwin-1.7.1-1\include\elf\vxworks.h > \cygwin-1.7.1-1\include\coff\z80.h > \cygwin-1.7.1-1\config.guess None of these files is under control of the Cygwin project, most of them are not even used at all when building Cygwin. These files are all part of the underlying build system which has evolved from the original Cygnus build tree over time. Since they are subsumed under "common files", they are all included in the Cygwin source archive, even when unused. The part controlled by the Cygwin project is only the stuff below the winsup directory. All the files under the winsup subtree are Cygwin licensed, BSD, or Public Domain. There's no license collision with the GPLv3 files from the build system since Cygwin isn't just licensed GPLv2. Rather, Cygwin is licensed under the Cygwin license, which is GPLv2 plus an exception which allows interaction with other OSS licenses. Disclaimer: IANAL. I can't speak for our legal dept, of course. There won't be any changes in the Cygwin license any time soon as far as I'm aware. If your lawyers feel that they have more questions about this, the best course of action might be to contact Red Hat and discuss this problem with our legal dept. > 2) GPL v2 - BSD with Advertising Clause incompatibility: (see > http://www.gnu.org/licenses/license-list.html section Original BSD License) > > The following files are BSD (with Advertising Clause) licensed > \cygwin-1.7.1-1\winsup\cygserver\sysv_shm.cc > \cygwin-1.7.1-1\winsup\testsuite\winsup.api\shmtest.c > \cygwin-1.7.1-1\winsup\testsuite\winsup.api\semtest.c > \cygwin-1.7.1-1\winsup\testsuite\winsup.api\msgtest.c These have been fixed a couple of months ago. 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: Mg3a - a version of Mg2a developed on Cygwin
Corinna Vinschen wrote: >Just a hint: > >When on Cygwin, you might better use Cygwin's(*) wcwidth function. It's >based on the same code from Markus Kuhn, but it interacts with the >setlocale function to make sure that the width returned for the CJK >ambiguous width characters makes sense in the given locale. Plus, it >supports a Cygwin-specific locale modifier '@cjknarrow' which allows the >user to modify this behaviour. When using your own wcwidth, you're >giving up on this feature. > >Better yet, convert wide chars to wide strings and use the wcswidth >function. In contrast to wcwidth, it can also handle surrogate pairs. I don't use surrogates. I only use UTF-8 and UTF-32. But using cygwin's wcwidth may be worth thinking about. I suppose it will be consistent with mintty that way; otherwise not? Using wcswidth isn't very useful in the editor because it has special requirements, like showing control characters with ^C. That's one of the reasons I mostly wrote my own, all the special requirements. I always iterate of bytes, which are converted in a mode-dependent way to ints (UTF-32). Do you have a case-insensitive compare? Because I limited that to ASCII. -- 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: Mg3a - a version of Mg2a developed on Cygwin
On Feb 24 11:56, Bengt Larsson wrote: > Corinna Vinschen wrote: > >Just a hint: > > > >When on Cygwin, you might better use Cygwin's(*) wcwidth function. It's > >based on the same code from Markus Kuhn, but it interacts with the > >setlocale function to make sure that the width returned for the CJK > >ambiguous width characters makes sense in the given locale. Plus, it > >supports a Cygwin-specific locale modifier '@cjknarrow' which allows the > >user to modify this behaviour. When using your own wcwidth, you're > >giving up on this feature. > > > >Better yet, convert wide chars to wide strings and use the wcswidth > >function. In contrast to wcwidth, it can also handle surrogate pairs. > > I don't use surrogates. I only use UTF-8 and UTF-32. But using cygwin's > wcwidth may be worth thinking about. I suppose it will be consistent > with mintty that way; otherwise not? Yes, I think Andy uses the system functions as well. As for the wide char representation, wchar_t is UTF-16 on Cygwin, as on the underlying Windows, and surrogate pairs are always possible. You can't use any libc wide char function if you assume UTF-32. > Using wcswidth isn't very useful in the editor because it has special > requirements, like showing control characters with ^C. Well, it's not really such a big problem to special case wide char control values and just call wcswidth otherwise... > That's one of the > reasons I mostly wrote my own, all the special requirements. I always > iterate of bytes, which are converted in a mode-dependent way to ints > (UTF-32). Do you have a case-insensitive compare? Because I limited that > to ASCII. wcscasecmp and wcsncasecmp are both available. But obviously they use UTF-16, since wchar_t is UTF-16. 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: Mg3a - a version of Mg2a developed on Cygwin
Bengt Larsson wrote: >I don't use surrogates. I only use UTF-8 and UTF-32. But using cygwin's >wcwidth may be worth thinking about. I suppose it will be consistent >with mintty that way; otherwise not? And: is wcwidth always available in modern Unices? How do you find out these things? I mean practically available. -- 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: Mg3a - a version of Mg2a developed on Cygwin
Corinna Vinschen wrote: >> Using wcswidth isn't very useful in the editor because it has special >> requirements, like showing control characters with ^C. > >Well, it's not really such a big problem to special case wide char >control values and just call wcswidth otherwise... Oh I see. wcwidth takes a wchar_t. Handily, Kuhn's implementation takes an UCS character. Now I understand what you mean by wcswidth. -- 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: Mg3a - a version of Mg2a developed on Cygwin
On Feb 24 12:19, Bengt Larsson wrote: > Bengt Larsson wrote: > >I don't use surrogates. I only use UTF-8 and UTF-32. But using cygwin's > >wcwidth may be worth thinking about. I suppose it will be consistent > >with mintty that way; otherwise not? > > And: is wcwidth always available in modern Unices? How do you find out > these things? I mean practically available. wcwidth and wcswidth are XSI extensions, so they are optional. As for finding out, that's usally nicely done by autoconf'ing your project. 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: Mg3a - a version of Mg2a developed on Cygwin
On Feb 24 12:40, Bengt Larsson wrote: > Corinna Vinschen wrote: > >> Using wcswidth isn't very useful in the editor because it has special > >> requirements, like showing control characters with ^C. > > > >Well, it's not really such a big problem to special case wide char > >control values and just call wcswidth otherwise... > > Oh I see. wcwidth takes a wchar_t. Handily, Kuhn's implementation takes > an UCS character. Now I understand what you mean by wcswidth. Yeah, newlibs wcswidth combines UTF-16 surrogates into UCS-32 chars and calls the internal __wcwidth function, which is basically Kuhn's code, and which takes a wint_t as parameter. Since wint_t is 32 bit... Of course, this trick doesn't work for wcwidth, which will blindly call __wcwidth with every incoming surrogate half. 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: Mg3a - a version of Mg2a developed on Cygwin
On 24 February 2011 11:14, Corinna Vinschen wrote: > On Feb 24 11:56, Bengt Larsson wrote: >> I don't use surrogates. I only use UTF-8 and UTF-32. ... which of course means that you don't support anything but UTF-8 and ASCII locales. Can't argue with that, but you might want to use nl_langinfo(CODESET) to check and warn if something else is used. >> But using cygwin's >> wcwidth may be worth thinking about. I suppose it will be consistent >> with mintty that way; otherwise not? > > Yes, I think Andy uses the system functions as well. Yep, as should any other terminal emulator. Andy -- 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: GNUPLOT in Cygwin: Terminal type set to 'unknown'
There is lots of additional good gnuplot info on the WWW. Fast answer: gnuplot> set terminal dumb Terminal type set to 'dumb' Options are 'feed size 79, 24' gnuplot> plot sin(x) A (crude) graph of sin(x) should now be on the terminal screen, or if you're using X, then it will appear in an X window. Keith -- 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: License conflicts in Cygwin
On 02/24/2011 03:22 AM, Corinna Vinschen wrote: > Disclaimer: IANAL. I can't speak for our legal dept, of course. There > won't be any changes in the Cygwin license any time soon as far as I'm > aware. If your lawyers feel that they have more questions about this, > the best course of action might be to contact Red Hat and discuss this > problem with our legal dept. Also, the cygwin-licensing list is a better place to discuss these questions. -- Eric Blake ebl...@redhat.com+1-801-349-2682 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
Re: Mg3a - a version of Mg2a developed on Cygwin
On 02/24/2011 04:50 AM, Corinna Vinschen wrote: > On Feb 24 12:19, Bengt Larsson wrote: >> Bengt Larsson wrote: >>> I don't use surrogates. I only use UTF-8 and UTF-32. But using cygwin's >>> wcwidth may be worth thinking about. I suppose it will be consistent >>> with mintty that way; otherwise not? >> >> And: is wcwidth always available in modern Unices? How do you find out >> these things? I mean practically available. > > wcwidth and wcswidth are XSI extensions, so they are optional. As for > finding out, that's usally nicely done by autoconf'ing your project. And if you don't mind [L]GPL licensing, gnulib provides a source code replacement that guarantees wide character support on all modern porting platforms (particularly useful for mingw, which is sorely lacking on this front); and is currently working on introducing a wwchar_t type that is guaranteed to be UTF-32 even on cygwin (this is how coreutils gets wide character support for things like wc). Portions of that gnulib code are incorporated into libunistring. But from the sounds of your program's license, I'm not sure you can take advantage of gnulib or libunistring. -- Eric Blake ebl...@redhat.com+1-801-349-2682 Libvirt virtualization library http://libvirt.org signature.asc Description: OpenPGP digital signature
Re: Please test latest developer snapshot
On 17 February 2011 07:04, Corinna Vinschen wrote: > Apart from your testing and our fixing of obvious bugs, the other item > holding up the release of Cygwin 1.7.8 is the imminent release of > Service Pack 1 for Windows 7. It seems unwise to release a new Cygwin > package just minutes before a Service Pack comes out. Given the latest > experience that even monthly fixes can come with a nice, hidden gift, I > rather wait for a couple of days and test with SP1 first. Just a heads up, I've been testing the latest snapshot on Win7SP1 x64 and have not encountered any issues as of yet in my day-to-day use. Chris -- 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: Please test latest developer snapshot
On Feb 24 09:56, Chris Sutcliffe wrote: > On 17 February 2011 07:04, Corinna Vinschen wrote: > > Apart from your testing and our fixing of obvious bugs, the other item > > holding up the release of Cygwin 1.7.8 is the imminent release of > > Service Pack 1 for Windows 7. It seems unwise to release a new Cygwin > > package just minutes before a Service Pack comes out. Given the latest > > experience that even monthly fixes can come with a nice, hidden gift, I > > rather wait for a couple of days and test with SP1 first. > > Just a heads up, I've been testing the latest snapshot on Win7SP1 x64 > and have not encountered any issues as of yet in my day-to-day use. Thank you! I'm running SP1 32 and 64 bit for a couple of days now, too. But we all have different usage profiles so I appreciate to get this kind of feedback. If there's nothing else missing, I'm planning to release 1.7.8 on the weekend or early next week. 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: Mg3a - a version of Mg2a developed on Cygwin
Andy Koppe wrote: >On 24 February 2011 11:14, Corinna Vinschen wrote: >> On Feb 24 11:56, Bengt Larsson wrote: >>> I don't use surrogates. I only use UTF-8 and UTF-32. > >... which of course means that you don't support anything but UTF-8 >and ASCII locales. Can't argue with that, but you might want to use >nl_langinfo(CODESET) to check and warn if something else is used. Utf-8 and a number of 8-bit charsets, actually. I'm getting rather annoyed that people judge the program without looking at it. And it does use nl_langinfo(CODESET). >>> But using cygwin's >>> wcwidth may be worth thinking about. I suppose it will be consistent >>> with mintty that way; otherwise not? >> >> Yes, I think Andy uses the system functions as well. > >Yep, as should any other terminal emulator. I have fixed it to use Cygwin's wcswidth. -- 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: Please test latest developer snapshot
> Date: Thu, 24 Feb 2011 16:16:11 +0100 > From: corinna > Subject: Re: Please test latest developer snapshot > > On Feb 24 09:56, Chris Sutcliffe wrote: > > On 17 February 2011 07:04, Corinna Vinschen wrote: > > > Apart from your testing and our fixing of obvious bugs, the other item > > > holding up the release of Cygwin 1.7.8 is the imminent release of > > > Service Pack 1 for Windows 7. It seems unwise to release a new Cygwin > > > package just minutes before a Service Pack comes out. Given the latest > > > experience that even monthly fixes can come with a nice, hidden gift, I > > > rather wait for a couple of days and test with SP1 first. > > > > Just a heads up, I've been testing the latest snapshot on Win7SP1 x64 > > and have not encountered any issues as of yet in my day-to-day use. > > Thank you! I'm running SP1 32 and 64 bit for a couple of days now, too. > But we all have different usage profiles so I appreciate to get this > kind of feedback. > > If there's nothing else missing, I'm planning to release 1.7.8 on the > weekend or early next week. > Also great here Vista 32...lots of ssh, sftp, ssh port forwarding. Thanks for making it happen... ...Karl -- Problem reports: http://cygwin.com/problems.html FAQ: http://cygwin.com/faq/ Documentation: http://cygwin.com/docs.html Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Re: Please test latest developer snapshot
>> Please test latest developer snapshot Lots of perl builds and smokes passed with no new errors. -- Reini -- 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: Please test latest developer snapshot
Yes, good progress. A lot of those x64 Win7 issues don't appear anymore for me and I didn't had now for some time no more forking issues. Thanks, Kai -- 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: Mg3a - a version of Mg2a developed on Cygwin
Le 24/02/2011 19:50, Bengt Larsson a écrit : Utf-8 and a number of 8-bit charsets, actually. I'm getting rather annoyed that people judge the program without looking at it. And it does use nl_langinfo(CODESET). make install should copy mg to /bin instead of /docs/Command, copy documentation files in /usr/share/doc/mg3a and samples (dot files) in /us/share/doc/mg3a/examples v2$ echo $LANG en_US.UTF-8 v2$ mg M-x emacs-version Mg 2a (formerly MicroGnuEmacs) s/2/3/ no ? v2$ mg ^H a RET apropos: Segmentation fault uh! sigh, no ^X d (aka dired mode) by default ! well, I've tried w/o NO_DIRED and d_makename() needs to be rewritten a lot to handle dynamic comlumns sizing of gnu ls :-( to compile w/o NO_DIRED, in function fbackupfile in file fileio.c, replace : char *malloc(); by #define rename renamefile ^Z doesn't suspend ! ^X ^F doesn't complete :-( no M-T (transpose-words) M-x something say [Ambiguous] w/o listing possible solutions about defines : -DNO_BACKUP may be replaced by -DMAKEBACKUP=0, so, it is disabled by default and may be enable using (make-backup-files) if needed. as suggested, -DLF_DEFAULT should be defined -DNOTAB seems to work fine but no-tab-mode and nobom must be switched in keymap.c -DPREFIXREGION seems to work fine -DREGEX seems to work fine -DSCROLLBYONE seems to work fine Regards, Cyrille Lefevre -- mailto:cyrille.lefevre-li...@laposte.net -- 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: Mg3a - a version of Mg2a developed on Cygwin
forgot about make install :
install: strip installbin installdoc
PREFIX=/usr
#PREFIX=/usr/local
BINDIR=${PREFIX}/bin
DOCDIR=${PREFIX}/share/doc/mg3a
DOCFILES=README README.misc README.programmer README.reference \
orig/mgprog.doc orig/README orig/tutorial
SAMPDIR=${DOCDIR}/examples
SAMFILES=.mg .mg-cygwin .mg-xterm
installbin:
cp mg.exe /usr/local/bin
installdoc:
mkdir -p ${DOCDIR}/orig ${SAMPDIR}
for file in ${SAMFILES}; do cp bl/$${file}
${SAMPDIR}/dot$${file}; done
for file in ${DOCFILES}; do cp $${file} ${DOCDIR}/$${file}; done
Regards,
Cyrille Lefevre
--
mailto:cyrille.lefevre-li...@laposte.net
--
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: Mg3a - a version of Mg2a developed on Cygwin
Cyrille Lefevre wrote: Thanks for your informed criticism. But I haven't suggested it should be delivered with Cygwin. >make install should copy mg to /bin instead of /docs/Command, Yup >copy >documentation files in /usr/share/doc/mg3a and samples (dot files) >in /us/share/doc/mg3a/examples Yes. Thanks. > >v2$ echo $LANG >en_US.UTF-8 > >v2$ mg >M-x emacs-version >Mg 2a (formerly MicroGnuEmacs) Ah. Thanks. > >s/2/3/ no ? > >v2$ mg >^H a RET >apropos: Segmentation fault >uh! Old bug. Menitioned in the old documentation. Incredibly hairy code. > >sigh, no ^X d (aka dired mode) by default ! True. I never use it. I kind of philosophically disagree with it. >well, I've tried w/o NO_DIRED and d_makename() needs to be rewritten >a lot to handle dynamic comlumns sizing of gnu ls :-( It was good that it worked at all :-) There is also a NO_BACKUP #define. I don't guarantee what happens if you remove it. >to compile w/o NO_DIRED, in function fbackupfile in file fileio.c, replace : >char *malloc(); >by >#define rename renamefile Helpful. Thanks. > >^Z doesn't suspend ! I know. The very old code did this for a BSD system. But I have never figured out how to do this portably on a more modern system. Mentioned in the documentation. > >^X ^F doesn't complete :-( That would be a nice feature. > >no M-T (transpose-words) Hmm. Could be added I guess. > >M-x something say [Ambiguous] w/o listing possible solutions OK. It never did, actually. Of course we don't have to do everything Emacs did. > >about defines : >-DNO_BACKUP may be replaced by -DMAKEBACKUP=0, so, it is disabled by >default and may be enable using (make-backup-files) if needed. >as suggested, -DLF_DEFAULT should be defined If it were distributed with Cygwin I would certainly define LF_DEFAULT. I wouldn't do it all on my own, but certainly if it's a condition. >-DNOTAB seems to work fine but no-tab-mode and nobom must be switched in >keymap.c OH! Thanks. Fixed. >-DPREFIXREGION seems to work fine >-DREGEX seems to work fine I haven't touched those. >-DSCROLLBYONE seems to work fine OK. That was more thorough than I asked for ;-) But very helpful. Thanks. -- 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: Mg3a - a version of Mg2a developed on Cygwin
Cyrille Lefevre wrote: > >forgot about make install : Again Super-helpful. Thanks. -- 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: Mg3a - a version of Mg2a developed on Cygwin
One comment in-line... On Thu, Feb 24, 2011 at 22:47, Bengt Larsson wrote: > Cyrille Lefevre wrote: > > Thanks for your informed criticism. But I haven't suggested it should be > delivered with Cygwin. > >>make install should copy mg to /bin instead of /docs/Command, > > Yup > >>copy >>documentation files in /usr/share/doc/mg3a and samples (dot files) >>in /us/share/doc/mg3a/examples > > Yes. Thanks. > >> >>v2$ echo $LANG >>en_US.UTF-8 >> >>v2$ mg >>M-x emacs-version >>Mg 2a (formerly MicroGnuEmacs) > > Ah. Thanks. > >> >>s/2/3/ no ? >> >>v2$ mg >>^H a RET >>apropos: Segmentation fault >>uh! > > Old bug. Menitioned in the old documentation. Incredibly hairy code. > >> >>sigh, no ^X d (aka dired mode) by default ! > > True. I never use it. I kind of philosophically disagree with it. Strange, as "dired" is one of the most important pieces of emacs and when one says "emacs" and then says "but this version doesn't have 'dired'", the emacs person will go, "What?!" It's kInd of like having a kitchen sink with no running water :-) >>well, I've tried w/o NO_DIRED and d_makename() needs to be rewritten >>a lot to handle dynamic comlumns sizing of gnu ls :-( > > It was good that it worked at all :-) > > There is also a NO_BACKUP #define. I don't guarantee what happens if you > remove it. > >>to compile w/o NO_DIRED, in function fbackupfile in file fileio.c, replace : >>char *malloc(); >>by >>#define rename renamefile > > Helpful. Thanks. > >> >>^Z doesn't suspend ! > > I know. The very old code did this for a BSD system. But I have never > figured out how to do this portably on a more modern system. Mentioned > in the documentation. > >> >>^X ^F doesn't complete :-( > > That would be a nice feature. > >> >>no M-T (transpose-words) > > Hmm. Could be added I guess. >> >>M-x something say [Ambiguous] w/o listing possible solutions > > OK. It never did, actually. Of course we don't have to do everything > Emacs did. > >> >>about defines : >>-DNO_BACKUP may be replaced by -DMAKEBACKUP=0, so, it is disabled by >>default and may be enable using (make-backup-files) if needed. >>as suggested, -DLF_DEFAULT should be defined > > If it were distributed with Cygwin I would certainly define LF_DEFAULT. > I wouldn't do it all on my own, but certainly if it's a condition. > >>-DNOTAB seems to work fine but no-tab-mode and nobom must be switched in >>keymap.c > > OH! Thanks. Fixed. > >>-DPREFIXREGION seems to work fine >>-DREGEX seems to work fine > > I haven't touched those. > >>-DSCROLLBYONE seems to work fine > > OK. That was more thorough than I asked for ;-) But very helpful. > Thanks. -- 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
