Am Fri, 27 Aug 2010 08:40:39 +1000
schrieb Peter Hutterer peter.hutte...@who-t.net:
like /dev/input/mice?
Kind of, but on steroids. Also in the concept I'm thinking of here,
access to individual devices wasn't impossible. But you'd normally not
need it.
It only made sense in combination with
On 17:04 Thu 26 Aug , Glynn Clements wrote:
Wolfgang Draxinger wrote:
Which brings me to something I always wondered about: Why is there
no X pendant for screen (or I'm not aware of it)? I.e. some proxy X
server, opening an additional display passing through X
transparently,
On Wed, Aug 25, 2010 at 5:45 PM, Wolfgang Draxinger
wdraxinger.maill...@draxit.de wrote:
On Thu, 26 Aug 2010 08:44:46 +1000
Peter Hutterer peter.hutte...@who-t.net wrote:
Also, assuming that if we ditched input features somehow Gallium or
other graphics parts would be finished sooner is a
Donnie Berkholz wrote:
Which brings me to something I always wondered about: Why is there
no X pendant for screen (or I'm not aware of it)? I.e. some proxy X
server, opening an additional display passing through X
transparently, keeping record of prerequisite resources.
Am Fri, 27 Aug 2010 08:50:33 -0700
schrieb Corbin Simpson mostawesomed...@gmail.com:
Peter's been working solely on input handling and the XInput 2 stuff
since he got started. If you want more work put into Gallium, you
should find people like Marek, Luca, or me, that currently work on
Wolfgang Draxinger wdraxinger.maill...@draxit.de writes:
I'm one of those who's work would be severely disrupted by a hardwired
CTRL-ALT-Backspace Zap. CTRL-ALT-Backspace is hardwired in my fingers
from nearly 30 years of editing using Emacs and kin.
Just curious here, and don't want to
On Thu, 26 Aug 2010 16:25:04 +0900
Miles Bader mi...@gnu.org wrote:
(...)
Only instead, it kills your X server... :(
Ouch...
Well, using Vim (and I preferably in uxterm) one is kind of protected
from loosing changes by putting things into a screen session (but of
course all the other
On Thu, Aug 26, 2010 at 5:16 AM, Wolfgang Draxinger
wdraxinger.maill...@draxit.de wrote:
On Thu, 26 Aug 2010 16:25:04 +0900
Miles Bader mi...@gnu.org wrote:
(...)
Only instead, it kills your X server... :(
Ouch...
Well, using Vim (and I preferably in uxterm) one is kind of protected
On Thu, Aug 26, 2010 at 04:50:18PM +0200, ext Alex Deucher wrote:
On Thu, Aug 26, 2010 at 5:16 AM, Wolfgang Draxinger
wdraxinger.maill...@draxit.de wrote:
On Thu, 26 Aug 2010 16:25:04 +0900
Miles Bader mi...@gnu.org wrote:
(...)
Only instead, it kills your X server... :(
Ouch...
Wolfgang Draxinger wrote:
Which brings me to something I always wondered about: Why is there no X
pendant for screen (or I'm not aware of it)? I.e. some proxy X server,
opening an additional display passing through X transparently, keeping
record of prerequisite resources.
Because it's
On Thu, 26 Aug 2010 12:20:31 +1000
Peter Hutterer peter.hutte...@who-t.net wrote:
uhm. hotplugging works in that the X server receives an event when a
device was added by the kernel. Then it opens the device file.
See, that's exactly what I meant: There's extra work to be done by X,
or any
On Thu, Aug 26, 2010 at 06:59:48PM +0200, Wolfgang Draxinger wrote:
On Thu, 26 Aug 2010 12:20:31 +1000
Peter Hutterer peter.hutte...@who-t.net wrote:
uhm. hotplugging works in that the X server receives an event when a
device was added by the kernel. Then it opens the device file.
See,
On Tue, 24 Aug 2010 20:19:05 +0200
Julien Cristau jcris...@debian.org wrote:
This is not true. The sequence was removed from the default xkb map,
and can be turned back on with the appropriate xkb option, either in
xorg.conf or your desktop or your session startup scripts.
Well, this is a
On Tue, 24 Aug 2010 19:05:42 +0100
Andrew Clayton and...@digital-domain.net wrote:
Don't worry. It's still there.
In some form, yes. However it can be disabled by
setxkbmap -option
Now there are situations in which you don't want users being able to
disable the Zap, but also don't want the
On Tue, 24 Aug 2010 13:33:03 -0400 (EDT)
Patrick O'Donnell p...@ascent.com wrote:
I'm one of those who's work would be severely disrupted by a hardwired
CTRL-ALT-Backspace Zap. CTRL-ALT-Backspace is hardwired in my fingers
from nearly 30 years of editing using Emacs and kin.
Just curious
On Wed, 25 Aug 2010 09:07:16 +1000
Peter Hutterer peter.hutte...@who-t.net wrote:
re:xmodmap, the following may be interesting reading
http://who-t.blogspot.com/2010/06/keyboard-configuration-its-complicated.html
Educational indeed. However I hate relying on desktop environments and
their
Sorry guys,
I just took notice, that my replies missed the CC to the maillist (my
failure, I messed up my MUAs configuration). So those who now get
duplicates, due to the directly addressed replies, and now the CC, take
my apologies. But I prefer to CCs my answers here for the discussion
being
please tell a hardcore Vim user: What hotkey/command of Emacs collides
See: http://www.foldr.org/~michaelw/log/programming/lisp/dontzap-emacs
Pat
---
On Wed, Aug 25, 2010 at 12:14 PM, Wolfgang Draxinger
wdraxinger.maill...@draxit.de wrote:
On Tue, 24 Aug 2010 13:33:03 -0400 (EDT)
On 2010/08/25 19:13 (GMT+0200) Wolfgang Draxinger composed:
On Tue, 24 Aug 2010 20:19:05 +0200
No related xorg.conf option has been removed.
I beg to differ: ServerFlags Option DontZap off is no longer
interpreted (on my system).
Did you try it correctly quoted?
Section ServerFlags
On Wed, Aug 25, 2010 at 07:13:39PM +0200, Wolfgang Draxinger wrote:
On Tue, 24 Aug 2010 20:19:05 +0200
Julien Cristau jcris...@debian.org wrote:
This is not true. The sequence was removed from the default xkb map,
and can be turned back on with the appropriate xkb option, either in
On Wed, Aug 25, 2010 at 07:14:15PM +0200, Wolfgang Draxinger wrote:
On Wed, 25 Aug 2010 09:07:16 +1000
Peter Hutterer peter.hutte...@who-t.net wrote:
re:xmodmap, the following may be interesting reading
http://who-t.blogspot.com/2010/06/keyboard-configuration-its-complicated.html
On Thu, 26 Aug 2010 08:44:46 +1000
Peter Hutterer peter.hutte...@who-t.net wrote:
Then you get to either fix the scripts or fix your DE. No-one really
cares _what_ desktop environment you're running and one is as good as
the other. The one developers are running themselves naturally get
more
On Thu, Aug 26, 2010 at 02:45:51AM +0200, Wolfgang Draxinger wrote:
On Thu, 26 Aug 2010 08:44:46 +1000
Peter Hutterer peter.hutte...@who-t.net wrote:
Then you get to either fix the scripts or fix your DE. No-one really
cares _what_ desktop environment you're running and one is as good as
Peter Hutterer peter.hutte...@who-t.net writes:
On Thu, Aug 26, 2010 at 02:45:51AM +0200, Wolfgang Draxinger wrote:
[...]
I this particular case: I'm system administrator at my university's
student computer lab. Some students tend to lock their sessions,
(override-)configuring
Hi,
as you might know, Zapping the Xorg server by means of
CTRL+ALT+BACKSPACE has been first disabled by default, and later on
the xorg.conf option went away, too.
It is still possible to
setxkbmap -option terminate:ctrl_alt_bks
somewhere in the startup/init scripts to reenable, but I wonder
Date: Tue, 24 Aug 2010 18:08:55 +0200
From: Wolfgang Draxinger wdraxinger.maill...@draxit.de
...
CTRL, ALT and BACKSPACE however are present and behave the same on every
keyboard (I know of, which are plenty).
So, could we please bring back the static configuration for zapping
the X server by
On Tue, Aug 24, 2010 at 18:08:55 +0200, Wolfgang Draxinger wrote:
Hi,
as you might know, Zapping the Xorg server by means of
CTRL+ALT+BACKSPACE has been first disabled by default, and later on
the xorg.conf option went away, too.
This is not true. The sequence was removed from
On Tue, 24 Aug 2010 18:08:55 +0200, Wolfgang Draxinger wrote:
Frankly, I don't see any sane reason, why it was removed in the first
place. Disabling it by default, okay I can live with that. But taking
away the option alltogether: Not good.
Don't worry. It's still there.
If your using gnome,
On Tue, Aug 24, 2010 at 06:08:55PM +0200, Wolfgang Draxinger wrote:
as you might know, Zapping the Xorg server by means of
CTRL+ALT+BACKSPACE has been first disabled by default, and later on
the xorg.conf option went away, too.
It is still possible to
setxkbmap -option
29 matches
Mail list logo
