Skip to content
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

Closed
fulalas opened this issue Feb 25, 2024 · 9 comments
Closed
Assignees
Labels
bug Something isn't working

Comments

@fulalas
Copy link

fulalas commented Feb 25, 2024

After adding an emoji (Ctrl-S) or opening the contact list search (Ctrl-N), my Ctrl-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 hit Ctrl-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.

@fulalas fulalas added the bug Something isn't working label Feb 25, 2024
@d99kris
Copy link
Owner

d99kris commented Mar 6, 2024

Hi @fulalas - thanks for reporting. Could you please share a copy of your ~/.nchat/key.conf? Either copy and paste the content in a comment here, or attach it as-is (might require making a copy of the file with a .txt suffix for Github to accept it).

@fulalas
Copy link
Author

fulalas commented Mar 6, 2024

Sure!

key.conf.txt

@d99kris
Copy link
Owner

d99kris commented Mar 22, 2024

Thanks @fulalas - I can reproduce the bug here too. I'm preparing a fix, hope to get it tested and push it this weekend.

@d99kris
Copy link
Owner

d99kris commented Mar 24, 2024

Hi @fulalas - the above commit should fix the reported issue. Please let me know if you still encounter problems.

@fulalas
Copy link
Author

fulalas commented Mar 24, 2024

Yes, it works. Thanks a lot!

I have 2 questions though:

  1. is there a way to make -DCMAKE_INSTALL_LIBDIR=lib64 work? On some distros we don't want 64-bit libs to go into /usr/lib, but /usr/lib64 instead. I tried to use it on your project, but it seems it doesn't have any effect.
  2. the nchat version I was using before was built on Arch, and magically libwmchat.so didn't depend on libgo, but now that I'm building on PorteuX (Slackware current based), it's depending on libgo, which is a big showstopper for me. Do you know how to workaround that?

@fulalas
Copy link
Author

fulalas commented Mar 25, 2024

OK, for the question 2 I found the answer: we need to compile using golang instead of gcc-go.

@d99kris
Copy link
Owner

d99kris commented Mar 29, 2024

Hi @fulalas - for question 1 - I will look into preparing a fix for this, I can see that it's currently hardcoded to lib.

@d99kris
Copy link
Owner

d99kris commented Mar 30, 2024

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!

@fulalas
Copy link
Author

fulalas commented Mar 30, 2024

It's working perfectly! Thanks a lot!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants