Hi,
Sorry my response took so long.
On 26 May, [EMAIL PROTECTED] wrote:
> 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
Hi,
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.
Inputrc and cshrc can be used to map the different possible
key-sequences, but I agree with you that this is not ve
On 20 May, [EMAIL PROTECTED] wrote:
>
> Which I suspect does the same, but more cleanly.
Indeed.
> Covered:
> : ! Fix Xaw (Athena widget set) programs to understand the delete key
> : *Text.translations: #override ~Shift ~Meta Delete:
> delete-next-character()
Excellent.
>> How do I fin
On 20 May, Luis Francisco Gonzalez wrote:
> I have now added the bindings for other keys to tcsh and will upload them with
> the next release. I am reluctant to add two mappings for home and end, one
> for xterm and another for rxvt. Isn't it possible to change the mapping for
> rxvt the way it wa
Hi,
On 20 May, Luis Francisco Gonzalez wrote:
> It does need the bidnkey but it is now included in the systemwide
> file.
This is good news.
> The same goes for Xresources.
Exactly what is included in Xresources?
To get things clear, I think the following is needed in Xresources:
*VT100.Trans
Hi,
I don't think there is policy on other keys than backspace and delete.
However, this is enough policy to keep us busy for the time being;-)
The keyboard policy is stated in
http://www.debian.org/doc/debian-policy/ch3.html#s3.8
The important part is the part where it is stated
Hi,
As I hate writing monologues (especially dramatic ones), I really hope
to get some response this time. I know everybody is very busy, and this
problem is a difficult one, I am just looking for some help and support
on this issue. While I am sure you all know a lot more about Debian
developme
On 7 May, Philip Hands wrote:
> That's not quite right, [<---] will be generating ASCII BS, which we take to
> mean emacs help, and perhaps (in bash for example) delete-left.
>
> [Delete] will be generating ASCII DEL which will do delete-left, so they
> don't
> get to do delete-under-cursor, a
Hi guys,
While the proposed set of solutions generally works fine (letting xterm
use DEL and \e[3~, and leaving BS for apps), the telnet problem (remote
machines are likely to have kbs=^H, kdch1=\177 terminfo entries) is a
serious one. The expect script works fine locally, and could maybe be
made
9 matches
Mail list logo
