jhunt@omews3.intel.com (Jim Hunt) (06/08/90)
I am running X11R4 on a Sun 386i under SunOS 4.0.2. Since installing X11, I have noticed that the amount of time that a key needs to be depressed before it starts autorepeating is significantly less than it was under X10. The result is I tend to get a lot of unintentional double characters when I type. I know I can disable autorepeat entirely, but being able to adjust the autorepeat delay, either from a user settable parameter or via a compile time option would be much preferable. Does anyone know how this could be done? Reply via e-mail preferred, our news connection is quite flakey at the moment. Thanks, +---------------------------------------------+-------------------------------+ |____________________ __ | Jim Hunt | |\______NCC_1701_____|) .____.--"--"---._____ | Intel Corporation, JF1-58 | | \\ -----._________.----/ | 5200 NE Elam Young Pkwy | | /========\\=====/ / "--" | Hillsboro, OR 97124 | | \==\_____________|-( | (503) 696-4781 | | | jhunt@mipon3.intel.com | +---------------------------------------------+-------------------------------+
ekberg@ti-csl.csc.ti.COM (06/11/90)
> I know I can disable autorepeat entirely, but being able to adjust the > autorepeat delay, either from a user settable parameter or via a compile > time option would be much preferable. Does anyone know how this could be > done? Since you are using a Sun server, look at the man page for Xsun and you will see the -ar1 and -ar2 switches. You can't control the auto-repeat stuff from xset because there is no way to do that via the X protocol. -- tom (aisle C-4Q), ekberg@csc.ti.com
mike@BACH.CS.BYU.EDU (Mike Burbidge) (06/11/90)
I think this is a bug that I reported in X11R2 but evidently wasn't fixed. Mike Burbidge mike@bach.cs.byu.edu
casey@gauss.llnl.gov (Casey Leedom) (06/14/90)
| > I know I can disable autorepeat entirely, but being able to adjust the | > autorepeat delay, either from a user settable parameter or via a compile | > time option would be much preferable. Does anyone know how this could be | > done? | | Since you are using a Sun server, look at the man page for Xsun and you will | see the -ar1 and -ar2 switches. You can't control the auto-repeat stuff from | xset because there is no way to do that via the X protocol. I sure wish the X Consortium would come up with a standard way for xset to change non-standard server parameters. Someone once asked for the ability to change the Sun autorepeat rate via xset and the reply that came down the line was that there wasn't any way to do that with the standard X11 protocol. Some asked for an autorepeat xset extension after that, but I think it would be nicer to be able to extend the protocol in a more general way so that any non-standard server parameter could be modified without having to modify the protocol every time someone comes up with a new server parameter that people would like to change via xset. Maybe something like ``xset sm <ServerMessage>'' where <ServerMessage> is a string which is to be sent to the server to be interpreted by it. With such an extention it would be trivial to tell the Sun server you wanted it to start autorepeating after 300 miliseconds and to autorepeat every 20 miliseconds via ``xset sm autorepeat=300/20'' or something similar. Casey
guy@auspex.auspex.com (Guy Harris) (06/15/90)
> Maybe something like ``xset sm <ServerMessage>'' where <ServerMessage> >is a string which is to be sent to the server to be interpreted by it. >With such an extention it would be trivial to tell the Sun server you >wanted it to start autorepeating after 300 miliseconds and to autorepeat >every 20 miliseconds via ``xset sm autorepeat=300/20'' or something >similar. Good idea, perhaps, but autorepeat is sort of generic, so I'd want *all* servers that let you set it at all to use the same extension....
janssen@parc.xerox.com (Bill Janssen) (06/15/90)
> Maybe something like ``xset sm <ServerMessage>'' where <ServerMessage> > is a string which is to be sent to the server to be interpreted by it. > With such an extention it would be trivial to tell the Sun server you > wanted it to start autorepeating after 300 miliseconds and to autorepeat > every 20 miliseconds via ``xset sm autorepeat=300/20'' or something > similar. I think that what you wind up proposing is a general escape mechanism that allows server vendors to implement vendor-specific extension languages in the server, no two of which need be alike, which presents a read-eval interface via `xset sm'. This seems so dangerous to standardization, portability, etc., that I'd hate to see it. Bill -- Bill Janssen janssen.pa@xerox.com (415) 494-4763 Xerox Palo Alto Research Center 3333 Coyote Hill Road, Palo Alto, California 94304
casey@gauss.llnl.gov (Casey Leedom) (06/15/90)
| From: janssen@parc.xerox.com (Bill Janssen) | | I think that what you wind up proposing is a general escape mechanism | that allows server vendors to implement vendor-specific extension languages | in the server, no two of which need be alike, which presents a read-eval | interface via `xset sm'. | | This seems so dangerous to standardization, portability, etc., that | I'd hate to see it. I don't think that it's as dangerous as you think it is. I think that the desire to remain within standards would be too strong (DEC aside.) I doubt very much that you'd see this becoming a major part of any server. The goal is simply to provide a way to set server parameters and options at run time instead of only at start up. The desire to set the keyboard autorepeat rate is one example. Another might be switching back and forth between mono and color modes. On the other hand, if someone were to implement a full Display PostScript extension to the X server which allowed the setting of server parameters as a side benefit I wouldn't complain at all, so my opinions should be suspect when it comes to demagogue about embedded interpreters not being dangerous. Casey
guy@auspex.auspex.com (Guy Harris) (06/17/90)
>The goal is simply to provide a way to set server parameters and >options at run time instead of only at start up. The desire to set >the keyboard autorepeat rate is one example. Unless there are keyboards that do auto-repeat in a fashion sufficiently different from the fashion with which I'm familiar (i.e., with a parameter that specifies the "autorepeate delay" and another that specifies the "autorepeat rate"), the request to set this should *not* be left up to vendors to customize, so that I could run the same parameter-setting program against several severs. > On the other hand, if someone were to implement a full Display PostScript >extension to the X server which allowed the setting of server parameters as >a side benefit I wouldn't complain at all, ("followups redirected to 'comp.protocols.news'"?)