This may or may not be useful, but with altivec you can print the
vector registers as such:
(gdb) p $v1
$1 = {
uint128 = 0x7fffdead7fffdead7fffdead7fffdead,
v4_float = {nan(0x7fdead), nan(0x7fdead), nan(0x7fdead), nan(0x7fdead)},
v4_int32 = {2147475117, 2147475117, 2147475117, 2147475117},
On Monday, 09 May 2005, at 20:33:33 (-0400),
Mike Frysinger wrote:
i'm hoping someone out there can help since i'm really not familiar
with deadkeys at all ...
basically, after upgrading eterm from 0.9.2 to 0.9.3, this user's
deadkeys stopped working properly. downgrading libast to 0.5 and
On Tuesday 10 May 2005 03:03 pm, Michael Jennings wrote:
On Monday, 09 May 2005, at 20:33:33 (-0400),
Mike Frysinger wrote:
i'm hoping someone out there can help since i'm really not familiar
with deadkeys at all ...
basically, after upgrading eterm from 0.9.2 to 0.9.3, this user's
On Tuesday, 10 May 2005, at 20:35:38 (-0400),
Mike Frysinger wrote:
for any other distribution maintainers, you can grab the patch which applies
against 0.9.3 here:
http://viewcvs.gentoo.org/x11-terms/eterm/files/eterm-0.9.3-deadkeys.patch
Please note that only the last hunk of this patch
i'm hoping someone out there can help since i'm really not familiar with
deadkeys at all ...
basically, after upgrading eterm from 0.9.2 to 0.9.3, this user's deadkeys
stopped working properly. downgrading libast to 0.5 and then building eterm
0.9.3 against that seemed to have no effect
Mike / Tobias,
I don't use deadkeys myself, being American and only speaking
programming languages, but after a few minutes of Googling I would guess
that it started here:
Commit by mej :: eterm/Eterm/ (ChangeLog configure.in):
Mon Apr 18 16:00:22 2005 Michael Jennings (mej)
Remove
