Re: kbd config
On Sep 25, Guy Maor wrote > I've just uploaded readline 2.1-6 which will try /etc/inputrc if > ~/.inputrc does not exist. AFAIK it the usual behaviour for programs that have both global and per-user configuration files to first process the global one, and then the user one. So, would it be possible to try /etc/inputrc and then ~/.inputrc? Ray -- ART A friend of mine in Tulsa, Okla., when I was about eleven years old. I'd be interested to hear from him. There are so many pseudos around taking his name in vain. - The Hipcrime Vocab by Chad C. Mulligan -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: Upcoming Debian Releases
On Sep 8, Brian C. White wrote > The following message is a list of items to be completed for the upcoming > releases of Debian GNU/Linux. If something is missing, incorrect, or you want > to take responsibility for one or more items, please send email to: > Brian White <[EMAIL PROTECTED]> > - configuring so non-ASCII characters work (???) [9] s|???|debian-i18n@lists.debian.org| probably. > 9 - One of the things that most people outside the US and UK have to deal > with is configuring everything so that non-ASCII characters and other > locale specific stuff works right. For example, bash needs a ~/.inputrc > so that you write åäö on the command line, instead of getting > beeps. Emacs needs some other stuff. -- Lars Wirzenius <[EMAIL > PROTECTED]> Please add: | There is a mailing list for internationalization issues in Debian: | debian-i18n@lists.debian.org . This list is used e.g. for the Debian | Keyboard Configuration Project | (http://fatman.mathematik.tu-muenchen.de/~schwarz/debian-kbd/) which | amongst other things, deals with providing an easy way to input non-ASCII | characters. On Sep 25, Guy Maor wrote > I've just uploaded readline 2.1-6 which will try /etc/inputrc if > ~/.inputrc does not exist. Great. The downside is, it doesn't help in dealing with the problem Lars noted, as libreadline isn't 8-bit clean by default. Please provide a default /etc/inputrc that is 8-bit clean, as explained in the the ISO 8859-1 National Character Set FAQ (ftp://ftp.vlsivie.tuwien.ac.at/pub/8bit/FAQ-ISO-8859-1): |14.1 bash |You need version 1.13 or higher and set the locale correctly (see |section 3). Also, to configure the `readline' input function of bash |to handle 8 bit characters correctly, you have to set some environment |variables in the readline startup file .inputrc: |--- |set meta-flag On |set convert-meta Off |set output-meta On |--- | |Before bash version 1.13, bash used the eighth bit of characters to mark |whether or not they were quoted when performing word expansions. While |this was not a problem in a 7-bit US-ASCII environment, this was a major |restriction for users working in a non-English environment. | |These readline variables have the following meaning (and default |values): |meta-flag (Off) | If set to On, readline will enable eight-bit input (that is, | it will not strip the high bit from the characters it reads), | regardless of what the terminal claims it can support. | convert-meta (On) | If set to On, readline will convert characters with the eighth | bit set to an ASCII key sequence by stripping the eighth bit | and prepending an escape character (in effect, using escape as | the meta prefix). | output-meta (Off) | If set to On, readline will display characters with the eighth | bit set directly rather than as a meta-prefixed escape sequence. -- UNFAIR Term applied to advantages enjoyed by other people which we tried to cheat them out of and didn't manage. See also DISHONESTY, SNEAKY, UNDERHAND and JUST LUCKY I GUESS. - The Hipcrime Vocab by Chad C. Mulligan -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
Re: fixing backspace and delete
On Tue, Apr 21, 1998 at 08:38:14AM +, [EMAIL PROTECTED] wrote: > On 22 Apr, Petr Kolar wrote: > > Is not better to map keycode 14 to delete and keycode 111 to remove (and > > later to "\e[3~") and let Ctrl-H to be backspace? Does eg. 'info' work > > with your setting? > > In info both the backspace and delete key will erase to the left > (backspace). This breaks info's documented interface. In info's help file it says :Moving within a node: :- : SPC Scroll forward a page. : DEL Scroll backward a page. Not a very intuitive choice of key, I admit. But I don't think this should be broken. > Since the arrow keys do not seem to work in info Debian's version of info has been patched for the cursor keys to work since March 1997. Greetings, Ray -- Cyberspace, a final frontier. These are the voyages of my messages, on a lightspeed mission to explore strange new systems and to boldly go where no data has gone before. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: keyboard... a huge BUG
On Wed, May 20, 1998 at 02:34:00PM +, Anne Baretta wrote:
> Exactly what is included in Xresources?
>
> To get things clear, I think the following is needed in Xresources:
>
> *VT100.Translations: #override \
> Delete:string("\033[3~") \n\
> BackSpace: string(0x7F) \n\
> Home: string("\033[1~") \n\
> End: string("\033[4~")
>
> *ttyModes: erase ^?
The current Xresources (from xbase 3.3.2.1-1) has:
: ! Make the backspace key generate ^? instead of ^H, per Debian keyboard
: ! policy.
: *VT100*backarrowKey: false
:
: ! Make the delete key generate ^[[3~ instead of ^?, per Debian keyboard
: ! policy; this also makes the Home and End keys produce the same character
: ! sequences as they do in the virtual console.
: *VT100.Translations: #override Delete: string("\033[3~")\n\
:Home: string("\033[1~")\n\
:End: string("\033[4~")
Which I suspect does the same, but more cleanly.
> Ideally, I'd also like to see the following included to make [Delete]
> work in athena-based apps:
>
> *Text.translations:#override \
> ~Shift ~Meta Delete: delete-next-character()
Covered:
: ! Fix Xaw (Athena widget set) programs to understand the delete key
: *Text.translations: #override ~Shift ~Meta Delete:
delete-next-character()
> How do I find out what's being done about Xresources
Ask the xbase maintainer; I don't know if he's on this list, so I've added a
Cc: [EMAIL PROTECTED] to this.
> and terminfo? I think these are the most important at this point.
The maintainer of ncurses (and thus of our terminfo database) has recently
started a new job and is currently unavailable for Debian work. Thus, the
only changes are in non-maintainer uploads in response to release-critical
bugs (Severity: important or higher).
The only recent change to ncurses that affects Debian keyboard policy was in
the 1.9.9g-8.1 ncurses packages I made:
: * Added a new xterm terminfo entry: kbs changed from ^H to \177
:and kdch1 from \177 to \E[3~ (per policy) (addresses part of #21914).
Are there other terminfo issues I should be aware of? If so, please report
them as "Severity: important" bugs against ncurses3.4 .
Ray
--
LEADERSHIP A form of self-preservation exhibited by people with auto-
destructive imaginations in order to ensure that when it comes to the crunch
it'll be someone else's bones which go crack and not their own.
- The Hipcrime Vocab by Chad C. Mulligan
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: the home/end issue
On Tue, May 26, 1998 at 03:04:32PM +, Anne Baretta wrote: > I wonder whether it is feasible to consistently map home/end to \e[1~ and > \e[4~ in all applications? While I think this is policy-stuff, a > discussion here may be useful. Maybe I'm misunderstanding this, but IMO there's a big difference between the backspace issue (^? or ^H) and this one. A quick look in the terminfo database (http://www.earthspace.net/~esr/terminfo/) shows there are a very large number of different sequences associated with khome/kend (e.g., for khome: \E[H ^^ \E[1~ \Ehm \E[Y \377\240 \E[7~ etc.). The correct way to make applications behave consistently with home and end, IMHO, would be something like: Screen-oriented programs that have/support cursor movement, e.g. editors, should use ncurses or an equivalent to parse the terminfo entry for the current TERM setting, and use that to support the following key behaviour, if it makes sense: "home" (khome): Move the cursor to the start of the current line. "end" (kend): Move the cursor to the end of the current line. "page up" (knp): Move one page up. "page down" (kpp): Move one page down. > That's a good idea, however, what the maintainers should do about it > depends on whether it's desirable to make a policy of only using \e[1~ > and \e[4~ or not. I don't think it is, as there are _many_ different sequences associated with home and end keys for different terminal types. With the backspace/delete issue, a big part of the problem is that many programs tried to fix it in their own particular way; with this issue, I don't think many programs are hardwired to expect specific sequences for home/end, pgup/pgdn etc.; the few that are should be changed to honour the terminfo entry. Ray -- LEADERSHIP A form of self-preservation exhibited by people with auto- destructive imaginations in order to ensure that when it comes to the crunch it'll be someone else's bones which go crack and not their own. - The Hipcrime Vocab by Chad C. Mulligan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Fixkeys Mini Howto
I joust notice this on freshmeat: :Fixkeys is a mini howto http://electron.et.tudelft.nl/~jdegoede/fixkeys.txt :on howto get your keys to work once and for all :under linux.. This howto comes with a few example config files. And doesn't :only explain what you should change but also why. I've been using and :refining this setup for 2 years now and it works great. Please check it out :as I hope to get Red Hat, Debian and other distributions to include this to :really fix key problems out of the box. Also please contact me with any :suggestions. I suspect most, perhaps even all, the issues addressed in this howto were fixed in Debian 2.0 as a result of the Debian Keyboard Configuration Project (anyone have a working URL for it?). Can someone who has followed this more closely than I please confirm this? Greetings, Ray -- ART A friend of mine in Tulsa, Okla., when I was about eleven years old. I'd be interested to hear from him. There are so many pseudos around taking his name in vain. - The Hipcrime Vocab by Chad C. Mulligan
Re: Fixkeys Mini Howto
On Mon, Sep 14, 1998 at 12:36:56PM +0200, Hans wrote: > > I suspect most, perhaps even all, the issues addressed in this howto > > were fixed in Debian 2.0 as a result of the Debian Keyboard > > Configuration Project (anyone have a working URL for it?). Can someone > > who has followed this more closely than I please confirm this? > > > Okay, I myself am well aware of this project since I followed it with much > interest as I already said I've been busy here and then with this keybaord > stuff for two years. > > Here's the url: > > http://schwarz.developer.debian.org/kbd/index.html > > And here's whats on their page: > > The home page of the Debian Keyboard Configuration Project has been > removed from this server since the project was unmaintained for several > months. If you are intrested in taking over these pages, please drop me a > note. > > Christian Schwarz That's a result of Christian having left Debian. I'm not sure if there's an up to date page available. > This project not getting anywhere was one of the reasons for me to write > this little howto. It's just a start, and there are others like it. But > this howto tries to address the core of the problem. And I am activly > trying to get redhat to include these fixes and other distributions i hope > will follow, if debian is interested in my work please drop me a note. Debian has fixed at least the backspace/delete behaviour as of 2.0; I'm not sure about other issues. Ray -- PATRIOTISM A great British writer once said that if he had to choose between betraying his country and betraying a friend he hoped he would have the decency to betray his country. - The Hipcrime Vocab by Chad C. Mulligan
Re: Keyboard Policy
[Note: mailing list change] On Wed, Sep 23, 1998 at 01:02:18PM +0200, Rainer Dorsch wrote: > After upgrading from 1.3 to 2.0 my system decided to ignore <-- in an > xterm, netscape, but work on the console, emacs, etc. Do you have Xkb enabled? The implementation of the keyboard policy for X only works for Xkb. > `<--' generates KB_Backspace in X. > > `Delete' generates KB_Delete in X. > > KB_Backspace, what is this? An X keyboard event name (or something like it); check with "xev". > That is all for me. The policy is not understandable for non-experts While it would be nice if it were, this isn't exactly a requirement; it is meant for the developers who have to implement it. > and the system is not working as it should. This may be a result of not switching to updated configuration files as supplied by the maintainer; I'd look into xbase's configuration files, and in /etc/X11/XF86Config (which may have "XKbdDisable" in it). Ray -- Obsig: developing a new sig
