Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: mdk@mdk.am (Michael Dominic K.)
Subject: [sup-talk] Backspace key?
Date: Thu, 14 Feb 2008 00:08:57 +0100	[thread overview]
Message-ID: <67ed228e0802131508y19d94e55h2ba3b41bd748e758@mail.gmail.com> (raw)
In-Reply-To: <1202804371-sup-2434@clarabella.clarabella>

On Feb 12, 2008 9:25 AM, Giorgio Lando <patroclo7 at gmail.com> wrote:
> Excerpts from Michael Dominic K.'s message of Tue Feb 12 00:57:37 +0100 2008:
> > I'm having one trivial problem though -- my backspace key doesn't work
> > in all entry fields (del works). It's been a while since I fixed
> > del/backspace issues in linux... any help/hints/config switch?
>
> I do not use the gnome-terminal, but in my case the working string for
> backspace in sup is ^h, while my terminals (all rxvt derivatives) sent
> ^? by default. From the large literature about the topic, I think that
> other terminal settings could adjust the behaviour also with ^?, but
> setting ^h has no negative side effect for me. So look in the
> configuration of gnome-terminal for something like backspaceKey or
> string...

Thanks,

that worked for me (^h). Actually gnome terminal has a special
configuration in the "compatibility section" that allows you to choose
what is sent for backspace.

However, I belive this is a bit of a workaround. I haven't noticed
anything breaking with ^h except... sup-config. Where, again,
backspace doesn't work with ^h on.

-- 
Michael.


  reply	other threads:[~2008-02-13 23:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-11 23:57 Michael Dominic K.
2008-02-12  8:25 ` Giorgio Lando
2008-02-13 23:08   ` Michael Dominic K. [this message]
2008-02-12  9:48 ` Nicolas Pouillard
2008-02-16 13:21   ` William Morgan
2008-02-16 13:54     ` Nicolas Pouillard

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=67ed228e0802131508y19d94e55h2ba3b41bd748e758@mail.gmail.com \
    --to=mdk@mdk.am \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox