I can confirm that Karmic also affected.
t...@helios:~$ lsb_release -rd
Description:Ubuntu 9.10
Release:9.10
Hope this will help to solve this: http://www.midnight-
commander.org/ticket/386
** Bug watch added: www.midnight-commander.org/ #386
** Changed in: vte (Ubuntu)
Importance: Undecided = Low
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
** Changed in: gnome-terminal (Ubuntu)
Status: Confirmed = Triaged
** Changed in: gnome-terminal (Ubuntu)
Assignee: salwanet (fauzi-abdurrohim) = Ubuntu Desktop Bugs (desktop-bugs)
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You
** Changed in: gnome-terminal (Ubuntu)
Assignee: Ubuntu Desktop Bugs (desktop-bugs) = salwanet (fauzi-abdurrohim)
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Think this was missed, as per Micah's comment, Invalidating ncurses
package.
** Changed in: ncurses (Ubuntu)
Status: New = Invalid
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are a member of
Suggested fix: konsole. More options, and as a bonus all the friggin
keys work (at least the ones I use anyway). I feel stupid using kde apps
on a gnome desktop but even stoopider not being able to use all the keys
on the keyboard.
--
[feisty] function keys don't work in gnome-terminal
That's at best a workaround, not a fix.
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I can confirm this.
$ lsb_release -rd
Description:Ubuntu jaunty (development branch)
Release:9.04
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this
Wow, I totally don't remember why I assigned myself to this bug.
I don't know what change needs to be done to solve this, so unassigning myself
for now.
If anyone runs across a patch, idea for a fix, or whatever, feel free to
re-assign this bug to me and outline what needs to be done. Meanwhile
** Changed in: xterm (Ubuntu)
Assignee: Bryce Harrington (bryceharrington) = (unassigned)
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Ctrl-End also has a problem; it seems to produce exactly the same codes
as End using showkey -s
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Indeed; filed bug 342436 - showkey only seems to work as root, which
probably deserves another bug
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
David, that's really a separate issue and should get a separate report
(but I can confirm the same behavior on Intrepid, though showkey doesn't
work for me).
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because
Confirmed it's still an issue on Jaunty with xterm and gnome-terminal.
** Changed in: xterm (Ubuntu)
Status: Confirmed = Triaged
** Changed in: xterm (Ubuntu)
Assignee: (unassigned) = Bryce Harrington (bryceharrington)
--
[feisty] function keys don't work in gnome-terminal
I also see that the modifyFunctionKeys:2 section of xterm's terminfo
seems to be the default.
Looking at xterm's changelog, the default was changed to 2 in Patch #216 -
2006/8/3:
# change default resource modifyFunctionKeys to 2 to avoid sending SS3 with
parameters (report by Kalle Olavi
At some point gnome-terminal changed its strings for modified function-keys. I
documented those
in terminfo.src for ncurses 5.7 (they don't match xterm, of course).
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification
No, the bug is still present here (8.04). I.e. pressing F1, F2, F3 and
F4 with modifiers still doesn't work and generates the same sequence as
demonstrated in the description. Shift+Arrows work though.
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
I too still see this bug in 8.04.
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Ooops - confirmed: With modifiers it still doesn't work neither in xterm
nor in gnome-terminal. In konsole, however, everything is still fine...
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are a
Just wanted to report that the problem disappeared for me after a dist-
upgrade to Hardy (via Gutsy, of course). So maybe the bug is silently
solved?
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are a
On Fri, 25 Jul 2008, Izzy wrote:
Just wanted to report that the problem disappeared for me after a dist-
upgrade to Hardy (via Gutsy, of course). So maybe the bug is silently
solved?
No bug here - it's either a fix in gnome-terminal, or the application
using it, e.g., vim.
--
[feisty]
Must be a fix in some underlying libraries - for me it's not only solved
in gnome-terminal, but in xterm as well (I only tested with the Midnight
Commander). So if some more people can confirm it's gone, the maintainer
maybe can close the bug as solved.
--
[feisty] function keys don't work in
** Changed in: xterm (Ubuntu)
Importance: Undecided = Medium
Status: New = Confirmed
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
On Tue, 23 Oct 2007, Alexey Borzenkov wrote:
Thomas, I don't seem to understand you. I just grabbed and compiled
terminfo.src you gave and while it helped with xterm (except that it's
just like with my previous attempts, Shift+F2 starts a new file in mc
instead of Shift+F4) it didn't work in
I don't use mc, but have read that it stores key-definitions per $TERM
with its learn-keys feature. That may be what's confusing it.
God, you are right!! I was looking at config in my home directory and
was already going to say that it's not like that, when an idea striked
me that maybe there's
Can anyone please explain what exactly has to be done with termcap files
in order to actually use them? TD is unreasonably terse which makes it
very difficult to decipher the advice that he offers.
Please, most people have not had to deal with terminfo or tic before...
the last time I saw a bug
I'd like to second steviant's request. For a long time this bug forced
me to use konsole instead of gnome-terminal, just for ability to press
Shift+F4. Unfortunately with konsole Shift+Left/Shift+Right don't work
(which work under gnome-terminal), so editing text files is not of much
use. It's
Hmm... about xterm-xf86-v44 I apologize since now it is somehow working.
:-/ I wonder why it didn't work a couple of months ago when I first
tried that.
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are
Also I just found that xterm sends slightly different codes for
Shift+F1...F4, so this myxterm.ti is also for xterm:
xterm|X11 terminal emulator with correct kf-sequences,
kf13=\EO1;2P,
kf14=\EO1;2Q,
kf15=\EO1;2R,
kf16=\EO1;2S,
kf13=\E[1;2P,
On Tue, 23 Oct 2007, Alexey Borzenkov wrote:
Also I just found that xterm sends slightly different codes for
Shift+F1...F4, so this myxterm.ti is also for xterm:
xterm|X11 terminal emulator with correct kf-sequences,
This would be for xterm with modifyFunctionKeys:0
I made a list in xterm
On Tue, 23 Oct 2007, Alexey Borzenkov wrote:
I'd like to second steviant's request. For a long time this bug forced
me to use konsole instead of gnome-terminal, just for ability to press
Shift+F4. Unfortunately with konsole Shift+Left/Shift+Right don't work
(which work under gnome-terminal),
Thomas, I don't seem to understand you. I just grabbed and compiled
terminfo.src you gave and while it helped with xterm (except that it's
just like with my previous attempts, Shift+F2 starts a new file in mc
instead of Shift+F4) it didn't work in gnome-terminal (because of \E[
and \EO difference
arrow keys don't work in vi in an ssh session either
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
On Tue, 14 Aug 2007, Izzy wrote:
I just found out that the problem does *NOT* appear with konsole.
That's not unexpected, given the history of the feature.
I implemented the original flavor in (xterm of course)
Patch #94 - 1999/3/27 - XFree86 3.9Pf
and made the change which seems to be
I just found out that the problem does *NOT* appear with konsole.
Checking a bit deeper, it uses TERM=linux - setting TERM=xterm here
breaks a few things again. The other way round (setting TERM=linux in a
xterm session) is not helpful at all. Side-effect of TERM=linux is that
you lose mouse
Agree: gnome-terminal has never emulated all of xterm's control sequences, and
it is unlikely
that it ever will. That's why there is a separate terminfo entry gnome to
address its actual
behavior. Set $TERM to gnome and report discrepancies there.
For instance, the comment about gnome's bug
First it is very funny: Half a year just pointing at each other saying
There's the problem, not here!. :-(
@Thomas Dickey goes Second:
===[ cut here ]===
[EMAIL PROTECTED]:~$ echo $TERM
gnome
[EMAIL PROTECTED]:~$ mc
Unknown terminal: gnome
Check the TERM environment variable.
Also make
On Sun, Aug 05, 2007 at 08:58:45PM -, Izzy wrote:
First it is very funny: Half a year just pointing at each other saying
There's the problem, not here!. :-(
@Thomas Dickey goes Second:
===[ cut here ]===
[EMAIL PROTECTED]:~$ echo $TERM
gnome
[EMAIL PROTECTED]:~$ mc
Unknown
On Sun, Aug 05, 2007 at 08:58:45PM -, Izzy wrote:
gnome
[EMAIL PROTECTED]:~$ mc
Unknown terminal: gnome
Check the TERM environment variable.
Also make sure that the terminal is defined in the terminfo database.
Alternatively, set the TERMCAP environment variable to the desired
termcap
Instead of fighting for who's fault it is: Is it somehow likely that this will
be fixed in the near future? I guess the standard user is not interested in
the fact whether the bug is because of ncurses, xterm or whatever. To me it is
completely irrelevant whether xterm follows the rules
Wasn't fighting for whose fault it was; was fighting whether it was a
really bug, and whether infocmp's output really was meant to describe
modified function keys. Now that that's been established, I think the
change should be relatively straightforward; assuming xterm has changed
its behavior
OK - sounds like progress, we were just clearing up things and now the
*issue* is clear. Agree with you we need to check which package needs
the corrections: Whether xterm behaves correctly (and terminfo needs to
be fixed), or xterm is broken (which means xterm, gnome-terminal etc.
need to be
Micah, looking in further detail at xterm's terminfo file, I found some
interesting stuff.
Its terminfo file contains multiple definitions for kf25, under multiple term
types:
xterm+pcfn: kf25=\E[46~
xterm+pcfN: kf25=\E[46~
xterm+pcf0: kf25=\EO5P
xterm+pcf1: kf25=\E[5P
xterm+pcf2: kf25=\E[1;5P
Adding to ncurses since the terminfo xterm definition doesn't match what
xterm actually does.
** Also affects: ncurses (Ubuntu)
Importance: Undecided
Status: New
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug
Alex, Izzy, I'm not sure where you get the idea that xterm should
generate those sequences. infocmp gives \EO5P for function key 25, not
for control-function key 1. Infocmp does not and has never had a
mechanism for specifying modifiers to special keys. It looks to me that
MC is in the wrong.
Micah,
I'm afraid I must disappoint you. The entire problem started (for me)
with Feisty and only appears when working locally. When I log in via ssh
(i.e. not Ubuntu xterm, but e.g. RHEL4), everything works as expected:
Shift-F4 opens a new file to edit. If it was mc causing problems, I
would
Izzy, the second paragraph you wrote is rather uninformative. Many of
the characters being generated are being stripped out, using the method
you've described. Use cat instead.
Note that for many terminals, the sequences generated will depend
greatly upon whether the terminal is in keypad
Micah, since the purpose of terminfo is to recognize what xterm does, it
seems to me that suggesting that xterm should follow what terminfo says
it does is putting the cart before the horse. terminfo doesn't describe
what xterm should do, it (should) describe what xterm *does*.
Of course, it is
Also, comments on gnome's bug #337252 suggest that xterm's behaviour *did*
change [somewhat] recently:
http://bugzilla.gnome.org/show_bug.cgi?id=337252#c1
http://bugzilla.gnome.org/show_bug.cgi?id=337252#c4
http://bugzilla.gnome.org/show_bug.cgi?id=337252#c9
--
[feisty] function keys don't work
«Micah, since the purpose of terminfo is to recognize what xterm does,
it seems to me that suggesting that xterm should follow what terminfo
says it does is putting the cart before the horse. terminfo doesn't
describe what xterm should do, it (should) describe what xterm *does*.»
Xterm does, in
by my understanding, xterm is intended to produce F13-F24 for
Shift+F1-Shift+F12, F25-F36 for Ctrl+F1-Ctrl+F12, etc.
This is supported by
http://webcvs.freedesktop.org/xorg/xc/programs/xterm/terminfo?revision=1.5view=markup
as well as
Another file that supports my understanding: debian's (and therefore
presumably Ubuntu's) own xterm terminfo file from ncurses-base, includes
the comment:
# Function keys with modifiers (Sun/PC):
# -
# Shift-Fx - kf{12+x}
# Control-Fx
Okay, thanks Alex, that clarifies things quite a lot. I guess Xterm and
its sisters have repurposed the kfX strings. It might help for
terminfo(5) to clarify this situation (even though it really isn't
ncurses' responsibility to do so, since that's not the original meaning
of those names; still,
Ah, I see your point about the other special keys (cursor in particular)
there's cuu1, cuf1, cud1, and cub1...but shifted variants only for left
and right (kLFT and kRIT); and no control variants whatsoever. And this
all without getting into alt/meta/super variants... ;-)
Did any terminal ever
Did any terminal ever actually have 64 function keys, as the existence
of kf0-kf63 suggests?
I doubt it. And I had been wondering about that. :)
Seems to me, though, if terminfo has 'em in there _specifically_ for
usages like xterm's, they're without excuse for not saying something
about how
This also affects xterm - same behavior as described for gnome-terminal
** Also affects: xterm (Ubuntu)
Importance: Undecided
Status: Unconfirmed
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you
Is this definitely a problem with gnome-terminal, given that xterm also
generates these sequences?
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Alex, I've tried to downgrade gnome-terminal to 2.16.1-0ubuntu1 in
Feisty and nothing has changed. It means that the problem is indeed not
(entirely) in gnome-terminal itself but maybe somewhere else in GNOME --
the thing is that gnome-terminal is where it can be clearly observed.
Anyway, I still
This looks to be a problem with vte changing to match XTerm's behaviour,
and possibly XTerm not matching how terminfo thinks it behaves.
http://svn.gnome.org/viewcvs/vte/trunk/src/keymap.c?r1=1341r2=1391
shows the change.
It looks like the distinction is there to differentiate F13-F16 from
oh, and according to the comment on the change in question, it was done
to fix gnome bug #337252,
http://bugzilla.gnome.org/show_bug.cgi?id=337252
** Also affects: vte (Ubuntu)
Importance: Undecided
Status: Unconfirmed
** Changed in: vte (Ubuntu)
Status: Unconfirmed = Confirmed
Of course, since vte is an xterm emulator, that means that doing what
xterm does is 100% correct.
Thus the fault lies either with the terminfo database for claiming that
Shift-F1 is F13 is \EO2P or with MC for thinking that Shift-F1 is F13.
--
[feisty] function keys don't work in gnome-terminal
confirmed. Happened after upgrading to feisty.
--
[feisty] function keys don't work in gnome-terminal
https://bugs.launchpad.net/bugs/96676
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Thanks for your bug report. This bug has been reported to the developers
of the software. You can track it and make comments here:
http://bugzilla.gnome.org/show_bug.cgi?id=425462
** Changed in: gnome-terminal (Ubuntu)
Importance: Undecided = Low
Assignee: (unassigned) = Ubuntu Desktop
Sorry for the flood with spelling corrections, I should have guessed it
will e-mail every single one to subscribers :)
--
[feisty] function keys don't work in gnome-terminal
https://launchpad.net/bugs/96676
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
64 matches
Mail list logo
