-
-
Notifications
You must be signed in to change notification settings - Fork 831
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Function Keys not working #36
Comments
Thank you for your report. This is probably an upstream bug; could you test it please https://launchpad.net/ubuntu-terminal-app |
There should not be any kde specific dependency in Ubuntu Terminal App. The error you see happens because the terminal can't locate the konsole plugin that comes with the applicaton. |
Hi, I just merged a pull request which should fix the problems with keytabs. Could you retest it and let me know if now everything is working fine? |
Thanks for the fix! Function keys work perfectly now. However, Shift+Up/Down is now scrolling the terminal, instead of passing the key combination to the terminal, which is the default behaviour in all the terminals I use. Should I file a new issue for that? |
Very well then. I was just looking into the issue with Shift+Up/Shift+Down. This is the expected default behavior but it should be customizable editing xterm.keytab. At the moment there is an issue and those values are hardcoded, but I will fix that soon. |
Ok, in the last master that should be fixed. Please open the xterm.keytab file and comment the following lines: key Up +Shift-AppScreen : scrollLineUp |
I'm closing this issue since it is related to a very old version. If it's still valid let me know and I'll reopen it. |
Completely forgot about this. I compiled latest master, edited |
Ubuntu 14.04, with pantheon DE. Any key combination involving function keys does not work.
--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/3406343-function-keys-not-working?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F479407&utm_medium=issues&utm_source=github).The text was updated successfully, but these errors were encountered: