Re: Some keys are not properly recognized in Konsole/xterm
On Thu, Feb 11, 2010 at 08:14:44PM -0500, Thomas Dickey wrote: > On Fri, 12 Feb 2010, Oswald Buddenhagen wrote: > >do in any graphical mail reader), i have to: > >1) find out that i can do that at all. the man page doesn't contain the > >term "URL" once. > >2) write a regexp matching urls > > See the bottom of the app-defaults file. > oh - great. so if i did my initial config now (and not 10 years ago) i'd even have a chance to be clued into the existence and setup of the feature. ;) > >3) have some process which leads from a selection to opening a browser. > >klipper to the rescue! yay! even more regexps! > > Most people would remember how to use the paste operation (ymmv) > you entirely missed the point. it's about reducing the number of manual actions required. you should read some basic literature on usability. > >right. that's why all graphical muas lack that feature ... ;) > > hmm - no "all". > all which have a noteworthy market share (guess why they do). > Perhaps "all" of the ones in front of you at the moment. > i'm not aware of any attempts to make mutt graphical. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Fri, 12 Feb 2010, Oswald Buddenhagen wrote: do in any graphical mail reader), i have to: 1) find out that i can do that at all. the man page doesn't contain the term "URL" once. 2) write a regexp matching urls See the bottom of the app-defaults file. 3) have some process which leads from a selection to opening a browser. klipper to the rescue! yay! even more regexps! Most people would remember how to use the paste operation (ymmv) right. that's why all graphical muas lack that feature ... ;) hmm - no "all". Perhaps "all" of the ones in front of you at the moment. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Thu, Feb 11, 2010 at 07:03:40PM -0500, Thomas Dickey wrote: > On Fri, 12 Feb 2010, Oswald Buddenhagen wrote: > >anyway, some useful features would be tabs, clickable urls and proper > > It's been configurable for "clickable urls", for highlighting for a few > years. > i suppose you mean the multi-click options. so let's see. to use it in a way even remotely resembling just clicking urls in emails (like it would do in any graphical mail reader), i have to: 1) find out that i can do that at all. the man page doesn't contain the term "URL" once. 2) write a regexp matching urls 3) have some process which leads from a selection to opening a browser. klipper to the rescue! yay! even more regexps! or maybe a global shortcut with khotkeys to pop up a new empty browser window i could paste the url into? i can't decide - both options are *so* appealing ... arguably, somewhere between 0) and 1), you lost that "user friendliness" idea frank was mentioning ... ;) > Spawning off a web-brower only seems like a good idea until you > see it in action. > right. that's why all graphical muas lack that feature ... ;) as far as i'm concerned, it would be sufficient if url hovering and clicking would work only when ctrl is held down. oh, wait - that already pops up a menu which does its best to induce rsi by requiring me to hold down the mouse button while i navigate it. next idea then ... > >config dialogs (imagine - most people don't like reading man pages). > > most of gnome's users are subliterate, agreed. > i'm sure that to switch gears in your car/bike you always lean down and operate them directly - after all, appropriate controls anywhere near the console are clearly meant for illiterates. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Thu, 11 Feb 2010, Thomas Dickey wrote: On Fri, 12 Feb 2010, Oswald Buddenhagen wrote: and maybe you find something inspiring in http://www.midnight-commander.org/ticket/24 ;) yes, I noticed some related reports in either Redhat or Gentoo, which add to my to-do list... -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Fri, 12 Feb 2010, Oswald Buddenhagen wrote: On Thu, Feb 11, 2010 at 06:16:00PM -0500, Thomas Dickey wrote: On Thu, 11 Feb 2010, frank wrote: Give xterm the friendliness users are longing for and all those imitations will just disappear. i bet a leg against that. :P hmm - transparent backgrounds for people who aren't typing or reading. with the advent of compositing window managers you don't need to make them transparent yourself any more. mwahahaha anyway, some useful features would be tabs, clickable urls and proper It's been configurable for "clickable urls", for highlighting for a few years. Spawning off a web-brower only seems like a good idea until you see it in action. config dialogs (imagine - most people don't like reading man pages). most of gnome's users are subliterate, agreed. and maybe you find something inspiring in http://www.midnight-commander.org/ticket/24 ;) ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Thu, Feb 11, 2010 at 06:16:00PM -0500, Thomas Dickey wrote: > On Thu, 11 Feb 2010, frank wrote: > >Give xterm the friendliness users are longing for and all those > >imitations will just disappear. > i bet a leg against that. :P > hmm - transparent backgrounds for people who aren't typing or reading. > with the advent of compositing window managers you don't need to make them transparent yourself any more. mwahahaha anyway, some useful features would be tabs, clickable urls and proper config dialogs (imagine - most people don't like reading man pages). and maybe you find something inspiring in http://www.midnight-commander.org/ticket/24 ;) ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Thu, 11 Feb 2010, frank wrote: The bug reports also demonstrate that they don't really understand the issue, and have made a few changes to make it more complicated. (I'm not expecting anything productive from upstream unless a new developer takes over ;-) Upstream of upstream something productive could come from the xterm maintainer. For instance, friendly features in xterm. If you have not asked yourself yet why Gnome Terminal and Konsole and others are around, this could be the right time. Give xterm the friendliness users are longing for and all those imitations will just disappear. hmm - transparent backgrounds for people who aren't typing or reading. etc. awai -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
The bug reports also demonstrate that they don't really understand the issue, and have made a few changes to make it more complicated. (I'm not expecting anything productive from upstream unless a new developer takes over ;-) Upstream of upstream something productive could come from the xterm maintainer. For instance, friendly features in xterm. If you have not asked yourself yet why Gnome Terminal and Konsole and others are around, this could be the right time. Give xterm the friendliness users are longing for and all those imitations will just disappear. Regards frank ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Tue, 2 Feb 2010, R. Steven Rainwater wrote: On Tue, 2010-02-02 at 20:08 +0100, Yury V. Zaytsev wrote: On Tue, 2010-02-02 at 10:56 -0600, R. Steven Rainwater wrote: and the GNOME terminal developers are saying they won't change the way the key bindings work because it would break lots of other stuff. Are they saying anything at all? The GNOME terminal developers have not responded to my emails about the bug report (yet) but some googling revealed the escape sequence problem came up before some years ago and they refused to change the behavior for the reason that a lot of other programs now depended on the current behavior. I don't have a reference handy though. The bug reports also demonstrate that they don't really understand the issue, and have made a few changes to make it more complicated. (I'm not expecting anything productive from upstream unless a new developer takes over ;-) -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Tue, 2010-02-02 at 21:15 +0100, Yury V. Zaytsev wrote: > Editor -> Options -> General > > [ ] Visible trailing spaces > [ ] Cursor beyond end of line Thanks! Also, "[ ] Visible tabs" turned off the distracting garbage characters appearing inline with my text. I definitely think all three of those should be off by default. But I'm glad to have found a way to turn them off anyhow. That makes the editor much, much more usable! Now if I could find a fix for the ctrl-pgup/ctrl-pgdn breakage, MC would be back to its perfect self again! :) -Steve ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Tue, 2010-02-02 at 14:10 -0600, R. Steven Rainwater wrote: > In mc-4.7.0.1-1.fc12, which is standard with Fedora 12, both those > "features" are on by default and I have not seen any obvious way of > turning them off. I highly approve any changes that would make such > unusual behaviors not the default. In the meantime, how could I turn off > those behaviors? Editor -> Options -> General [ ] Visible trailing spaces [ ] Cursor beyond end of line -- Sincerely yours, Yury V. Zaytsev ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Tue, 2010-02-02 at 20:08 +0100, Yury V. Zaytsev wrote: > On Tue, 2010-02-02 at 10:56 -0600, R. Steven Rainwater wrote: > > and the GNOME terminal developers are saying they won't change > > the way the key bindings work because it would break lots of > > other stuff. > > Are they saying anything at all? The GNOME terminal developers have not responded to my emails about the bug report (yet) but some googling revealed the escape sequence problem came up before some years ago and they refused to change the behavior for the reason that a lot of other programs now depended on the current behavior. I don't have a reference handy though. The RedHat bug ID tracking the MC ctrl-pgup/ctrl-pgdn problem is: https://bugzilla.redhat.com/show_bug.cgi?id=551062 The Redhat bug started as an MC bug and was then switched to a GNOME terminal bug since that's technically where the problem is (even though it was a change in MC which caused the loss of functionality) The MC bug (which has been closed as a "won't fix"): http://www.midnight-commander.org/ticket/1938 > Actually, I have just tried Ctrl+PgUp / Ctrl+PgDown (which you can free > from the settings dialog) and Ctrl+Home / Ctrl+End on 4.7.0.1 in Gnome > Terminal and neither of those takes me to the beginning / end of file. Yes, neither work for me on RedHat Fedora 12. Prior to this version, ctrl-pgdn took me to the bottom of the file and ctrl-pgup took me to the top of the file. That functionality worked on all previous versions of Fedora and on Fedora 12 when it was first released but broke with they updated to MC 4.7.0. > >(other nits that annoy me are the recent breakage of the cursor that > > makes it float out past the real end of line and not wrap correctly, > > and the earlier change that replaced white space with gibberish characters) > > Both of these are optional and should be off by default. If this is not > the case with the latest version, please submit a bug report. In mc-4.7.0.1-1.fc12, which is standard with Fedora 12, both those "features" are on by default and I have not seen any obvious way of turning them off. I highly approve any changes that would make such unusual behaviors not the default. In the meantime, how could I turn off those behaviors? -Steve ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Tue, 2010-02-02 at 10:56 -0600, R. Steven Rainwater wrote: > > To me, the bigger problem is not what keys are used but whether or or > not it works at all. And since the ctrl-home and ctrl-end key combos > don't work with MC in GNOME terminal, this change broke the > functionality. As best I can tell, the MC developers are blaming the > breakage on GNOME terminal and the GNOME terminal developers are saying > they won't change the way the key bindings work because it would break > lots of other stuff. Are they saying anything at all? Actually, I have just tried Ctrl+PgUp / Ctrl+PgDown (which you can free from the settings dialog) and Ctrl+Home / Ctrl+End on 4.7.0.1 in Gnome Terminal and neither of those takes me to the beginning / end of file. Ctrl+PgUp / Ctrl+PgDown take me to the beginning or the end of the buffer and Ctrl+Home / Ctrl+End behave identically to Home/End. ... > I've been an MC user for at least a decade but changes that have been > showing up in recent versions of the MC editor are making the program > more and more difficult to use productively. (other nits that annoy me > are the recent breakage of the cursor that makes it float out past the > real end of line and not wrap correctly, and the earlier change that > replaced white space with gibberish characters) Both of these are optional and should be off by default. If this is not the case with the latest version, please submit a bug report. -- Sincerely yours, Yury V. Zaytsev ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Tue, 2010-02-02 at 10:23 +, frank wrote: > > This does not really explain why the default key bindings were switched > > from Ctrl+PgUp and Ctrl+PgDown that I've been using unconsciously for > > quite a long time at all. > > Quite correct and quite oblivious of reality. > > It must be at least 10 years that editors have standardised on > Ctrl-Home and Ctrl-End to move to begin resp. end of buffer. To me, the bigger problem is not what keys are used but whether or or not it works at all. And since the ctrl-home and ctrl-end key combos don't work with MC in GNOME terminal, this change broke the functionality. As best I can tell, the MC developers are blaming the breakage on GNOME terminal and the GNOME terminal developers are saying they won't change the way the key bindings work because it would break lots of other stuff. Is there perhaps some way that these other editors you're mentioning detect Konsole or GNOME terminal and adapt to their slightly out of whack xterm escape sequences? Perhaps MC could be adapted to work correctly with them too. I've been an MC user for at least a decade but changes that have been showing up in recent versions of the MC editor are making the program more and more difficult to use productively. (other nits that annoy me are the recent breakage of the cursor that makes it float out past the real end of line and not wrap correctly, and the earlier change that replaced white space with gibberish characters) And, sorry, I don't really mean to give the idea I don't like MC, because up until recently I've always been a huge proponent of MC and installed it on every GNU/Linux system I've used as well as using it on HPUX, AIX, Solaris, and other systems. It really is a great program and I appreciate all the hard work that's gone into it. :) -Steve ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Tue, 02 Feb 2010 10:25:46 +0100 "Yury V. Zaytsev" wrote: > This does not really explain why the default key bindings were switched > from Ctrl+PgUp and Ctrl+PgDown that I've been using unconsciously for > quite a long time at all. Oh, sorry... I didn't quite understand that e-mail. The discussed change of keybindings was inpired by http://www.midnight-commander.org/ticket/1724#comment:4 and http://www.midnight-commander.org/ticket/1724#comment:22 -- Andrew ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
This does not really explain why the default key bindings were switched from Ctrl+PgUp and Ctrl+PgDown that I've been using unconsciously for quite a long time at all. Quite correct and quite oblivious of reality. It must be at least 10 years that editors have standardised on Ctrl-Home and Ctrl-End to move to begin resp. end of buffer. And please be sure you do not mention vim, emacs and the crowd from the Linux text console. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Tue, 2010-02-02 at 08:51 +0300, Andrew Borodin wrote: > On Mon, 01 Feb 2010 13:17:06 -0600 "R. Steven Rainwater" wrote: > > I've noticed similar problems with GNOME terminal in recent versions of > > MC included with Redhat Fedora. > > Look at http://www.midnight-commander.org/ticket/1938. > This does not really explain why the default key bindings were switched from Ctrl+PgUp and Ctrl+PgDown that I've been using unconsciously for quite a long time at all. -- Sincerely yours, Yury V. Zaytsev ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
Thanks for the tip. I installed the ncurses-term package and set TERM to konsole, but the effect is the same; mc will still not recognize the keys I mentioned in my first email. I tried various combinations of TERM and Konsole keyboards to no avail. 2010/2/1 Thomas Dickey > On Mon, 1 Feb 2010, Miguel Pérez wrote: > > Interesting, I'm using Konsole from KDE 3.5 (KDE 3.5.10, Qt 3.3.8b, >> Konsole >> 1.6.6) which doesn't have a "konsole" map nor my terminfo database (which >> came in the Ubuntu package ncurses-base 5.6+20071124-1ubuntu2) has an >> entry >> for konsole. >> > > In Debian, that (and gnome, etc), are in ncurses-term > > /usr/share/terminfo/k/konsole-vt100 > /usr/share/terminfo/k/konsole-16color > /usr/share/terminfo/k/konsole-linux > /usr/share/terminfo/k/konsole-256color > /usr/share/terminfo/k/konsole > /usr/share/terminfo/k/konsole-vt420pc > /usr/share/terminfo/k/konsole-xf4x > /usr/share/terminfo/k/konsole-base > /usr/share/terminfo/k/konsole-solaris > /usr/share/terminfo/k/konsole-xf3x > > The often-presented argument that installing ncurses-term involves a large > amount of diskspace loses effect when compared to a "minimal" install of KDE > or GNOME (several hundred megabytes). > > > >> 2010/2/1 Thomas Dickey >> >> On Mon, 1 Feb 2010, Thomas Dickey wrote: >>> >>> On Mon, 1 Feb 2010, Miguel Pérez wrote: >>> I love the ability to customize keybindings in 4.7. However, I've noticed > some keys cannot be bound because they aren't recognized properly by > Midnight Commander. When you hit an unrecognized sequence, mc will > simply > skip the escape sequence up to a point and print the rest of it. > > I'm using Konsole, set to the xterm (XFree 4.x.x) keyboard, and $TERM > is > xterm. These are the key combinations that produce escape sequences but > aren't recognized by mc. Everything else either works, or doesn't > produce > a > > konsole doesn't send escape sequences that match xterm. Use "infocmp konsole xterm" to see this. >>> ...of course that's assuming that mc relies on the terminal description >>> (I seem to recall some discussion where it's using separate configuration >>> information). >>> >>> Assuming that it's actually using the terminal description, e.g., from >>> ncurses, then mismatches would be due to (a) not using TERM=konsole, and >>> (b) >>> futher mismatches might be due to differences between the current konsole >>> application and the ncurses description. >>> >>> A quick check (using tack and TERM=konsole for konsole 2.3.2) shows no >>> issues. >>> >>> -- >>> Thomas E. Dickey >>> http://invisible-island.net >>> ftp://invisible-island.net >>> >>> >> >> >> -- >> Antes de imprimir este correo electrónico, considera tu responsabilidad >> medioambiental. >> >> Please consider your environmental responsibility before printing this >> email. >> >> > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net > -- Antes de imprimir este correo electrónico, considera tu responsabilidad medioambiental. Please consider your environmental responsibility before printing this email. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Mon, 01 Feb 2010 13:17:06 -0600 "R. Steven Rainwater" wrote: > I've noticed similar problems with GNOME terminal in recent versions of > MC included with Redhat Fedora. Look at http://www.midnight-commander.org/ticket/1938. -- Andrew ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Mon, 1 Feb 2010, Miguel P??rez wrote: Interesting, I'm using Konsole from KDE 3.5 (KDE 3.5.10, Qt 3.3.8b, Konsole 1.6.6) which doesn't have a "konsole" map nor my terminfo database (which came in the Ubuntu package ncurses-base 5.6+20071124-1ubuntu2) has an entry for konsole. In Debian, that (and gnome, etc), are in ncurses-term /usr/share/terminfo/k/konsole-vt100 /usr/share/terminfo/k/konsole-16color /usr/share/terminfo/k/konsole-linux /usr/share/terminfo/k/konsole-256color /usr/share/terminfo/k/konsole /usr/share/terminfo/k/konsole-vt420pc /usr/share/terminfo/k/konsole-xf4x /usr/share/terminfo/k/konsole-base /usr/share/terminfo/k/konsole-solaris /usr/share/terminfo/k/konsole-xf3x The often-presented argument that installing ncurses-term involves a large amount of diskspace loses effect when compared to a "minimal" install of KDE or GNOME (several hundred megabytes). 2010/2/1 Thomas Dickey On Mon, 1 Feb 2010, Thomas Dickey wrote: On Mon, 1 Feb 2010, Miguel P??rez wrote: I love the ability to customize keybindings in 4.7. However, I've noticed some keys cannot be bound because they aren't recognized properly by Midnight Commander. When you hit an unrecognized sequence, mc will simply skip the escape sequence up to a point and print the rest of it. I'm using Konsole, set to the xterm (XFree 4.x.x) keyboard, and $TERM is xterm. These are the key combinations that produce escape sequences but aren't recognized by mc. Everything else either works, or doesn't produce a konsole doesn't send escape sequences that match xterm. Use "infocmp konsole xterm" to see this. ...of course that's assuming that mc relies on the terminal description (I seem to recall some discussion where it's using separate configuration information). Assuming that it's actually using the terminal description, e.g., from ncurses, then mismatches would be due to (a) not using TERM=konsole, and (b) futher mismatches might be due to differences between the current konsole application and the ncurses description. A quick check (using tack and TERM=konsole for konsole 2.3.2) shows no issues. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net -- Antes de imprimir este correo electr??nico, considera tu responsabilidad medioambiental. Please consider your environmental responsibility before printing this email. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Mon, 2010-02-01 at 06:41 -0500, Thomas Dickey wrote: > On Mon, 1 Feb 2010, Miguel Pérez wrote: > > I'm using Konsole, set to the xterm (XFree 4.x.x) keyboard, and $TERM is > > xterm. These are the key combinations that produce escape sequences but > > aren't recognized by mc. Everything else either works, or doesn't produce a > > konsole doesn't send escape sequences that match xterm. > Use "infocmp konsole xterm" to see this. I've noticed similar problems with GNOME terminal in recent versions of MC included with Redhat Fedora. In particular the ctrl-pgup and ctrl-pgdn functionality was recently moved to the ctrl-home and ctrl-end key combos. These key combos don't work in GNOME terminal, so the ability to get instantly to the top and bottom of the file in the MC editor is now lost on GNOME-based GNU/Linux systems (unless the user manually remaps the functionality back to a usable key combo). I'm assuming that in the past, important functionality was intentionally limited to key combos that worked with major term programs like GNOME terminal and Konsole but it seems as if usability on those systems is no longer being tested (or perhaps no longer considered important)? Anyway, it would be nice to see MC work out of the box on GNOME terminal and konsole again on future versions. I love MC but I use GNOME terminal far more often than xterm. -Steve ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
Hello! Indeed, it's available now. I've updated to 4.7.0.1, though there's no difference with regards to Konsole keys. GNU Midnight Commander 4.7.0.1 Sistema de archivos virtual: tarfs, extfs, cpiofs, ftpfs, fish Editor de texto propio incluido Utilizando la biblioteca S-Lang instalada y terminales según terminfo Soporte subshell activo por defecto Soporte para operaciones en 2º plano Soporte para ratón en xterm y consola Linux Soporte para idioma local Soporte para cambio de juegos de caracteres Data types: char 8 int 32 long 64 void * 64 off_t 64 ecs_char 8 Cheers 2010/2/1 Yury V. Zaytsev > Hi! > > On Mon, 2010-02-01 at 11:50 +0100, Miguel Pérez wrote: > > > I'm using the mc package from Debian sid, version 3:4.7.0-1 on AMD64 > > with the following --version information: > > This is weird. 4.7.0.1 should have landed in Sid already. > > -- > Sincerely yours, > Yury V. Zaytsev > > -- Antes de imprimir este correo electrónico, considera tu responsabilidad medioambiental. Please consider your environmental responsibility before printing this email. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
Interesting, I'm using Konsole from KDE 3.5 (KDE 3.5.10, Qt 3.3.8b, Konsole 1.6.6) which doesn't have a "konsole" map nor my terminfo database (which came in the Ubuntu package ncurses-base 5.6+20071124-1ubuntu2) has an entry for konsole. 2010/2/1 Thomas Dickey > On Mon, 1 Feb 2010, Thomas Dickey wrote: > > On Mon, 1 Feb 2010, Miguel Pérez wrote: >> >> I love the ability to customize keybindings in 4.7. However, I've noticed >>> some keys cannot be bound because they aren't recognized properly by >>> Midnight Commander. When you hit an unrecognized sequence, mc will simply >>> skip the escape sequence up to a point and print the rest of it. >>> >>> I'm using Konsole, set to the xterm (XFree 4.x.x) keyboard, and $TERM is >>> xterm. These are the key combinations that produce escape sequences but >>> aren't recognized by mc. Everything else either works, or doesn't produce >>> a >>> >> >> konsole doesn't send escape sequences that match xterm. >> Use "infocmp konsole xterm" to see this. >> > > ...of course that's assuming that mc relies on the terminal description > (I seem to recall some discussion where it's using separate configuration > information). > > Assuming that it's actually using the terminal description, e.g., from > ncurses, then mismatches would be due to (a) not using TERM=konsole, and (b) > futher mismatches might be due to differences between the current konsole > application and the ncurses description. > > A quick check (using tack and TERM=konsole for konsole 2.3.2) shows no > issues. > > -- > Thomas E. Dickey > http://invisible-island.net > ftp://invisible-island.net > -- Antes de imprimir este correo electrónico, considera tu responsabilidad medioambiental. Please consider your environmental responsibility before printing this email. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
Hi! On Mon, 2010-02-01 at 11:50 +0100, Miguel Pérez wrote: > I'm using the mc package from Debian sid, version 3:4.7.0-1 on AMD64 > with the following --version information: This is weird. 4.7.0.1 should have landed in Sid already. -- Sincerely yours, Yury V. Zaytsev ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Mon, 1 Feb 2010, Thomas Dickey wrote: On Mon, 1 Feb 2010, Miguel P??rez wrote: I love the ability to customize keybindings in 4.7. However, I've noticed some keys cannot be bound because they aren't recognized properly by Midnight Commander. When you hit an unrecognized sequence, mc will simply skip the escape sequence up to a point and print the rest of it. I'm using Konsole, set to the xterm (XFree 4.x.x) keyboard, and $TERM is xterm. These are the key combinations that produce escape sequences but aren't recognized by mc. Everything else either works, or doesn't produce a konsole doesn't send escape sequences that match xterm. Use "infocmp konsole xterm" to see this. ...of course that's assuming that mc relies on the terminal description (I seem to recall some discussion where it's using separate configuration information). Assuming that it's actually using the terminal description, e.g., from ncurses, then mismatches would be due to (a) not using TERM=konsole, and (b) futher mismatches might be due to differences between the current konsole application and the ncurses description. A quick check (using tack and TERM=konsole for konsole 2.3.2) shows no issues. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Re: Some keys are not properly recognized in Konsole/xterm
On Mon, 1 Feb 2010, Miguel P??rez wrote: I love the ability to customize keybindings in 4.7. However, I've noticed some keys cannot be bound because they aren't recognized properly by Midnight Commander. When you hit an unrecognized sequence, mc will simply skip the escape sequence up to a point and print the rest of it. I'm using Konsole, set to the xterm (XFree 4.x.x) keyboard, and $TERM is xterm. These are the key combinations that produce escape sequences but aren't recognized by mc. Everything else either works, or doesn't produce a konsole doesn't send escape sequences that match xterm. Use "infocmp konsole xterm" to see this. -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
Some keys are not properly recognized in Konsole/xterm
I love the ability to customize keybindings in 4.7. However, I've noticed some keys cannot be bound because they aren't recognized properly by Midnight Commander. When you hit an unrecognized sequence, mc will simply skip the escape sequence up to a point and print the rest of it. I'm using Konsole, set to the xterm (XFree 4.x.x) keyboard, and $TERM is xterm. These are the key combinations that produce escape sequences but aren't recognized by mc. Everything else either works, or doesn't produce a distinguishable escape sequence so I won't expect it to work except if you use X. I've listed the escape sequences produced by Konsole (as seen with cat >/dev/null for example) and the gibberish text written by mc after failing to recognize the escape sequence: Shift+Tab: Konsole: ^[[Z mc ignores the key and prints: Z Alt+function keys: Konsole: ^[O3P ^[O3Q ^[O3R ^[O3S ^[[13;3~ ^[[17;3~ ^[[18;3~ ^[[19;3~ ^[[20;3~ ^[[21;3~ ^[[23;3~ ^[[24;3~ mc ignores the key and prints: 3P 3Q 3R 3S 13;3~ 17;3~ 18;3~ 19;3~ 20;3~ 21;3~ 23;3~ 24;3~ Alt+Shift+function keys: Same but 4 instead of 3 Control+function keys: Same but 5 instead of 3 Control+Shift+function keys: Same but 6 instead of 3 Control+Alt+function keys: Same but 7 instead of 3 Control+Alt+Shift+function keys: Same but 8 instead of 3 (Function keys and Shift+function keys work properly) Alt+Insert, Delete, Home, End: Konsole: ^[[2;3~ ^[[3;3~ ^[[1;3H ^[[1;3F mc ignores the key and prints: 2;3~ 3;3~ 1;3H 1;3F Alt+Shift+Insert, Delete, Home, End: Same but the last number is 4 instead of 3 (Ctrl+Insert, Delete, Home, End surprisingly work) Ctrl+Shift+Insert, Delete, Home, End: Same but the last number is 6 instead of 3 Ctrl+Alt+Insert, Delete, Home, End: Same but the last number is 7 instead of 3 Ctrl+Alt+Shift+Insert, Delete, Home, End: Same but the last number is 8 instead of 3 I'm using the mc package from Debian sid, version 3:4.7.0-1 on AMD64 with the following --version information: GNU Midnight Commander 4.7.0 Virtual File System: tarfs, extfs, cpiofs, ftpfs, fish With builtin Editor Using system-installed S-Lang library with terminfo database With subshell support as default With support for background operations With mouse support on xterm and Linux console With internationalization support With multiple codepages support Data types: char 8 int 32 long 64 void * 64 off_t 64 ecs_char 8 Any tips on how to make these keys work? Which terminal emulator, keyboard setting and $TERM value work best for you? Should I create a ticket in the mc website about this? Thank you very much in advance, ~Miguel -- Antes de imprimir este correo electrónico, considera tu responsabilidad medioambiental. Please consider your environmental responsibility before printing this email. ___ Mc-devel mailing list http://mail.gnome.org/mailman/listinfo/mc-devel
