Re: alt->meta->esc status quo
Tor Slettnes wrote: > Charl> Dear Debian-Xers, At the moment, I need to set the X > Charl> resource xterm*metaSendsEscape to true and to do xmodmap -e > Charl> "keysym Alt_L = Meta_L Alt_L" to get Alt+key combinations > Charl> to work in an xterm, e.g. on the command-line (e.g. alt-f > Charl> and alt-b for skipping words forwards and backwards) or in > Charl> programs like JED. > > Charl> Am I doing something wrong, or is this how it's supposed to > Charl> be? I've checked the xterm FAQ as well as the > Charl> xserver-common FAQ and some of the old BTS reports, but > Charl> couldn't find closure on this matter. Any clarification > Charl> would be most welcome, as this matter comes up every so > Charl> often. > > > Use the resources 'XTerm*modifier: meta', or 'XTerm*modifier: alt', as > you see fit. That does not work for me (using woody and X 4.1.0-9). This resource doesn't seem to exist either (or am I blind ?). regards, Stefan -- http://www.shockfrosted.org
Re: alt->meta->esc status quo
Do you mean the first or the second solution? I can only speak for the first, which works perfectly here and which is _a_ solution according to Thomas Dickey. On Wed, Dec 26, 2001 at 09:17:43PM +0100, Stefan Schwandter wrote: > Tor Slettnes wrote: > > Charl> Dear Debian-Xers, At the moment, I need to set the X > > Charl> resource xterm*metaSendsEscape to true and to do xmodmap -e > > Charl> "keysym Alt_L = Meta_L Alt_L" to get Alt+key combinations > > Charl> to work in an xterm, e.g. on the command-line (e.g. alt-f > > Charl> and alt-b for skipping words forwards and backwards) or in > > Charl> programs like JED. > > Use the resources 'XTerm*modifier: meta', or 'XTerm*modifier: alt', as > > you see fit. > > That does not work for me (using woody and X 4.1.0-9). This resource > doesn't seem to exist either (or am I blind ?). -- charl p. botha | computer graphics and cad/cam http://cpbotha.net/ | http://www.cg.its.tudelft.nl/
Re: alt->meta->esc status quo
Charl P. Botha wrote: > Do you mean the first or the second solution? I can only speak for the > first, which works perfectly here and which is _a_ solution according to > Thomas Dickey. I meant the second one. If the first one is a working solution, can't it (or anonther solution) be integrated in the package? Another long lasting problem: home and end keys don't work in xterm for bash and zsh for example (all readline-using applications?). It works with mutt, slrn, ... , however. Although I know the question has been asked several times, and the answer has probably already been given, I couldn't find it... What's the "right" way to deal with that? regards, Stefan -- http://www.shockfrosted.org
Re: alt->meta->esc status quo
On Wed, Dec 26, 2001 at 09:41:25PM +0100, Stefan Schwandter wrote: > Charl P. Botha wrote: > > Do you mean the first or the second solution? I can only speak for the > > first, which works perfectly here and which is _a_ solution according to > > Thomas Dickey. > > I meant the second one. If the first one is a working solution, can't > it (or anonther solution) be integrated in the package? It's not always the desired solution. Some keyboards _do_ have separate META keys and always binding meta to alt would be very rude. The same goes for binding escape to meta. > works with mutt, slrn, ... , however. Although I know the question has > been asked several times, and the answer has probably already been > given, I couldn't find it... What's the "right" way to deal with that? I have no idea. I'm a ctrl-a ctrl-e kind of guy. :) -- charl p. botha | computer graphics and cad/cam http://cpbotha.net/ | http://www.cg.its.tudelft.nl/
FAQ: How do I add custom sections to a dexconf-generated XF86Config or XF86Config-4 file?
I just wrote this for addition to the Debian X FAQ, and thought I would post it here since I've been getting asked about this lately. Also, it's a bit of signal to counter the noise I generated yesterday under provocation from Jack Howarth. :) Needless to say, XF86Config(7), XF86Config-v3(5), and XF86Config-4(5) are required reading for people who want to customize their XFree86 server configuration. *) How do I add custom sections to a dexconf-generated XF86Config or XF86Config-4 file? As of xfree86v3 3.3.6-42 and xfree86 4.1.0-10, the dexconf utility only writes to part of the X server configuration file, instead of claiming the entire file for itself. For XFree86 3.x servers, this is mostly useful for adding XInput and ServerFlags sections, and for replacing the Files and Modules sections with something more to the user's liking. For XFree86 4.x, this enables the replacement of the Files and Modules sections, and the addition of an arbitrary number of supplementary Device, InputDevice, Monitor, Screen, and ServerLayout sections. Sections that are never written by dexconf (ServerFlags, VideoAdaptor, Modes, and Vendor) can also be added, of course. The most obvious application of this functionality is to support additional input devices and multi-headed configurations, but another is the replacement of, for instance, the Device section with something more customized. For instance, the driver for your video card may be buggy and you may wish to add the 'Option "NoAccel"' flag to the Device section for your video card. Dexconf and the debconf questions associated with it do not support the plethora of possible options (many of them driver-specific), because it is not a very ambitious tool. The number one fact to remember about the XFree86 4.x server is that the first ServerLayout section encountered in the XF86Config-4 file is the one that is used by default. It is of course possible to add the "-layout" option to server invocations, either manually or by configuring xdm or xinit to do so by default (e.g., by editing /etc/X11/xinit/xserverrc and/or /etc/X11/xdm/Xservers). To implement the above example, then, I would add three sections to the configuration file generated by debconf: a Device section with 'Option "NoAccel", a Screen section to use that Device in conjunction with a monitor, and a ServerLayout section to bind the Screen to input devices. If I want my new ServerLayout to be the default, I'll put it at the top of the XF86Config-4 file, before the debconf area. The Device and Screen sections can go either before or after the debconf area, but I'll put them before just to keep my customizations together. Also, I'll remember to give my new sections unique identifiers so that they don't collide with the identifiers used by debconf. Example: Section "Device" Identifier"Custom Device" Driver"ati" Option"NoAccel" EndSection Section "Screen" Identifier "Custom Screen" Device "Custom Device" Monitor "Generic Monitor" DefaultDepth 24 Subsection "Display" Depth 8 Modes "[EMAIL PROTECTED]" "[EMAIL PROTECTED]" "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 16 Modes "[EMAIL PROTECTED]" "[EMAIL PROTECTED]" "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 24 Modes "[EMAIL PROTECTED]" "[EMAIL PROTECTED]" "1024x768" "800x600" "640x480" EndSubsection EndSection Section "ServerLayout" Identifier"Custom" Screen"Custom Screen" InputDevice "Generic Keyboard" "CoreKeyboard" InputDevice "Configured Mouse" "CorePointer" EndSection ### BEGIN DEBCONF SECTION [snip] ### END DEBCONF SECTION Of course, my "Generic Monitor", "Generic Keyboard", and "Configured Mouse" should be defined in the debconf section of the file, but the identifier in the monitor section may be different, depending on what dexconf wrote to the file. -- G. Branden Robinson| The key to being a Southern Debian GNU/Linux | Baptist: It ain't a sin if you [EMAIL PROTECTED] | don't get caught. http://people.debian.org/~branden/ | -- Anthony Davidson pgpqfrDPXazOG.pgp Description: PGP signature
Re: alt->meta->esc status quo
Charl P. Botha wrote: > It's not always the desired solution. Some keyboards _do_ have separate > META keys and always binding meta to alt would be very rude. The same goes > for binding escape to meta. Ok. But rxvt or gnome-terminal for example work out-of-the-box. I'll try to find out what they do differently... > > > works with mutt, slrn, ... , however. Although I know the question has > > been asked several times, and the answer has probably already been > > given, I couldn't find it... What's the "right" way to deal with that? > > I have no idea. I'm a ctrl-a ctrl-e kind of guy. :) I becoming one, too :-) In spite of that, it disturbs me. And like above, rxvt et al. don't have the problem. regards, Stefan -- http://www.shockfrosted.org
Re: alt->meta->esc status quo
Tor Slettnes wrote: > Charl> Dear Debian-Xers, At the moment, I need to set the X > Charl> resource xterm*metaSendsEscape to true and to do xmodmap -e > Charl> "keysym Alt_L = Meta_L Alt_L" to get Alt+key combinations > Charl> to work in an xterm, e.g. on the command-line (e.g. alt-f > Charl> and alt-b for skipping words forwards and backwards) or in > Charl> programs like JED. > > Charl> Am I doing something wrong, or is this how it's supposed to > Charl> be? I've checked the xterm FAQ as well as the > Charl> xserver-common FAQ and some of the old BTS reports, but > Charl> couldn't find closure on this matter. Any clarification > Charl> would be most welcome, as this matter comes up every so > Charl> often. > > > Use the resources 'XTerm*modifier: meta', or 'XTerm*modifier: alt', as > you see fit. That does not work for me (using woody and X 4.1.0-9). This resource doesn't seem to exist either (or am I blind ?). regards, Stefan -- http://www.shockfrosted.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alt->meta->esc status quo
Do you mean the first or the second solution? I can only speak for the first, which works perfectly here and which is _a_ solution according to Thomas Dickey. On Wed, Dec 26, 2001 at 09:17:43PM +0100, Stefan Schwandter wrote: > Tor Slettnes wrote: > > Charl> Dear Debian-Xers, At the moment, I need to set the X > > Charl> resource xterm*metaSendsEscape to true and to do xmodmap -e > > Charl> "keysym Alt_L = Meta_L Alt_L" to get Alt+key combinations > > Charl> to work in an xterm, e.g. on the command-line (e.g. alt-f > > Charl> and alt-b for skipping words forwards and backwards) or in > > Charl> programs like JED. > > Use the resources 'XTerm*modifier: meta', or 'XTerm*modifier: alt', as > > you see fit. > > That does not work for me (using woody and X 4.1.0-9). This resource > doesn't seem to exist either (or am I blind ?). -- charl p. botha | computer graphics and cad/cam http://cpbotha.net/ | http://www.cg.its.tudelft.nl/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alt->meta->esc status quo
Charl P. Botha wrote: > Do you mean the first or the second solution? I can only speak for the > first, which works perfectly here and which is _a_ solution according to > Thomas Dickey. I meant the second one. If the first one is a working solution, can't it (or anonther solution) be integrated in the package? Another long lasting problem: home and end keys don't work in xterm for bash and zsh for example (all readline-using applications?). It works with mutt, slrn, ... , however. Although I know the question has been asked several times, and the answer has probably already been given, I couldn't find it... What's the "right" way to deal with that? regards, Stefan -- http://www.shockfrosted.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: alt->meta->esc status quo
On Wed, Dec 26, 2001 at 09:41:25PM +0100, Stefan Schwandter wrote: > Charl P. Botha wrote: > > Do you mean the first or the second solution? I can only speak for the > > first, which works perfectly here and which is _a_ solution according to > > Thomas Dickey. > > I meant the second one. If the first one is a working solution, can't > it (or anonther solution) be integrated in the package? It's not always the desired solution. Some keyboards _do_ have separate META keys and always binding meta to alt would be very rude. The same goes for binding escape to meta. > works with mutt, slrn, ... , however. Although I know the question has > been asked several times, and the answer has probably already been > given, I couldn't find it... What's the "right" way to deal with that? I have no idea. I'm a ctrl-a ctrl-e kind of guy. :) -- charl p. botha | computer graphics and cad/cam http://cpbotha.net/ | http://www.cg.its.tudelft.nl/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
FAQ: How do I add custom sections to a dexconf-generated XF86Config or XF86Config-4 file?
I just wrote this for addition to the Debian X FAQ, and thought I would post it here since I've been getting asked about this lately. Also, it's a bit of signal to counter the noise I generated yesterday under provocation from Jack Howarth. :) Needless to say, XF86Config(7), XF86Config-v3(5), and XF86Config-4(5) are required reading for people who want to customize their XFree86 server configuration. *) How do I add custom sections to a dexconf-generated XF86Config or XF86Config-4 file? As of xfree86v3 3.3.6-42 and xfree86 4.1.0-10, the dexconf utility only writes to part of the X server configuration file, instead of claiming the entire file for itself. For XFree86 3.x servers, this is mostly useful for adding XInput and ServerFlags sections, and for replacing the Files and Modules sections with something more to the user's liking. For XFree86 4.x, this enables the replacement of the Files and Modules sections, and the addition of an arbitrary number of supplementary Device, InputDevice, Monitor, Screen, and ServerLayout sections. Sections that are never written by dexconf (ServerFlags, VideoAdaptor, Modes, and Vendor) can also be added, of course. The most obvious application of this functionality is to support additional input devices and multi-headed configurations, but another is the replacement of, for instance, the Device section with something more customized. For instance, the driver for your video card may be buggy and you may wish to add the 'Option "NoAccel"' flag to the Device section for your video card. Dexconf and the debconf questions associated with it do not support the plethora of possible options (many of them driver-specific), because it is not a very ambitious tool. The number one fact to remember about the XFree86 4.x server is that the first ServerLayout section encountered in the XF86Config-4 file is the one that is used by default. It is of course possible to add the "-layout" option to server invocations, either manually or by configuring xdm or xinit to do so by default (e.g., by editing /etc/X11/xinit/xserverrc and/or /etc/X11/xdm/Xservers). To implement the above example, then, I would add three sections to the configuration file generated by debconf: a Device section with 'Option "NoAccel", a Screen section to use that Device in conjunction with a monitor, and a ServerLayout section to bind the Screen to input devices. If I want my new ServerLayout to be the default, I'll put it at the top of the XF86Config-4 file, before the debconf area. The Device and Screen sections can go either before or after the debconf area, but I'll put them before just to keep my customizations together. Also, I'll remember to give my new sections unique identifiers so that they don't collide with the identifiers used by debconf. Example: Section "Device" Identifier"Custom Device" Driver"ati" Option"NoAccel" EndSection Section "Screen" Identifier "Custom Screen" Device "Custom Device" Monitor "Generic Monitor" DefaultDepth 24 Subsection "Display" Depth 8 Modes "1280x960@78" "1152x864@85" "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 16 Modes "1280x960@78" "1152x864@85" "1024x768" "800x600" "640x480" EndSubsection Subsection "Display" Depth 24 Modes "1280x960@78" "1152x864@85" "1024x768" "800x600" "640x480" EndSubsection EndSection Section "ServerLayout" Identifier"Custom" Screen"Custom Screen" InputDevice "Generic Keyboard" "CoreKeyboard" InputDevice "Configured Mouse" "CorePointer" EndSection ### BEGIN DEBCONF SECTION [snip] ### END DEBCONF SECTION Of course, my "Generic Monitor", "Generic Keyboard", and "Configured Mouse" should be defined in the debconf section of the file, but the identifier in the monitor section may be different, depending on what dexconf wrote to the file. -- G. Branden Robinson| The key to being a Southern Debian GNU/Linux | Baptist: It ain't a sin if you [EMAIL PROTECTED] | don't get caught. http://people.debian.org/~branden/ | -- Anthony Davidson msg03235/pgp0.pgp Description: PGP signature
Re: alt->meta->esc status quo
Charl P. Botha wrote: > It's not always the desired solution. Some keyboards _do_ have separate > META keys and always binding meta to alt would be very rude. The same goes > for binding escape to meta. Ok. But rxvt or gnome-terminal for example work out-of-the-box. I'll try to find out what they do differently... > > > works with mutt, slrn, ... , however. Although I know the question has > > been asked several times, and the answer has probably already been > > given, I couldn't find it... What's the "right" way to deal with that? > > I have no idea. I'm a ctrl-a ctrl-e kind of guy. :) I becoming one, too :-) In spite of that, it disturbs me. And like above, rxvt et al. don't have the problem. regards, Stefan -- http://www.shockfrosted.org -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
[no subject]
Title: NOVEMBER DECEMBER'S CLOSEOUT: JUDAICA ART - JUST IN TIME FOR THE HOLIDAYS For a Limited Time Only!!! David Yochanan - Colors David Yochanan - Micro Calligraphy "Beloved Jerusalem" (English and Hebrew Versions available) "Wailing Wall" Retail for $85 - Buy it Today for Only $19.99!! Limited Quantities!!! Click Here to Order!!! More pictures to choose from - Click Here!! CALL NOW!!! (877) 240-8501 (Toll Free In the US) Excellent Gifts for ANY Occasion!! CALL FOR WHOLESALE David Yochanan is an inspiring Jewish/Israeli artist from Tiberia, who captures Jewish art and mystic symbols in beautiful vivid colors and micro calligraphy. Pictures are individually signed, and are pre-matted, meaning they are ready for framing in 11X13 frame mouldings (available in most stores), or by custom framers (to fit in with your decour). We bring you huge discounts by buying out entire stocks of closeout and clearanced items. Items are in limited quantities, so ORDER TODAY! using our secure online shopping cart!!! CALL NOW!!! (877) 240-8501 (Toll Free In the US) To be removed from receiving further discount offers please respond to this email with REMOVE in the subject line, no message necessary. To subscribe to our mailing list please respond to this email with SUBSCRIBE in the subject line, no message necessary. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]