Re: (from comp.emacs.xemacs) Shift with KP-Add?
Hi,
XFree86 broken the logic behind this bit of code in event-Xt.c:
/* If this key contains two distinct keysyms, that is,
shift generates a different keysym than the
non-shifted key, then don't apply the shift modifier
bit: it's implicit. Otherwise, if there would be no
other way to tell the difference between the shifted
and unshifted version of this key, apply the shift bit.
Non-graphics, like Backspace and F1 get the shift bit
in the modifiers slot. Neither the characters a,
A, 2, nor @ normally have the shift bit set.
However, F1 normally does. */
if (modifiers XEMACS_MOD_SHIFT)
{
int Mode_switch_p = *state xd-ModeMask;
KeySym bot = XLookupKeysym (ev, Mode_switch_p ? 2 : 0);
KeySym top = XLookupKeysym (ev, Mode_switch_p ? 3 : 1);
if (top bot top != bot)
modifiers = ~XEMACS_MOD_SHIFT;
}
They (and I imagine x.org, until its proven otherwise) are shipping with
keymaps that bind, for example,
derrick [ xmodmap -pke | grep XF86
keycode 63 = KP_Multiply XF86_ClearGrab
[...]
Shift with KP_Multiply to some keysym.
XLookupKeysym(event, 1) returns that keysym, while XLookupString(event, buf,
bufsize, keysym, status) with an event that describes a shifted
KP_Multiply keypress returns KP_Multiply in *keysym. Previously, these were
always identical.
Im sure there is some way to work around this within XEmacs, and its
probably going to be ugly and long, because we various input methods,
determined at compile time, that may or may not use XLookupString. Whee.
Dinos, you can edit your XF86Config file, add
Option HandleSpecialKeys Always
to the ServerFlags section, and add
xmodmap -pke | sed 's/XF86_.*$//g' | xmodmap -
to your X11 initialisation scripts. After that, you should be able to bind
shift plus any of the keypad keys to whatever you want. Note that xmodmap
command may break if you are using an obscure XKB layout; it wont for any I
have available to me.
Best regards,
- Aidan
--
I, for instance, am gung-ho about open source because my family is being
held hostage in Rob Maldas basement. But who fact-checks me, or Enderle,
when we say something in public? No-one! -- Danny OBrien
___
Devel mailing list
Devel@XFree86.Org
http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 4.4.0 RC3
Ar an 18ú lá de mí 2, scríobh David Dawes : Lets face it: Your real objection is to giving credit to XFree86 and its contributors. GPL-incompatibility and FUD about FSF-freeness(*) of the modified licence is just a poor excuse. I think it's unfair to assume that, David, especially since there have been severl reasoned disagreements with your position from people who have been active, useful contributors to XFree86. There have been almost no expressions of support for this change, and coherent objections from many of those whose contributions matter to the project. I'm surprised you're still going ahead with it. -- I don't care if it rains or freezes/'Long as I got my Plastic Jesus Riding on the dashboard of my car. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Files with wrong exec bits set
Ar an 21ú lá de mí 1, scríobh Marc Aurele La France : The problem with this is that the permissions might be reset the next time something is committed to the affected files. So, all committers would need to re-checkout after the permission changes are made, or change the permissions in their own copy. Really? As I understand it, the only way you can change the permissions on a file in a CVS repository is by going and chmod'ing the actual files in the master repository on disk, not by checking out, modifying, then checking in again. There are more recent versions of CVS that support a config directive to preserve execute permissions et al, but that tends not to be used, because of a view that it was buggy. -- I don't care if it rains of freezes/'Long as I got my Plastic Jesus Riding on the dashboard of my car. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: DPI with multiple heads and virtual desktops
Ar an 20ú lá de mí 8, scríobh Dr Andrew C Aitchison : We have a laptop with a 125dpi screen and a lecture room projector with about 8dpi. If I were to make it run a two screen desktop, That's almost the argument Charles Petzold makes for the general crapness in the DPI system in Win32, and it's fallacious. Practically no-one wants to run a two screen desktop in that situation; the laptop screen ends up facing the speaker, and the speaker ends up standing in front of the projection screen. No-one gets to see both screens; no-one wants to. The speaker might like to be able to have private notes available, but she also wants to be sure she knows exactly what her audience is seeing. -- These are the prettiest looking witnesses we have had in a long time. I imagine you are all married. If not, you could be if you wanted to be. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: autotooling xrandr
Ar an 13ú lá de mí 8, scríobh Egbert Eich : Bug #72 has not been committed as it is not yet clear what your final conclusions are. Perhaps a comment to that effect could have been added to the bug? Anyway, as I said, I don't have the free time any more. If anyone else wants to take that on, go for it, but if not, close it. -- These are the prettiest looking witnesses we have had in a long time. I imagine you are all married. If not, you could be if you wanted to be. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: autotooling xrandr
Ar an 12ú lá de mí 8, scríobh Harold L Hunt II : However, I wouldn't expect a lot of interest from others, as this gets mentioned every so often but the person suggesting it often gives up after they realize how large of a job it is. I would venture to say too that since the build system isn't that well understood by _anyone_, patches to it move to the back of the queue, and stay there. Cf, http://bugs.xfree86.org/show_bug.cgi?id=72 . And if attempts at minor patches are silently dropped, anyone whose long-term plan is to rework the entire build system is going to get discouraged. -- These are the prettiest looking witnesses we have had in a long time. I imagine you are all married. If not, you could be if you wanted to be. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Someone has re-implemented ucs2any.pl in C
Hi, In the interests of portability--their base system doesn't ship with perl--the NetBSD people have implemented ucs2any.pl in C. There's a version at http://backyard.homeunix.net:8080/~ben/ucs2any/ It's worth considering including this in the XFree86 tree, if the server-side re-encoding is a long way from being complete. Bye, - Aidan Kehoe -- Parhásárd; rex quondam Pokémonorum, rex futuram Pokémonorum. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [XJANITOR] [Q] : where to submit patches?
Ar an 2ú lá de mí 6, scríobh Egbert Eich : Aidan Kehoe writes: Ar an 2ú lá de mí 6, scríobh Egbert Eich : Also they seem to have difficulties to make attachments NB; this is not a badly-designed-user-interface issue; bugzilla on bugs.xfree86.org is _buggy_ with regard to creating patches. Maybe you have misunderstood me: I understood you; unfortunately what I was trying to say in my head didn't make it to the keyboard in one piece. I meant to say, bugzilla on bugs.xfree86.org is buggy with regard to creating attachments. If people put patches (that is, diff(1) output) into the comments field, it was frequently because creating attachments wasn't working for them. That said, perhaps this has been fixed lately; I haven't noticed as many people putting diff output into comments in the last few weeks. -- Parhásárd; rex quondam Pokémonorum, rex futuram Pokémonorum. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [XJANITOR] [Q] : where to submit patches?
Ar an 3ú lá de mí 6, scríobh Egbert Eich : Egbert Eich writes: Aidan Kehoe writes: Ar an 2ú lá de mí 6, scríobh Egbert Eich : Also they seem to have difficulties to make attachments NB; this is not a badly-designed-user-interface issue; bugzilla on bugs.xfree86.org is _buggy_ with regard to creating patches. [...] And I forgot to add: First people advocated that XFree86 has a bugzilla. Now we have one and people complain that it is broken. Bugzilla is great, it's a valuable tool, and thank you all for putting it in place. It certainly makes life easier for the rest of the world who don't have CVS access, and I suspect it makes life easier for you too. As someone who has put diff output into comment fields, though, I wanted to point out that people have had good reason for doing so. We weren't just trying to make your life more difficult, even if it sometimes seems that way. Our expertise is developing X not running a bugzilla. Where are the people with this expertise, the volunteers who step up and offer to help us to tweak it so it suits our needs best? Where is the community spirit? I definitely miss it here in this list. Okay, I'm a long way from being a Perl expert, but I can try; what version of Bugzilla is being used on that machine? Was it installed as a Debian package, or by hand? -- Parhásárd; rex quondam Pokémonorum, rex futuram Pokémonorum. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: [XJANITOR] [Q] : where to submit patches?
Ar an 2ú lá de mí 6, scríobh Egbert Eich : Also they seem to have difficulties to make attachments NB; this is not a badly-designed-user-interface issue; bugzilla on bugs.xfree86.org is _buggy_ with regard to creating patches. -- Parhásárd; rex quondam Pokémonorum, rex futuram Pokémonorum. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: Having trouble getting CVS to compile
Ar an 2ú lá de mí 6, scríobh Egbert Eich : I wonder why this problem has not surfaced before. Is png.h installed by default on all platforms we support. Not on FreeBSD, NetBSD or OpenBSD I believe. People ended up working out where to add PngLibDir and stuff, though. I wonder how long we can keep up providing a self contained build environment. Not too long, I suspect, which is good in some ways but bad in others. Forcing XFree86 to distribute zlib when most platforms on which it is used already have zlib is not a win. -- Parhásárd; rex quondam Pokémonorum, rex futuram Pokémonorum. ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 host.def file questions
Ar an 26ú lá de mí 3, scríobh Matthieu Herrb : I'll probably merge some of its informaion into the BUILD document in the XFree86 tree if people find it useful. That would be really useful. Also, defining HasParallelMake causes a obscure build failure for me on NetBSD 1.6P; it may be worth mentioning this in the docs so other people don't have to resort to binary search on customized host.defs :-) . -- I have heard the swelling cry of the English speaking peoples of the world, and it tells me their cause is served best by flaming the few complacent asses on usenet. -- T. Samant, 29 June 1997 ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: XFree86 4.2.99.902 (4.3.0 RC2) tagged
Just noticed; The RELNOTES need to have the line FreeType2 updated to version 2.0.6. under Client and Library Updates section removed, since the current FreeType version included is 2.1.1, and this is mentioned under the I18N and Font updates. Ar an 26ú lá de mí 2, scríobh Thomas Winischhofer : [..] -- I have heard the swelling cry of the English speaking peoples of the world, and it tells me their cause is served best by flaming the few complacent asses on usenet. -- T. Samant, 29 June 1997 ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
