unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Brown <brown@google.com>
To: Dan Nicolaescu <dann@ics.uci.edu>
Cc: 2057@emacsbugs.donarmstrong.com
Subject: bug#2057: 23.0.60; delete key and deletechar
Date: Thu, 16 Apr 2009 13:54:28 -0400	[thread overview]
Message-ID: <18919.28884.261672.227349@paradicsom.nyc.corp.google.com> (raw)
In-Reply-To: <200904161619.n3GGJt3l014011@godzilla.ics.uci.edu>


Dan Nicolaescu writes:
 > Robert Brown <brown@google.com> writes:
 > 
 >   > I believe the following patch may be the right fix for bug 2057.  When
 >   > looking at the key sequences generated by function keys, Emacs should only
 >   > register those that generate two or more ASCII characters.
 >   > 
 >   > My termcap entry, xterm-color, contains "kD=\177", which means that the
 >   > delete *function* key generates code 177.
 > 
 > Interesting, it seems that you have a modified termcap database, the normal one
 > has kD=\E[3~ for xterm-color.

Yes, it's definitely a bug in the termcap entry.  Hitting the delete
function key generates \E[3~ for me.  I can fix the termcap.

 > Can you try setting TERM to xterm-256color and see if that the delete
 > key works better then?

Switching to a different termcap works well.

I still think it may incorrect for Emacs to map single character function
key sequences.  But perhaps these just never occur in practice.

bob






  reply	other threads:[~2009-04-16 17:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-16 15:10 bug#2057: 23.0.60; delete key and deletechar Robert Brown
2009-04-16 16:19 ` Dan Nicolaescu
2009-04-16 17:54   ` Robert Brown [this message]
2009-04-16 18:45 ` Stefan Monnier
2009-04-16 18:54   ` Robert Brown
  -- strict thread matches above, loose matches on Subject: below --
2009-04-16 15:33 Robert Brown
2009-01-25 23:01 Robert Brown

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=18919.28884.261672.227349@paradicsom.nyc.corp.google.com \
    --to=brown@google.com \
    --cc=2057@emacsbugs.donarmstrong.com \
    --cc=dann@ics.uci.edu \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).