I added two user defined tags: leftBracket -> { rightBracket -> } and created shortcuts: leftBracket -> Ctrl+7 rightBracket -> Ctrl+0 Afterwards, Kile still takes inputs, but no arrow keys, no backspace, no control key. Restarting Kile or removing the changes made, does not help. Reproducible: Didn't try Steps to Reproduce: 1.I added two user defined tags: leftBracket -> { rightBracket -> } 2.and created shortcuts: leftBracket -> Ctrl+7 rightBracket -> Ctrl+0 3. type an arrow key...
Created attachment 71313 [details] kilerc I tried to reproduce the issue but I didn't succeed. I guess something else must have happened as setting the shortcuts in the way you described it shouldn't influence the arrow or backspace keys. Could you maybe attach the ~/.kde/share/config/kilerc and ~/.kde/share/apps/kile/kileui.rc files here? Thanks.
Thanks for your quick reply, please find the files attached. I did not do anything in the meantime. > > Cheers > Andre > > On 22.05.2012 18:20, Michel Ludwig wrote: >> https://bugs.kde.org/show_bug.cgi?id=300459 >> >> --- Comment #1 from Michel Ludwig<michel.ludwig@kdemail.net> --- >> I tried to reproduce the issue but I didn't succeed. I guess >> something else >> must have happened as setting the shortcuts in the way you described it >> shouldn't influence the arrow or backspace keys. >> >> Could you maybe attach the ~/.kde/share/config/kilerc and >> ~/.kde/share/apps/kile/kileui.rc files here? Thanks. >> >
Created attachment 71314 [details] kileui.rc
Ok, the problem originates from the new shortcut scheme that you have created. If you set the user tag shortcuts inside the default scheme, everything should work fine. I'm inclined to say that this is a bug indeed as the default shortcuts should still be set if one creates a new shortcut scheme. Forwarding to kdelibs.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!