Re: What is a good Windows Manager for cygwin/XFree86
Try $ openbox & or $ wmaker & both are at /usr/X11R6/bin/ or u may visit for gnome or kde http://cygnome.sourceforge.net/ http://kde-cygwin.sourceforge.net/ Cheers Biju --- Greg Freemyer <[EMAIL PROTECTED]> wrote: > I want to find a basic windows manager the supports: >resize, move, minimize, maximize > Seems like a pretty basic request, but I have tried twm, mwm, and fvwm2. > fvwm2 is the most functional for me, but it does not have min/max. > What windows manager provides the above in a cygwin/XFree86 env. > > Thanks > Greg > -- > Greg Freemyer __ Do you Yahoo!? SBC Yahoo! DSL - Now only $29.95 per month! http://sbc.yahoo.com
What is a good Windows Manager for cygwin/XFree86
I want to find a basic windows manager the supports: resize, move, minimize, maximize Seems like a pretty basic request, but I have tried twm, mwm, and fvwm2. fvwm2 is the most functional for me, but it does not have min/max. What windows manager provides the above in a cygwin/XFree86 env. Thanks Greg -- Greg Freemyer
Re: US-Intl keymap
--- Benjamin Riefenstahl <[EMAIL PROTECTED]> schrieb: > > Do I assume > > correctly that the defines use the Unicode encodings? > > Not in general. X11 keysyms are a bit older than Unicode. > But > keysyms are identical with Latin-1 for that range, so > anything below > 256 is also identical to Unicode. > > > For completeness I would need the Unicode code points > 0x2018 > > and 0x2019, which aren't defined as far as I can tell. > > My X11/keysymdef.h has these: > > #define XK_leftsinglequotemark > 0xad0 > #define XK_rightsinglequotemark > 0xad1 > #define XK_leftdoublequotemark > 0xad2 > #define XK_rightdoublequotemark > 0xad3 > . . . > #define XK_singlelowquotemark > 0xafd > #define XK_doublelowquotemark > 0xafe Ok, that allows me to make the keymap a bit more Windows-compatible. See attachment. Cheers Stefan __ Gesendet von Yahoo! Mail - http://mail.yahoo.de Logos und Klingeltöne fürs Handy bei http://sms.yahoo.de us_intl_win Description: us_intl_win
Re: Xfree issues under Windows 2000
Shut down the already running login manager with /etc/init.d/xdm stop (maybe this file is kalled kdm or gdm or how the login manager is called) start xdm in debug mode xdm -debug 10 -nodaemon Pardon my ignorance, but I think I've restarted this with the correct settings (I found kdm in /usr/bin/, and it seemed to respond to the stop and start commands). I have also attempted connecting using xwin, and as usual it didn't go through, so now, I ask embarrassed, where do I find the log files generated by kdm in debug mode? Thanks as always, Ken _ Add photos to your e-mail with MSN 8. Get 2 months FREE*. http://join.msn.com/?page=features/featuredemail
Re: Xfree issues under Windows 2000
Ken C wrote: > Yep, I tried -from with both dynamic and static IP addresses. I'm guessing > the xdm startup you're referring to is on the Linux box? I'm not sure how > to do that, as everything starts up automatically at boot right now. Shut down the already running login manager with /etc/init.d/xdm stop (maybe this file is kalled kdm or gdm or how the login manager is called) start xdm in debug mode xdm -debug 10 -nodaemon bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: US-Intl keymap
Hi Stefan, > --- Alexander Gottwald > <[EMAIL PROTECTED]> schrieb: >> in /usr/include/X11/keysymdef.h Stefan Heinzmann <[EMAIL PROTECTED]> writes: > I didn't have that installed, thanks for the hint. Do I assume > correctly that the defines use the Unicode encodings? Not in general. X11 keysyms are a bit older than Unicode. But keysyms are identical with Latin-1 for that range, so anything below 256 is also identical to Unicode. > For completeness I would need the Unicode code points 0x2018 > and 0x2019, which aren't defined as far as I can tell. My X11/keysymdef.h has these: #define XK_leftsinglequotemark 0xad0 #define XK_rightsinglequotemark0xad1 #define XK_leftdoublequotemark 0xad2 #define XK_rightdoublequotemark0xad3 . . . #define XK_singlelowquotemark 0xafd #define XK_doublelowquotemark 0xafe benny
Re: Xfree issues under Windows 2000
[output] looks normal. > lo: family=TCP/IP (0) addr=127.0.0.1 > eth0: family=TCP/IP (0) addr=192.168.0.101 and you tried with the -from 192.168.0.101 parameter? Have you checked if the xdm server reported any errors? You can start xdm with xdm -debug 10 to print out a lot of debugging messages. Yep, I tried -from with both dynamic and static IP addresses. I'm guessing the xdm startup you're referring to is on the Linux box? I'm not sure how to do that, as everything starts up automatically at boot right now. Thanks again, Ken _ Protect your PC - get McAfee.com VirusScan Online http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
Re: US-Intl keymap
--- Alexander Gottwald <[EMAIL PROTECTED]> schrieb: > On Fri, 20 Jun 2003, Stefan Heinzmann wrote: [...] > Thats beyond my knowledge. This is a topic for the real > xfree86 > mailing list: > http://www.xfree86.org/mailman/listinfo/xfree86/ Done. I attached a revised version of my new keymap file with some new comments and a changed name: us_intl_win I think this could serve as a basis for submission to the xfree project, unless there are some changes that result from the niggles I mentioned. Cheers Stefan __ Gesendet von Yahoo! Mail - http://mail.yahoo.de Logos und Klingeltöne fürs Handy bei http://sms.yahoo.de us_intl_win Description: us_intl_win
Dead key and mode shift key behaviour
The attachment is a question from the cygwin-xfree list which appears to be more appropriate for this list. I wanted to add another question to it: I noticed when working with the right Alt key as a mode-shift key that it matters whether Shift is pressed after or before the right Alt-key. In order to get the correct behaviour, I have to press the Alt key first, then the Shift key. The other way round leads to the Alt key getting ignored. This is different from how the keys behave under Windows. Is this intentional or is it a bug? Cheers Stefan __ Gesendet von Yahoo! Mail - http://mail.yahoo.de Logos und Klingeltöne fürs Handy bei http://sms.yahoo.de--- Begin Message --- On Fri, 20 Jun 2003, Stefan Heinzmann wrote: > There's a minor niggle left, however: Under Windows the > behaviour of the dead keys is somewhat different. When a dead > key is followed by a kepress with which it doesn't combine, > the character of the dead key is generated followed by the > character of the key pressed thereafter. For example if I > press the apostrophe ' followed by the letter p the result is > 'p. Under X the apostrophe is lost and just the p is printed. > If I press the apostrophe twice under Windows then two > apostrophes are emitted, whereas under X a single apostrophe > is emitted. Is there a way to fiddle with this behaviour > under X to make it work in the same fashion as under Windows? Thats beyond my knowledge. This is a topic for the real xfree86 mailing list: http://www.xfree86.org/mailman/listinfo/xfree86/ bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723--- End Message ---
Re: US-Intl keymap
On Fri, 20 Jun 2003, Stefan Heinzmann wrote: > There's a minor niggle left, however: Under Windows the > behaviour of the dead keys is somewhat different. When a dead > key is followed by a kepress with which it doesn't combine, > the character of the dead key is generated followed by the > character of the key pressed thereafter. For example if I > press the apostrophe ' followed by the letter p the result is > 'p. Under X the apostrophe is lost and just the p is printed. > If I press the apostrophe twice under Windows then two > apostrophes are emitted, whereas under X a single apostrophe > is emitted. Is there a way to fiddle with this behaviour > under X to make it work in the same fashion as under Windows? Thats beyond my knowledge. This is a topic for the real xfree86 mailing list: http://www.xfree86.org/mailman/listinfo/xfree86/ bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: US-Intl keymap
--- Alexander Gottwald <[EMAIL PROTECTED]> schrieb: > On Fri, 20 Jun 2003, Stefan Heinzmann wrote: > > entry in xkb/keymap/xfree86 as follows: > > I also added an entry to xkb/keymap.dir > > > But it doesn't seem to have the slightest effect on the > > keybord behaviour. Have you got an idea what could be > wrong? > > The best is to test it with xkbcomp > xkbcomp -xkm -m us_intl_sh /etc/X11/xkb/keymap/xfree86 > localhost:0.0 > > This will produce errors if something goes wrong. I've not > tested > to set the map via the configfile but with setxkbmap > us_intl_sh. Cool, now it works. A syntax error had slipped into us_intl_sh when I modified it according to your findings. Thanks a lot for your help! I don't want to think about how long it would have taken me to find out myself. There's a minor niggle left, however: Under Windows the behaviour of the dead keys is somewhat different. When a dead key is followed by a kepress with which it doesn't combine, the character of the dead key is generated followed by the character of the key pressed thereafter. For example if I press the apostrophe ' followed by the letter p the result is 'p. Under X the apostrophe is lost and just the p is printed. If I press the apostrophe twice under Windows then two apostrophes are emitted, whereas under X a single apostrophe is emitted. Is there a way to fiddle with this behaviour under X to make it work in the same fashion as under Windows? Cheers Stefan __ Gesendet von Yahoo! Mail - http://mail.yahoo.de Logos und Klingeltöne fürs Handy bei http://sms.yahoo.de
Re: US-Intl keymap
I had a similar strange problem with AltGr while having the following entries in .inputrc : set meta-flag On set convert-meta Off set output-meta On I entered those to be ableto have danish national characters displayed correctly in bash. The effect was that using xterm in a local xserver would not give me AltGr characters - it worked allthough in xdmcp session - why I have no idea The "fix" has been to comment out the meta-flag statement : #set meta-flag On set convert-meta Off set output-meta On Hereafter the xterm works as expected Med venlig hilsen / Regards Franz Wolfhagen
Re: US-Intl keymap
On Fri, 20 Jun 2003, Stefan Heinzmann wrote: > entry in xkb/keymap/xfree86 as follows: I also added an entry to xkb/keymap.dir > But it doesn't seem to have the slightest effect on the > keybord behaviour. Have you got an idea what could be wrong? The best is to test it with xkbcomp xkbcomp -xkm -m us_intl_sh /etc/X11/xkb/keymap/xfree86 localhost:0.0 This will produce errors if something goes wrong. I've not tested to set the map via the configfile but with setxkbmap us_intl_sh. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: US-Intl keymap
It doesn't work for me. I created a separate us_intl_sh file
in order not to upset the existing us_intl. I created a new
entry in xkb/keymap/xfree86 as follows:
// Stefan Heinzmann's version of a US-international keyboard
xkb_keymap "us_intl_sh" {
xkb_keycodes{ include "xfree86" };
xkb_types { include "default" };
xkb_compatibility { include "default" };
xkb_symbols { include "us(pc101)+us_intl_sh"};
xkb_geometry{ include "pc" };
};
I finally changed XF86Config as follows:
Option "XkbLayout" "us_intl_sh"
But it doesn't seem to have the slightest effect on the
keybord behaviour. Have you got an idea what could be wrong?
Cheers
Stefan
__
Gesendet von Yahoo! Mail - http://mail.yahoo.de
Logos und Klingeltöne fürs Handy bei http://sms.yahoo.de
Re: US-Intl keymap (was: Re: X server acting funny when displayingremote KDE session)
On Fri, 20 Jun 2003, Stefan Heinzmann wrote:
> Umm, the attachment seems to have been lost...
Silly me ;)
bye
ago
--
[EMAIL PROTECTED]
http://www.gotti.org ICQ: 126018723//
// $XFree86: xc/programs/xkbcomp/symbols/us_intl,v 1.4.4.1 2002/08/26 21:43:24 paulo
Exp $
//
// Dead-keys definition for a very simple US/ASCII layout.
// by Conectiva (http://www.conectiva.com.br)
// modified by Ricardo Y. Igarashi ([EMAIL PROTECTED])
// Added the following deadkeys, to make it truly international:
//
// dead_macron: on AltGr-minus
// dead_breve: on AltGr-parenleft
// dead_abovedot: on AltGr-period
// dead_abovering: on AltGr-0
// dead_doubleacute: on AltGr-equal (as quotedbl is already used)
// dead_caron: on AltGr-less (AltGr-shift-comma)
// dead_cedilla: on AltGr-comma
// dead_ogonek: on AltGr-semicolon
// dead_belowdot: on AltGr-underscore (AltGr-shift-minus)
// dead_hook: on AltGr-question
// dead_horn: on AltGr-plus (AltGr-shift-equal)
// dead_diaeresis: on AltGr-colon (Alt-shift-semicolon)
//
// those were already there:
// dead_grave
// dead_acute
// dead_circumflex
// dead_tilde
// dead_diaeresis
//
// modified again for Windows CP-1252 compatibility by ([EMAIL PROTECTED])
partial default alphanumeric_keys
xkb_symbols "basic" {
name[Group1]= "US/ASCII";
// Alphanumeric section
key {[dead_grave,dead_tilde]};
key {[1,exclam],[exclamdown,onesuperior]};
key {[2,at],[twosuperior]};
key {[3,numbersign],[threesuperior]};
key {[4,dollar],[currency,sterling]};
key {[5,percent],[EuroSign]};
key {[6,dead_circumflex],[onequarter,asciicircum]};
key {[7,ampersand],[onehalf]};
key {[8,asterisk],[threequarters]};
key {[9,parenleft]};
key {[0,parenright]};
key {[minus,underscore],[yen]};
key {[equal,plus],[multiply,division]};
key {[q,Q],[adiaeresis,Adiaeresis]};
key {[w,W],[aring,Aring]};
key {[e,E],[eacute,Eacute]};
key {[r,R],[registered]};
key {[t,T],[thorn,THORN]};
key {[y,Y],[udiaeresis,Udiaeresis]};
key {[u,U],[uacute,Uacute]};
key {[i,I],[iacute,Iacute]};
key {[o,O],[oacute,Oacute]};
key {[p,P],[odiaeresis,Odiaeresis]};
key {[bracketleft,braceleft],[guillemotleft]};
key {[bracketright,braceright],[guillemotright]};
key {[backslash,bar],[notsign,brokenbar]};
key {[a,A],[aacute,Aacute]};
key {[s,S],[ssharp,section]};
key {[d,D],[eth,ETH]};
key {[f,F]};
key {[g,G]};
key {[h,H]};
key {[j,J]};
key {[k,K]};
key {[l,L],[oslash,Oslash]};
key {[semicolon,colon],[paragraph,degree]};
key {[dead_acute,dead_diaeresis],[acute,diaeresis]};
key {[z,Z],[ae,AE]};
key {[x,X]};
key {[c,C],[copyright,cent]};
key {[v,V]};
key {[b,B]};
key {[n,N],[ntilde,Ntilde]};
key {[m,M],[mu]};
key {[comma,less],[ccedilla,Ccedilla]};
key {[period,greater]};
key {[slash,question],[questiondown]};
key {[Mode_switch,Multi_key]};
// End alphanumeric section
};
Re: US-Intl keymap (was: Re: X server acting funny when displaying remote KDE session)
--- Alexander Gottwald <[EMAIL PROTECTED]> schrieb: > On Fri, 20 Jun 2003, Stefan Heinzmann wrote: > > > Does the mapping in the attached file make sense? > > The entrys for no symbols were too much. I've removed them. > > See the attached file. A short test was ok (äñ© for alt-r + > qnc). Umm, the attachment seems to have been lost... Cheers Stefan __ Gesendet von Yahoo! Mail - http://mail.yahoo.de Logos und Klingeltöne fürs Handy bei http://sms.yahoo.de
Re: US-Intl keymap (was: Re: X server acting funny when displayingremote KDE session)
On Fri, 20 Jun 2003, Stefan Heinzmann wrote: > Does the mapping in the attached file make sense? The entrys for no symbols were too much. I've removed them. See the attached file. A short test was ok (äñ© for alt-r + qnc). bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: US-Intl keymap (was: Re: X server acting funny when displayingremote KDE session)
On Fri, 20 Jun 2003, Stefan Heinzmann wrote: > I tried that and it didn't work for some reason. I defined > the AltGr key combinations by modifying xkb/symbols/us_intl, > which I attach. I modified xkb/keymap/xfree86 to include a > us_intl_sh variant that pulls in my new file and modified > XF86Config to use this variant. But it hasn't changed from > before. Is there something I missed in installation? i'll take a look > That's the way how AltGr-combinations are defined, right? I > did that in the attached file. My question however was how to > define the dead-key combinations. How do I define for example > that the apostrophe followed by a lowercase c results in a > ccedille? I'm not sure. But most deadkeys should already produce what you want. Just set the symbol for the deadkey to dead_acute and in combination with c it will produce the ç. > I didn't have that installed, thanks for the hint. Do I > assume correctly that the defines use the Unicode encodings? I think yes. But I'm not 100% sure. > For completeness I would need the Unicode code points 0x2018 > and 0x2019, which aren't defined as far as I can tell. maybe you can add them to /usr/X11R6/lib/X11/XkeysymDB. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
Re: Custom icons + MouseUp fix
Hi Earle, The DLL hook is fairly straightforward to use, but is intrusive on the rest of a system, (MS don't really recommend using them!) MSDN however have lots of stuff on hooks e.g. http://msdn.microsoft.com/library/en-us/winui/WinUI/WindowsUserInterface/Win dowing/Hooks/AboutHooks.asp I've got one working in a separate DLL, but it isn't fit for public consumption and often goes bang! Harold's Morse program shows the potential power of hooks, and will really annoy any one within earshot if you have big woofers hanging on your pc! On using the standard Windoze cursors instead of the SW DIX one. Don't we have to use Hardware cursors to do this, or use Sprite Layer alternatives to the Pointer Layer routines in miDCInitialize(pScreen, &g_winPointerCursorFuncs)? Or are you proposing converting X cursors on the fly using something similar to the Icon convert and still use miPointerAbsoluteCursor calls to place them. How can we tell which X cursor is in play on a client? I must admit I'm a little green in this area and keep going round in circles going through the porting docs, making pennies drop! Luckily, unlike icons, there are only a finite number of standard X cursor shapes to deal with, so a map could be used for these perhaps? Colin
Re: US-Intl keymap (was: Re: X server acting funny when displaying remote KDE session)
--- Alexander Gottwald
<[EMAIL PROTECTED]> schrieb: > On Thu,
19 Jun 2003, Stefan Heinzmann wrote:
>
> > The right-hand Alt key is used as a shift-key to produce
> > alternate characters together with most of the other keys
> in
> > the same way as the AltGr key on german keyboards.
> > The left Alt key keeps is traditional meaning. Below are
> the
> > characters that can be produced using this method. The
> four
> > lines show the character unshifted, Shift, AltGr, and
> > AltGr-Shift.
>
> This is already defined. The right alt key should be
> defined
> as the Mode_switch key, which switches to the second (the
> Alt-Gr)
> mapping for keys.
I tried that and it didn't work for some reason. I defined
the AltGr key combinations by modifying xkb/symbols/us_intl,
which I attach. I modified xkb/keymap/xfree86 to include a
us_intl_sh variant that pulls in my new file and modified
XF86Config to use this variant. But it hasn't changed from
before. Is there something I missed in installation?
> >
> > 1234567890-=\`qwertyuiop[]asdfghjkl;'zxcvbnm,./
> > [EMAIL PROTECTED]&*()_+|~QWERTYUIOP{}ASDFGHJKL:"ZXCVBNM<>?
> > ¡²³¤¼½¾¥×¬ äåé®þüúíóö«»áßð ø¶´æ © ñµç ¿
> > ¹ £ ÷¦ ÄÅÉ ÞÜÚÍÓÖ Á§Ð Ø°¨Æ ¢ Ñ Ç
>
> > o How do I specify which keys a dead key combines with
> and
> > what the resulting character is for each of those
> > combinations?
>
> every symbol in the list has a symbolic name assigned.
> eg adiaresis (or something like that). For every column
> you have to create an entry
>
> key { [ row_1, row_2 ], [ row_3, row_4 ] };
>
> and substitute the row_x with the symbol names for the
> character
> in that row.
That's the way how AltGr-combinations are defined, right? I
did that in the attached file. My question however was how to
define the dead-key combinations. How do I define for example
that the apostrophe followed by a lowercase c results in a
ccedille?
> >
> > o Each character seems to have a symbolic name which I
> have
> > to use in the keymap (such as 'asciitilde'). Where is the
> > mapping between symbolic name and character code
> documented?
>
> in /usr/include/X11/keysymdef.h
I didn't have that installed, thanks for the hint. Do I
assume correctly that the defines use the Unicode encodings?
For completeness I would need the Unicode code points 0x2018
and 0x2019, which aren't defined as far as I can tell.
> > o The keys themselves also have symbolic names, where is
> the
> > mapping between key scan code and symbolic name
> documented?
>
> /etc/X11/xkb/keycodes/xfree86
>
> This is the mapping to the raw keyboard scancodes. But it's
> easier
> to take the us map and add the second mappings to the
> exising mappings
Does the mapping in the attached file make sense?
Cheers
Stefan
__
Gesendet von Yahoo! Mail - http://mail.yahoo.de
Logos und Klingeltöne fürs Handy bei http://sms.yahoo.de
us_intl_sh
Description: us_intl_sh
Re: Xfree issues under Windows 2000
On Thu, 19 Jun 2003, Ken C wrote: > Thanks again for the help - here's the result of the program (I'm assuming > you wanted me to post it): [output] looks normal. > lo: family=TCP/IP (0) addr=127.0.0.1 > eth0: family=TCP/IP (0) addr=192.168.0.101 and you tried with the -from 192.168.0.101 parameter? Have you checked if the xdm server reported any errors? You can start xdm with xdm -debug 10 to print out a lot of debugging messages. bye ago -- [EMAIL PROTECTED] http://www.gotti.org ICQ: 126018723
