From: Stefan Monnier <monnier@iro.umontreal.ca>
To: dickey@his.com
Cc: gnu.emacs.bug@googlegroups.com, Sven Joachim <svenjoac@gmx.de>,
13471@debbugs.gnu.org
Subject: bug#13471: 24.3.50; S-up does not work in xterm: <select> is undefined
Date: Thu, 17 Jan 2013 12:37:19 -0500 [thread overview]
Message-ID: <jwvlibrbtn2.fsf-monnier+bug#13471@gnu.org> (raw)
In-Reply-To: <b5ec319a-c4b9-45b6-b9da-209b5e9e4137@googlegroups.com> (dickey@his.com's message of "Thu, 17 Jan 2013 01:33:45 -0800 (PST)")
Hi Thomas,
I'm not familiar enough to follow your argument and/or suggestion and
I'm especially unable to relate your email's body with its subject.
Could you try to help me understand?
Stefan
>>>>> "dickey" == dickey <dickey@his.com> writes:
> On Thursday, January 17, 2013 3:53:15 AM UTC-5, Sven Joachim wrote:
>> --8<---------------cut here---------------start------------->8---
>> === modified file 'src/term.c'
>> --- src/term.c 2013-01-11 02:40:58 +0000
>> +++ src/term.c 2013-01-17 08:49:20 +0000
>> @@ -1415,7 +1415,6 @@ term_get_fkeys_1 (void)
>> CONDITIONAL_REASSIGN ("F1", "k<", "f11");
>> CONDITIONAL_REASSIGN ("F2", "k>", "f12");
>> CONDITIONAL_REASSIGN ("%1", "kq", "help");
>> - CONDITIONAL_REASSIGN ("*6", "kU", "select");
>>
>> #undef CONDITIONAL_REASSIGN
>>
>> }
> A follow message says that there is a comment
> /* IBM has their own non-standard dialect of terminfo.
> If the standard name isn't found, try the IBM name. */
> which is interesting: the code fragment is dealing with termcap
> names (the first parameter is conventional termcap names, the
> second is not). It is not dealing with terminfo (there is a
> difference...). AIX has been terminfo-only for a long time
> (I don't have access to a machine old enough to provide an
> example of termcap in use - that would have to be from the
> early 1990s.
> I would suggest researching the history of this fragment,
> and probably discarding the entire chunk as obsolete,
> e.g., if it referred to AIX 3 or 4.
next prev parent reply other threads:[~2013-01-17 17:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.17669.1358412868.855.bug-gnu-emacs@gnu.org>
2013-01-17 9:33 ` bug#13471: 24.3.50; S-up does not work in xterm: <select> is undefined dickey
2013-01-17 9:55 ` Andreas Schwab
2013-01-17 10:06 ` Thomas Dickey
2013-01-17 10:22 ` Thomas Dickey
2013-01-17 10:28 ` Andreas Schwab
2013-01-17 10:38 ` Thomas Dickey
2013-01-17 10:49 ` Andreas Schwab
2013-01-17 10:53 ` Thomas Dickey
2013-01-17 11:11 ` Andreas Schwab
2013-01-17 11:00 ` Andreas Schwab
2013-01-17 11:45 ` Thomas Dickey
2013-01-17 17:37 ` Stefan Monnier [this message]
2013-01-18 0:02 ` Thomas Dickey
2013-01-18 14:12 ` Andreas Schwab
[not found] ` <mailman.17815.1358518404.855.bug-gnu-emacs@gnu.org>
2013-01-18 23:30 ` dickey
2013-01-19 10:29 ` Juri Linkov
2013-01-19 14:20 ` Stefan Monnier
2013-01-19 19:19 ` Thomas Dickey
2013-12-11 0:32 ` Juri Linkov
2013-01-17 8:53 Sven Joachim
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='jwvlibrbtn2.fsf-monnier+bug#13471@gnu.org' \
--to=monnier@iro.umontreal.ca \
--cc=13471@debbugs.gnu.org \
--cc=dickey@his.com \
--cc=gnu.emacs.bug@googlegroups.com \
--cc=svenjoac@gmx.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.