Re: xterm doesn't open on start (was: checkX problems)
Christopher Faylor wrote: On Thu, Dec 03, 2009 at 12:25:14AM +0100, Lothar Brendel wrote: More information as promised, after getting the new run and checkX (run2) packages announced this morning. $ checkX -v run2 0.3.2 0.3.2 announced? I didn't get any such message, and setup still only offers 0.3.1-1 to me. http://cygwin.com/ml/cygwin-announce/2009-12/msg2.html http://cygwin.com/ml/cygwin/2009-12/msg00079.html Thanx. I had just focused on cygwin-xfree, but indeed run2 is more general. Ciao Lothar -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: X11R7.5 and C.UTF-8
On Dec 3 07:48, Andy Koppe wrote: 2009/12/3 Linda Walsh: C.UTF_8 doesn't exist. Well, guess what: it does in Cygwin 1.7, and it's the default locale. Not exactly. The default locale is C.UTF-8. You can also use C.UTF8 or C.utf-8 or C.utf8, but not C.UTF_8 or C.utf_8. Corinna -- Corinna Vinschen Please, send mails regarding Cygwin to Cygwin Project Co-Leader cygwin AT cygwin DOT com Red Hat -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: X11R7.5 and C.UTF-8
On Thu, 3 Dec 2009, Andy Koppe wrote: 2009/12/3 Linda Walsh: C.UTF_8 doesn't exist. ... You can't have C and UTF-8, because C means no encoding (default). UTF-8 IS an encoding, so they are mutually exclusive. From http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html, §7.2: The tables in Locale Definition describe the characteristics and behavior of the POSIX locale for data consisting entirely of characters from the portable character set and the control character set. For other characters, the behavior is unspecified. This means that characters 0..127 have to be treated as ASCII, but beyond that an implementation can do what it wants. And on Cygwin 1.7, plain C actually does imply UTF-8, which happily is backward-compatible with ASCII. That's an interpretation that so far hasn't been blessed by the standards people. Any discussion of this topic should mention that, as a caveat. ymmv -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: X11R7.5 and C.UTF-8
2009/12/3 Thomas Dickey: From http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html, §7.2: The tables in Locale Definition describe the characteristics and behavior of the POSIX locale for data consisting entirely of characters from the portable character set and the control character set. For other characters, the behavior is unspecified. This means that characters 0..127 have to be treated as ASCII, but beyond that an implementation can do what it wants. And on Cygwin 1.7, plain C actually does imply UTF-8, which happily is backward-compatible with ASCII. That's an interpretation that so far hasn't been blessed by the standards people. Any discussion of this topic should mention that, as a caveat. Fair point. It also means that apps are entitled to assume that C supports no more than ASCII, which is why Cygwin 1.7's default locale is C.UTF-8. A default locale setting based on the user's language selection would be better, but we don't have that (yet?). Andy -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: X11R7.5 and C.UTF-8
On Dec 3 13:16, Andy Koppe wrote:
2009/12/3 Thomas Dickey:
From
http://www.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap07.html,
§7.2:
The tables in Locale Definition describe the characteristics and
behavior of the POSIX locale for data consisting entirely of
characters from the portable character set and the control character
set. For other characters, the behavior is unspecified.
This means that characters 0..127 have to be treated as ASCII, but
beyond that an implementation can do what it wants. And on Cygwin 1.7,
plain C actually does imply UTF-8, which happily is
backward-compatible with ASCII.
That's an interpretation that so far hasn't been blessed by the standards
people. Any discussion of this topic should mention that, as a caveat.
Fair point. It also means that apps are entitled to assume that C
supports no more than ASCII, which is why Cygwin 1.7's default locale
is C.UTF-8. A default locale setting based on the user's language
selection would be better, but we don't have that (yet?).
Try the attached. Note: It has a hidden --testloop option...
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
#define WINVER 0x0600
#include stdio.h
#include windows.h
#include getopt.h
#define VERSION 1.0
extern char *__progname;
void version () __attribute__ ((noreturn));
void usage (FILE *, int) __attribute__ ((noreturn));
void
version ()
{
printf (%s (Cygwin) %s\n, __progname, VERSION);
exit (0);
}
void
usage (FILE * stream, int status)
{
fprintf (stream, \n\
Usage: %s [-suU] [-l LCID]\n\
\n\
Return POSIX LANG identifier corresponding to a locale, default is the\n\
system default locale\n\
Possible options are:\n\
\n\
-s, --system return LANG for the system's default locale\n\
-u, --userreturn LANG for the current user's default locale\n\
-l, --lcid LCID return LANG for the LCID given as argument\n\
-U, --UTF-8 always attach .UTF-8 to LANG\n\
-h, --helpthis text\n\
-V, --version print the version of %s and exit\n,
__progname, __progname);
exit (status);
}
struct option longopts[] = {
{system, no_argument, NULL, 's'},
{user, no_argument, NULL, 'u'},
{lcid, required_argument, NULL, 'l'},
{UTF-8, no_argument, NULL, 'U'},
{help, no_argument, NULL, 'h'},
{version, no_argument, NULL, 'V'},
{testloop, no_argument, NULL, 'T'},
{0, no_argument, NULL, 0}
};
char *opts = dsul:UhV;
int
getlocale (LCID lcid, bool utf, bool test)
{
UINT codepage;
char iso639[10];
char iso3166[10];
if (!GetLocaleInfo (lcid, LOCALE_IDEFAULTANSICODEPAGE | LOCALE_RETURN_NUMBER,
(char *) codepage, sizeof codepage)
|| !GetLocaleInfo (lcid, LOCALE_SISO639LANGNAME, iso639, 10)
|| !GetLocaleInfo (lcid, LOCALE_SISO3166CTRYNAME, iso3166, 10))
{
if (!test)
fprintf (stderr, %s: Non existant locale\n, __progname);
return 2;
}
if (utf)
codepage = 0;
if (test)
{
char cty[256];
char lang[256];
GetLocaleInfo (lcid, LOCALE_SENGCOUNTRY, cty, 256);
GetLocaleInfo (lcid, LOCALE_SENGLANGUAGE, lang, 256);
printf (0x%04x=\%s_%s\, %s (%s)\n, (unsigned) lcid, iso639, iso3166,
lang, cty);
}
else
printf (LANG=\%s_%s%s\\n, iso639, iso3166, codepage ? : .UTF-8);
return 0;
}
#define d(X) {X, #X}
struct dl {
LCTYPE t;
const char *s;
} dlist[] = {
d(LOCALE_SLONGDATE),
d(LOCALE_SSHORTDATE),
d(LOCALE_STIMEFORMAT),
d(LOCALE_SYEARMONTH),
d(LOCALE_S1159),
d(LOCALE_S2359),
d(LOCALE_SDAYNAME1),
d(LOCALE_SDAYNAME2),
d(LOCALE_SDAYNAME3),
d(LOCALE_SDAYNAME4),
d(LOCALE_SDAYNAME5),
d(LOCALE_SDAYNAME6),
d(LOCALE_SDAYNAME7),
d(LOCALE_SABBREVDAYNAME1),
d(LOCALE_SABBREVDAYNAME2),
d(LOCALE_SABBREVDAYNAME3),
d(LOCALE_SABBREVDAYNAME4),
d(LOCALE_SABBREVDAYNAME5),
d(LOCALE_SABBREVDAYNAME6),
d(LOCALE_SABBREVDAYNAME7),
d(LOCALE_SMONTHNAME1),
d(LOCALE_SMONTHNAME2),
d(LOCALE_SMONTHNAME3),
d(LOCALE_SMONTHNAME4),
d(LOCALE_SMONTHNAME5),
d(LOCALE_SMONTHNAME6),
d(LOCALE_SMONTHNAME7),
d(LOCALE_SMONTHNAME8),
d(LOCALE_SMONTHNAME9),
d(LOCALE_SMONTHNAME10),
d(LOCALE_SMONTHNAME11),
d(LOCALE_SMONTHNAME12),
d(LOCALE_SMONTHNAME13),
d(LOCALE_SABBREVMONTHNAME1),
d(LOCALE_SABBREVMONTHNAME2),
d(LOCALE_SABBREVMONTHNAME3),
d(LOCALE_SABBREVMONTHNAME4),
d(LOCALE_SABBREVMONTHNAME5),
d(LOCALE_SABBREVMONTHNAME6),
d(LOCALE_SABBREVMONTHNAME7),
d(LOCALE_SABBREVMONTHNAME8),
d(LOCALE_SABBREVMONTHNAME9),
d(LOCALE_SABBREVMONTHNAME10),
d(LOCALE_SABBREVMONTHNAME11),
d(LOCALE_SABBREVMONTHNAME12),
d(LOCALE_SABBREVMONTHNAME13),
{ 0, NULL }
};
int main (int argc, char **argv)
{
int opt;
LCID lcid = LOCALE_SYSTEM_DEFAULT;
bool utf = false;
bool test = false;
bool dates = false;
while ((opt = getopt_long (argc, argv, opts, longopts, NULL)) != EOF)
switch (opt)
{
1.7 - what's the right way to start X?
What is the recommended/preferred way to start X in 1.7? In 1.5 I used a modified version of startxwin.bat. And where do I put my .xinitrc/.xsession script? -- Fredrik Stax\ang | rot13: s...@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: 1.7 - what's the right way to start X?
On 12/03/2009 04:07 PM, Fredrik Staxeng wrote: What is the recommended/preferred way to start X in 1.7? In 1.5 I used a modified version of startxwin.bat. And where do I put my .xinitrc/.xsession script? What about startxwin.bat doesn't work for you? There shouldn't be differences between 1.5 and 1.7 here. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
cygwin-x xterm not compatible with windows 7?
Hi: I sent this post earlier this week and have not received any replies. If this is the wrong place to post this, please let me know where I should. Thanks Hi All: This is my first post here. I've never had a problem I couldn't fix with cygwin-x before. Here is the deal: I just bought a new PC with windows 7 64 bit, build number 7600, version 6.1. I downloaded a fresh install of cygwin and cannot get cygwin-x xterm running. Cygwin version is 1.7.0(0.218/5/3) I tried running the cygwin-x XWin Server shortcut command line from a cmd window to get the error output: C:\cygwin\bin\run.exe /usr/bin/startxwin.bat and see this: /usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0 this seems to be coming from this command in the batch file: :\Users\princessC:\cygwin\bin\\..\bin\run -p /usr/bin xterm -e /usr/bin/bash - usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0 If I kill the server and run the script again, I'll get a STATUS_ACCESS_VIOLATION error, indicating some sort of shared memory corruption. I then have to restart the PC. I checked to see if there was more than one cygwin1.dll in response to earlier posts about this error and there is only one. I tried turning off the windows firewall. That helps in other ways, because other cygwin network utilities, such as nslookup were blocked until I did that. I tried changing the display from 127.0.0.1 to the IP address of the machine. Basically, I have a fresh machine with windows 7 and a fresh install of cygwin and I can't get xterm to work. Anyone have any ideas? Or is this just a windows 7 thing, and I'll have to give up on cygwin-x for a while? BTW, other shortcuts in the cygwin-x start folder work, such as bitmap and xcalc, just not the Xwin server and xterm. Thanks in advance, George -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: 1.7 - what's the right way to start X?
Larry Hall (Cygwin X) reply-to-list-only-l...@cygwin.com writes: On 12/03/2009 04:07 PM, Fredrik Staxeng wrote: What is the recommended/preferred way to start X in 1.7? In 1.5 I used a modified version of startxwin.bat. And where do I put my .xinitrc/.xsession script? What about startxwin.bat doesn't work for you? There shouldn't be differences between 1.5 and 1.7 here. Well, I did not find it, so I assumed it had been replaced with something better. Something that a) does not pop up a command window and b) calls .xinitrc or something I have to admit I did not look at the Cygwin site before posting the question. I did so after, and saw the Cygwin/X section. -- Fredrik Stax\ang | rot13: s...@hcqngr.hh.fr This is all you need to know about vi: ESC : q ! RET -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: cygwin-x xterm not compatible with windows 7?
From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree- ow...@cygwin.com] On Behalf Of wgw...@sbcglobal.net Sent: Thursday, December 03, 2009 1:47 PM I sent this post earlier this week and have not received any replies. If this is the wrong place to post this, please let me know where I should. This is the place, but I don't know how many of us have tried using 64 bit Windows 7 yet. I know I haven't, but I'll offer advice anyway. (What's the smiley for evil leer?) I just bought a new PC with windows 7 64 bit, build number 7600, version 6.1. I downloaded a fresh install of cygwin and cannot get cygwin-x xterm running. Cygwin version is 1.7.0(0.218/5/3) I tried running the cygwin-x XWin Server shortcut command line from a cmd window to get the error output: C:\cygwin\bin\run.exe /usr/bin/startxwin.bat and see this: /usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0 this seems to be coming from this command in the batch file: :\Users\princessC:\cygwin\bin\\..\bin\run -p /usr/bin xterm -e /usr/bin/bash - usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0 ...implying that the server didn't start. If I kill the server and run the script again, I'll get a STATUS_ACCESS_VIOLATION error, indicating some sort of shared memory corruption. I then have to restart the PC. I checked to see if there was more than one cygwin1.dll in response to earlier posts about this error and there is only one. I tried turning off the windows firewall. That helps in other ways, because other cygwin network utilities, such as nslookup were blocked until I did that. I tried changing the display from 127.0.0.1 to the IP address of the machine. I believe the X server listens on 0.0.0.0, so that shouldn't make a difference. Basically, I have a fresh machine with windows 7 and a fresh install of cygwin and I can't get xterm to work. Anyone have any ideas? Or is this just a windows 7 thing, and I'll have to give up on cygwin-x for a while? BTW, other shortcuts in the cygwin-x start folder work, such as bitmap and xcalc, just not the Xwin server and xterm. How can xcalc work if the server doesn't start?! Please send your /var/log/XWin0.log and cygcheck.out (cygcheck -s -v -r cygcheck.out) as attachments in the hope that they will inspire. Thanks, Mike
RE: cygwin-x xterm not compatible with windows 7?
From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree- ow...@cygwin.com] On Behalf Of wgw...@sbcglobal.net Sent: Thursday, December 03, 2009 1:47 PM I sent this post earlier this week and have not received any replies. If this is the wrong place to post this, please let me know where I should. This is the right place, but it's possible none of us with time to spare has run on Windows 7 64 bit yet. I just bought a new PC with windows 7 64 bit, build number 7600, version 6.1. I downloaded a fresh install of cygwin and cannot get cygwin-x xterm running. Cygwin version is 1.7.0(0.218/5/3) I tried running the cygwin-x XWin Server shortcut command line from a cmd window to get the error output: C:\cygwin\bin\run.exe /usr/bin/startxwin.bat and see this: /usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0 this seems to be coming from this command in the batch file: :\Users\princessC:\cygwin\bin\\..\bin\run -p /usr/bin xterm -e /usr/bin/bash - usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0 ...implying that the server didn't start. Did you run as administrator? I checked to see if there was more than one cygwin1.dll in response to earlier posts about this error and there is only one. I tried turning off the windows firewall. That helps in other ways, because other cygwin network utilities, such as nslookup were blocked until I did that. I tried changing the display from 127.0.0.1 to the IP address of the machine. I believe the X server listens on 0.0.0.0, so that shouldn't make a difference. Basically, I have a fresh machine with windows 7 and a fresh install of cygwin and I can't get xterm to work. Anyone have any ideas? Or is this just a windows 7 thing, and I'll have to give up on cygwin-x for a while? BTW, other shortcuts in the cygwin-x start folder work, such as bitmap and xcalc, just not the Xwin server and xterm. How can xcalc work if the server doesn't start?! Please send your /var/log/XWin0.log and cygcheck.out (cygcheck -s -v -r cygcheck.out) as attachments in the hope that they will inspire. Thanks, Mike
FW: cygwin-x xterm not compatible with windows 7?
From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree- ow...@cygwin.com] On Behalf Of wgw...@sbcglobal.net Sent: Thursday, December 03, 2009 1:47 PM I sent this post earlier this week and have not received any replies. If this is the wrong place to post this, please let me know where I should. This is the right place, but it's possible none of us with time to spare has run on Windows 7 64 bit yet. I just bought a new PC with windows 7 64 bit, build number 7600, version 6.1. I downloaded a fresh install of cygwin and cannot get cygwin-x xterm running. Cygwin version is 1.7.0(0.218/5/3) I tried running the cygwin-x XWin Server shortcut command line from a cmd window to get the error output: C:\cygwin\bin\run.exe /usr/bin/startxwin.bat and see this: /usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0 this seems to be coming from this command in the batch file: :\Users\princessC:\cygwin\bin\\..\bin\run -p /usr/bin xterm -e /usr/bin/bash - usr/bin/xterm Xt error: Can't open display: 127.0.0.1:0.0 ...implying that the server didn't start. Did you run as administrator? I checked to see if there was more than one cygwin1.dll in response to earlier posts about this error and there is only one. I tried turning off the windows firewall. That helps in other ways, because other cygwin network utilities, such as nslookup were blocked until I did that. I tried changing the display from 127.0.0.1 to the IP address of the machine. I believe the X server listens on 0.0.0.0, so that shouldn't make a difference. Basically, I have a fresh machine with windows 7 and a fresh install of cygwin and I can't get xterm to work. Anyone have any ideas? Or is this just a windows 7 thing, and I'll have to give up on cygwin-x for a while? BTW, other shortcuts in the cygwin-x start folder work, such as bitmap and xcalc, just not the Xwin server and xterm. How can xcalc work if the server doesn't start?! Please send your /var/log/XWin0.log and cygcheck.out (cygcheck -s -v -r cygcheck.out) as attachments in the hope that they will inspire. Thanks, Mike
Re: cygwin-x xterm not compatible with windows 7?
On Thu, Dec 3, 2009 at 3:22 PM, Mike Ayers mike_ay...@tvworks.com wrote: This is the right place, but it's possible none of us with time to spare has run on Windows 7 64 bit yet. I'm running Windows 7 Professional, 64-bit. I have been using Cygwin 1.7 with latest X, etc. for some time without any problems. I haven't done anything special, so I haven't run into any of the same problems as the OP. - Jim -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: xterm doesn't open on start
Timares, Brian (Patriot) wrote: Any other ideas? I keep updating but so far all I can do is launch an Xterm manually and clean up, then everything seems fine til the next time I relaunch it. --- Do you have DISPLAY=:0 set in your Windows environment? (system properties, Advanced, Env Vars). I put mine in the System Environment so it's there no matter how I'm logged in. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
RE: FW: cygwin-x xterm not compatible with windows 7?
From: cygwin-xfree-ow...@cygwin.com [mailto:cygwin-xfree- ow...@cygwin.com] On Behalf Of Christopher Faylor You really only need to send this type of thing once. Three times is overkill. The first two came back to me from cygwin-xfree-retur...@cygwin.com addresses with the first part garbled, so I thought they were mangled by my mailer and not getting sent to the list. Apologies for the inconvenience - still not sure what happened. Mike
RE: xterm doesn't open on start
Linda Walsh wrote: Timares, Brian (Patriot) wrote: Any other ideas? I keep updating but so far all I can do is launch an Xterm manually and clean up, then everything seems fine til the next time I relaunch it. Do you have DISPLAY=:0 set in your Windows environment? I didn't, but I do now. I am forced to use Outlook so I forwarded the more extensive email to my personal account so I can edit it more easily/correctly and because my work got pretty busy. I reverted to 1.5 to see if that would work better, it doesn't really, so I'll try to install 1.7 in parallel when I get a chance (I have servers doing things now so I have to let it alone for awhile). I do appreciate all the terrific replies--I've been on the net for awhile and this is one of the friendliest lists I've been on. Brian Timares oh and then there is the 7-year-old, he is taking lots of time :) -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: xterm doesn't open on start
On 12/03/2009 10:47 PM, Timares, Brian (Harris Corp.) wrote: I do appreciate all the terrific replies--I've been on the net for awhile and this is one of the friendliest lists I've been on. Do you mind if I frame this and hang it on the Cygwin home page. ;-) -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: X11R7.5 and C.UTF-8
Thomas Dickey dickey at his.com writes: This means that characters 0..127 have to be treated as ASCII, but No, it means that portable characters and control characters must be 128. ASCII meets this characteristic, but so does EBCDIC, as well as UTF-8. The C locale also implies that you can manipulate bytes = 128 in the naive manner, so long as you don't care about characters embedded in those bytes. And what do you know - ASCII, EBCDIC, and UTF-8 all meet this property, too. beyond that an implementation can do what it wants. And on Cygwin 1.7, plain C actually does imply UTF-8, which happily is backward-compatible with ASCII. That's an interpretation that so far hasn't been blessed by the standards people. Any discussion of this topic should mention that, as a caveat. Actually, the standards people HAVE spoken - and they agreed with our interpretation. POSIX was INTENTIONALLY written with the intent that a UTF-8 encoding is valid for the C locale, for the same reason that it was written that an EBCDIC encoding is valid for the C locale. These emails from the Austin Group (the folks that write POSIX) are telling: https://www.opengroup.org/sophocles/show_mail.tpl? CALLER=show_archive.tplsource=Llistname=austin-group-lid=12982 https://www.opengroup.org/sophocles/show_mail.tpl? CALLER=show_archive.tplsource=Llistname=austin-group-lid=13012 But they also admitted that there is still more work needed in POSIX to make this intent clearly codified (for example, that control characters must be single bytes 128). -- Eric Blake -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: cygwin-x xterm not compatible with windows 7?
wgw...@sbcglobal.net wrote: Hi: I sent this post earlier this week and have not received any replies. If this is the wrong place to post this, please let me know where I should. Thanks Hi All: This is my first post here. I've never had a problem I couldn't fix with cygwin-x before. Here is the deal: I just bought a new PC with windows 7 64 bit, build number 7600, version 6.1. I downloaded a fresh install of cygwin and cannot get cygwin-x xterm running. Cygwin version is 1.7.0(0.218/5/3) I tried running the cygwin-x XWin Server shortcut command line from a cmd window to get the error output: C:\cygwin\bin\run.exe /usr/bin/startxwin.bat try this -- edit /usr/bin/startxwin.bat and put a 5 second sleep between the call to Xwin and the call to xterm, and see what happens -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
