-
Notifications
You must be signed in to change notification settings - Fork 54
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
Setting home to Ctrl-Home might stop working after some shortcuts get pressed #193
Comments
Hi @fulalas - thanks for reporting. Could you please share a copy of your |
Sure! |
Thanks @fulalas - I can reproduce the bug here too. I'm preparing a fix, hope to get it tested and push it this weekend. |
Hi @fulalas - the above commit should fix the reported issue. Please let me know if you still encounter problems. |
Yes, it works. Thanks a lot! I have 2 questions though:
|
OK, for the question 2 I found the answer: we need to compile using golang instead of gcc-go. |
Hi @fulalas - for question 1 - I will look into preparing a fix for this, I can see that it's currently hardcoded to |
Hi again - in 59afacd support for custom CMAKE_INSTALL_LIBDIR has been added. Please try it out and let me know if you encounter any issues (ideally by reporting a new bug). Thanks! |
It's working perfectly! Thanks a lot! |
After adding an emoji (
Ctrl-S
) or opening the contact list search (Ctrl-N
), myCtrl-Home
(home=\33\133\61\73\65\110) bind to home (beginning of history) stops working, and it doesn't work anymore until I quit nchat and open it again. The character that appears when I hitCtrl-Home
(after the issue starts) is: The same applies to end (end of history) associated to
Ctrl-End
(end=\33\133\61\73\65\106), and the character that appears instead is: It applies to both Telegram and WhatsApp contacts.
No other shortcut has this issue.
The text was updated successfully, but these errors were encountered: