Re: Japanese keyboard auto-detection

2003-10-07 Thread Takuma Murakami 
Alexander,

Thank you for supporting Japanese keyboards.
It is really useful for us.

I have one request on this feature.  Could you change
the line
{  0x411, -1, "jp","jp",  NULL, NULL, "Japanese"},
to
{  0x411,  7, "jp","jp",  NULL, NULL, "Japanese"},
in winconfig.c?  It prevents JP layouts loaded for JP
Windows with US keyboards.

Thanks in advance.

Takuma Murakami ([EMAIL PROTECTED])

Re: Weird keyboard behavior with "Caps Lock" key

2003-10-07 Thread Takuma Murakami 
> Open "Regional and Language Option" in Control Panel.
> Add English as input language.
> After XFree86/Cygwin start, change language to English using
> Shift+Alt key.
> 
> Doesn't this help you?

It surely works on my machine, both by Control Panel
and by the function LoadKeyboardLayout.  Thank you for
the excellent solution.

Takuma Murakami ([EMAIL PROTECTED])

Re: Mississippi -> Miiippi

2003-10-07 Thread Dai Itasaka 
Additional information.

This weird behavior can only be observed in an xterm with bash.
If I invoke it by "xterm -e tcsh" then no problem. If I do
"xterm -e bash" (or without -e bash) then no 's' allowed at
the prompt. I can't type nor paste.

The stdout still works so that I do see all the 's'es in
a command output. But not at the shell prompt. The bash shell
prompt.

Re: Mississippi -> Miiippi

2003-10-07 Thread Dai Itasaka 
I have no intention to secure the X connection.
I use ssh simply because the remote guy doesn't have a telnet server
running. Do I still need to use the -X option?


) By the way, you're using ssh all wrong. What you should really be doing is:
)
) 1) Invoke startxwin.sh
) 2) In the local xterm, verify that the value of DISPLAY is 127.0.0.1:0
) (and set it to that if it is not)
) 3) ssh to the remote box using the "-X" flag to enable X-forwarding.
) 4) Once connected to the remote host, verify that the value of DISPLAY
) is something like remotehost:8.
) 5) Run your remote X-clients normally.

Re: Mississippi -> Miiippi

2003-10-07 Thread Dai Itasaka 
I'm using Windows XP Professional. The "Regional and Language Options"
in the ControlPanel says:

  Regional Options tab:
Standards and formats: English(United States)
Location: United States
  Language tab:
Text Services and Input Languages: Japanese - MS Natural Input 2002 v8.1
  Advanced tab:
Language for non-Unicode programs: Japanese

I cannot live without doing that setxkbmap because otherwise I will be
in a bigger sh^H^H hole where the at mark becomes the double quotation,
the double quotation becomes the star, the star becomes the left parenthesis,
the left parenthesis becomes rightcrazy.


) What language is Windows using by default?
)
) You have, or course, tried this same demo (very carefully, I might add)
) to make sure that the same problem happens when you don't use setxkbmap?
)
) Harold
)
) Dai Itasaka wrote:
)
) > I did:
) >
) >  setxkbmap -rules xfree86 -model pc104 -layout us -option ""
) >
) > XWin was invoked without any option in startxwin.sh. (XWin &)
) >
) > The keyboard is a normal US keyboard. (101? It's from Dell)
) >
) >
) > ) Are you installing your own keymap?
) > )
) > ) Are you using an XF86Config file?
) > )
) > ) What keyboard layout is Windows configured for?
) > )
) > ) Harold
) > )
) > ) Dai Itasaka wrote:
) > )
) > ) > Hello list,
) > ) >
) > ) > Here is what I did:
) > ) >
) > ) > - Opened several tcsh windows (as separate MS Window apps)
) > ) > - Started X by invoking "startxwin.sh" which gave me one big root window
) > ) >   and one xterm window
) > ) > - In this xterm window, I did:
) > ) > > xhost 10.0.1.2
) > ) > > ssh [EMAIL PROTECTED]
) > ) > (now I'm logged in)
) > ) > > setenv DISPLAY 10.0.1.1:0
) > ) > (10.0.1.1 is the Windows PC with cygwin running, 10.0.1.2 is a Linux
) > box)
) > ) > > twm &
) > ) > (now the desktop is managed by twm)
) > ) > - Opened a few more xterm windows from twm and already opened xterm
) > ) > - Went back to one of the tcsh window and did:
) > ) > > setenv DISPLAY localhost:0
) > ) > > xterm
) > ) >
) > ) > This opened up one xterm window in the X desktop with "bash-2.05b"
prompt.
) > ) > In this xterm window, I couldn't type the letter 's'. Not only I
couldn't
) > ) > type, but I was unable to yank and copy a string with 's'. For example,
) > ) > I yanked a string "tcsh" in another xterm window and pasted it in this
) > ) > troubled xterm window, it displayed "tch". For another example, I yanked
) > ) > the word "Mississippi" from /usr/share/dict/words and pasted it and got
) > ) > "Miiippi". I had no such problem in any other xterm windows but this.
) > ) >
) > ) > What was happening?
) > ) >
) > ) >
) > ) >>uname -a
) > ) >
) > ) > CYGWIN_NT-5.1 myname 1.5.5(0.94/3/2) 2003-09-20 16:31 i686 unknown
unknown
) > ) > Cygwin
) > ) >
) > ) >
) > ) >

Re: Mississippi -> Miiippi

2003-10-07 Thread Thomas Chadwick 
By the way, you're using ssh all wrong.  What you should really be doing is:

1) Invoke startxwin.sh
2) In the local xterm, verify that the value of DISPLAY is 127.0.0.1:0 (and 
set it to that if it is not)
3) ssh to the remote box using the "-X" flag to enable X-forwarding.
4) Once connected to the remote host, verify that the value of DISPLAY is 
something like remotehost:8.
5) Run your remote X-clients normally.

From: "Dai Itasaka" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: <[EMAIL PROTECTED]>
Subject: Mississippi -> Miiippi
Date: Tue, 7 Oct 2003 10:56:06 -0700
Hello list,

Here is what I did:

- Opened several tcsh windows (as separate MS Window apps)
- Started X by invoking "startxwin.sh" which gave me one big root window
  and one xterm window
- In this xterm window, I did:
> xhost 10.0.1.2
> ssh [EMAIL PROTECTED]
(now I'm logged in)
> setenv DISPLAY 10.0.1.1:0
(10.0.1.1 is the Windows PC with cygwin running, 10.0.1.2 is a Linux 
box)
> twm &
(now the desktop is managed by twm)
- Opened a few more xterm windows from twm and already opened xterm
- Went back to one of the tcsh window and did:
> setenv DISPLAY localhost:0
> xterm

This opened up one xterm window in the X desktop with "bash-2.05b" prompt.
In this xterm window, I couldn't type the letter 's'. Not only I couldn't
type, but I was unable to yank and copy a string with 's'. For example,
I yanked a string "tcsh" in another xterm window and pasted it in this
troubled xterm window, it displayed "tch". For another example, I yanked
the word "Mississippi" from /usr/share/dict/words and pasted it and got
"Miiippi". I had no such problem in any other xterm windows but this.
What was happening?

>uname -a
CYGWIN_NT-5.1 myname 1.5.5(0.94/3/2) 2003-09-20 16:31 i686 unknown unknown
Cygwin
_
Share your photos without swamping your Inbox.  Get Hotmail Extra Storage 
today! http://join.msn.com/?PAGE=features/es

Re: Mississippi -> Miiippi

2003-10-07 Thread Harold L Hunt II 
Dai,

What language is Windows using by default?

You have, or course, tried this same demo (very carefully, I might add)
to make sure that the same problem happens when you don't use setxkbmap?

Harold

Dai Itasaka wrote:

> I did:
> 
>  setxkbmap -rules xfree86 -model pc104 -layout us -option ""
> 
> XWin was invoked without any option in startxwin.sh. (XWin &)
> 
> The keyboard is a normal US keyboard. (101? It's from Dell)
> 
> 
> ) Are you installing your own keymap?
> )
> ) Are you using an XF86Config file?
> )
> ) What keyboard layout is Windows configured for?
> )
> ) Harold
> )
> ) Dai Itasaka wrote:
> )
> ) > Hello list,
> ) >
> ) > Here is what I did:
> ) >
> ) > - Opened several tcsh windows (as separate MS Window apps)
> ) > - Started X by invoking "startxwin.sh" which gave me one big root window
> ) >   and one xterm window
> ) > - In this xterm window, I did:
> ) > > xhost 10.0.1.2
> ) > > ssh [EMAIL PROTECTED]
> ) > (now I'm logged in)
> ) > > setenv DISPLAY 10.0.1.1:0
> ) > (10.0.1.1 is the Windows PC with cygwin running, 10.0.1.2 is a Linux
> box)
> ) > > twm &
> ) > (now the desktop is managed by twm)
> ) > - Opened a few more xterm windows from twm and already opened xterm
> ) > - Went back to one of the tcsh window and did:
> ) > > setenv DISPLAY localhost:0
> ) > > xterm
> ) >
> ) > This opened up one xterm window in the X desktop with "bash-2.05b" prompt.
> ) > In this xterm window, I couldn't type the letter 's'. Not only I couldn't
> ) > type, but I was unable to yank and copy a string with 's'. For example,
> ) > I yanked a string "tcsh" in another xterm window and pasted it in this
> ) > troubled xterm window, it displayed "tch". For another example, I yanked
> ) > the word "Mississippi" from /usr/share/dict/words and pasted it and got
> ) > "Miiippi". I had no such problem in any other xterm windows but this.
> ) >
> ) > What was happening?
> ) >
> ) >
> ) >>uname -a
> ) >
> ) > CYGWIN_NT-5.1 myname 1.5.5(0.94/3/2) 2003-09-20 16:31 i686 unknown unknown
> ) > Cygwin
> ) >
> ) >
>

Re: Mississippi -> Miiippi

2003-10-07 Thread Dai Itasaka 
I did:

 setxkbmap -rules xfree86 -model pc104 -layout us -option ""

XWin was invoked without any option in startxwin.sh. (XWin &)

The keyboard is a normal US keyboard. (101? It's from Dell)


) Are you installing your own keymap?
)
) Are you using an XF86Config file?
)
) What keyboard layout is Windows configured for?
)
) Harold
)
) Dai Itasaka wrote:
)
) > Hello list,
) >
) > Here is what I did:
) >
) > - Opened several tcsh windows (as separate MS Window apps)
) > - Started X by invoking "startxwin.sh" which gave me one big root window
) >   and one xterm window
) > - In this xterm window, I did:
) > > xhost 10.0.1.2
) > > ssh [EMAIL PROTECTED]
) > (now I'm logged in)
) > > setenv DISPLAY 10.0.1.1:0
) > (10.0.1.1 is the Windows PC with cygwin running, 10.0.1.2 is a Linux
box)
) > > twm &
) > (now the desktop is managed by twm)
) > - Opened a few more xterm windows from twm and already opened xterm
) > - Went back to one of the tcsh window and did:
) > > setenv DISPLAY localhost:0
) > > xterm
) >
) > This opened up one xterm window in the X desktop with "bash-2.05b" prompt.
) > In this xterm window, I couldn't type the letter 's'. Not only I couldn't
) > type, but I was unable to yank and copy a string with 's'. For example,
) > I yanked a string "tcsh" in another xterm window and pasted it in this
) > troubled xterm window, it displayed "tch". For another example, I yanked
) > the word "Mississippi" from /usr/share/dict/words and pasted it and got
) > "Miiippi". I had no such problem in any other xterm windows but this.
) >
) > What was happening?
) >
) >
) >>uname -a
) >
) > CYGWIN_NT-5.1 myname 1.5.5(0.94/3/2) 2003-09-20 16:31 i686 unknown unknown
) > Cygwin
) >
) >

Re: Mississippi -> Miiippi

2003-10-07 Thread Harold L Hunt II 
Dai,

Are you installing your own keymap?

Are you using an XF86Config file?

What keyboard layout is Windows configured for?

Harold

Dai Itasaka wrote:

> Hello list,
> 
> Here is what I did:
> 
> - Opened several tcsh windows (as separate MS Window apps)
> - Started X by invoking "startxwin.sh" which gave me one big root window
>   and one xterm window
> - In this xterm window, I did:
> > xhost 10.0.1.2
> > ssh [EMAIL PROTECTED]
> (now I'm logged in)
> > setenv DISPLAY 10.0.1.1:0
> (10.0.1.1 is the Windows PC with cygwin running, 10.0.1.2 is a Linux box)
> > twm &
> (now the desktop is managed by twm)
> - Opened a few more xterm windows from twm and already opened xterm
> - Went back to one of the tcsh window and did:
> > setenv DISPLAY localhost:0
> > xterm
> 
> This opened up one xterm window in the X desktop with "bash-2.05b" prompt.
> In this xterm window, I couldn't type the letter 's'. Not only I couldn't
> type, but I was unable to yank and copy a string with 's'. For example,
> I yanked a string "tcsh" in another xterm window and pasted it in this
> troubled xterm window, it displayed "tch". For another example, I yanked
> the word "Mississippi" from /usr/share/dict/words and pasted it and got
> "Miiippi". I had no such problem in any other xterm windows but this.
> 
> What was happening?
> 
> 
>>uname -a
> 
> CYGWIN_NT-5.1 myname 1.5.5(0.94/3/2) 2003-09-20 16:31 i686 unknown unknown
> Cygwin
>

Mississippi -> Miiippi

2003-10-07 Thread Dai Itasaka 
Hello list,

Here is what I did:

- Opened several tcsh windows (as separate MS Window apps)
- Started X by invoking "startxwin.sh" which gave me one big root window
  and one xterm window
- In this xterm window, I did:
> xhost 10.0.1.2
> ssh [EMAIL PROTECTED]
(now I'm logged in)
> setenv DISPLAY 10.0.1.1:0
(10.0.1.1 is the Windows PC with cygwin running, 10.0.1.2 is a Linux box)
> twm &
(now the desktop is managed by twm)
- Opened a few more xterm windows from twm and already opened xterm
- Went back to one of the tcsh window and did:
> setenv DISPLAY localhost:0
> xterm

This opened up one xterm window in the X desktop with "bash-2.05b" prompt.
In this xterm window, I couldn't type the letter 's'. Not only I couldn't
type, but I was unable to yank and copy a string with 's'. For example,
I yanked a string "tcsh" in another xterm window and pasted it in this
troubled xterm window, it displayed "tch". For another example, I yanked
the word "Mississippi" from /usr/share/dict/words and pasted it and got
"Miiippi". I had no such problem in any other xterm windows but this.

What was happening?

>uname -a
CYGWIN_NT-5.1 myname 1.5.5(0.94/3/2) 2003-09-20 16:31 i686 unknown unknown
Cygwin

Re: -clipboard crash with large amount of text

2003-10-07 Thread Harold L Hunt II 
Kensuke,

Thanks for the patch.  I have released it as part of the 
XFree86-xserv-4.3.0-18 package.

Harold

Kensuke Matsuzaki wrote:

Harold,

I misunderstod Xutf8TextPropertyToTextList return value and meaning
of iCount. This attached patch will prevent crash.
To transfer large amount of text they use incrementally way called
INCR, so we need to support it to copy/paste large amount of text.
Kensuke Matsuzaki

Re: Xwin stackdump while logging into RH8 with KDE as window manager

2003-10-07 Thread Harold L Hunt II 
Alexander,

Egbert Eich has scheduled your patch to xkbcomp to be committed to CVS HEAD.

Harold

Harold L Hunt II wrote:

Alexander,

I have submitted this to XFree86 to get it in before the XFree86 4.4.0 
feature deadline in about two weeks:

http://bugs.xfree86.org/show_bug.cgi?id=768

Harold

Alexander Gottwald wrote:

Missing attachment :)

NP: Lacrimosa - Schakal



Index: xkbcomp.c
===
RCS file: /cvs/xc/programs/xkbcomp/xkbcomp.c,v
retrieving revision 3.19
diff -u -u -r3.19 xkbcomp.c
--- xkbcomp.c27 May 2003 22:27:07 -3.19
+++ xkbcomp.c7 Sep 2003 18:56:18 -
@@ -871,16 +871,30 @@
  * -- Branden Robinson
  */
 int outputFileFd;
+int binMode = 0;
+const char *openMode = "w";
 unlink(outputFile);
+#ifdef O_BINARY
+switch (outputFormat) {
+case WANT_XKM_FILE:
+binMode = O_BINARY;
+openMode = "wb";
+break;
+default:
+binMode = 0;
+break;
+}
+#endif
 outputFileFd= open(outputFile, O_WRONLY|O_CREAT|O_EXCL,
-S_IRUSR|S_IWUSR|S_IRGRP|S_IWGRP|S_IROTH|S_IWOTH);
+
S_IRUSR|S_IWUSR|S_IRGRP|S_IWGRP|S_IROTH|S_IWOTH|binMode);
 if (outputFileFd<0) {
 ERROR1("Cannot open \"%s\" to write keyboard description\n",
 outputFile);
 ACTION("Exiting\n");
 exit(1);
 }
-out= fdopen(outputFileFd, "w");
++out= fdopen(outputFileFd, openMode);
 /* end BR */
 if (out==NULL) {
 ERROR1("Cannot open \"%s\" to write keyboard description\n",

XFree86 Bugzilla - New Cygwin Xserver product added - Use for entering bugs

2003-10-07 Thread Harold L Hunt II 
All,

If you have any outstanding issues that you still want looked at, please 
go to http://bugs.xfree86.org/ and enter new bugs assigned to the 
"Cygwin Xserver" product.  That will automatically send me an email and 
allow me to track which issues are open, invalid, and fixed.

As it is right now we are not using any bug tracking system, so I expect 
that this will at least help me to stop forgetting open issues.

Waiting for those first few bugs to be entered...

Harold

Note: You can enter "enhancement" bugs for new feature requests.  This 
is perfectly allowable and encouraged.