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

Custom C-i bindings do not play well with citar-open and RET #802

Open
dschrempf opened this issue Sep 25, 2023 · 9 comments
Open

Custom C-i bindings do not play well with citar-open and RET #802

dschrempf opened this issue Sep 25, 2023 · 9 comments
Labels
bug Something isn't working

Comments

@dschrempf
Copy link

Describe the bug
In citar-open, pressing RET results in an error <C-i> is undefined.

To Reproduce

  1. Set
  (define-key input-decode-map (kbd "C-i") [C-i])
  1. Bind <C-i>, for example using general:
  (general-mmap "<C-i>" #'better-jumper-jump-forward)
  1. Run citar-open and press RET.

Expected behavior
The entry is opened.

Screenshots
If applicable, add screenshots to help explain your problem.

Emacs version:
29.1

Context

  • Most likely related to RETURN has no effect in citar minibuffer #707.
  • Setting (setq citar--multiple-setup (cons "<tab>" "RET") is a workaround (but in my opinion it should not be necessary).
  • Could be a problem of my setup (I try to distinguish between C-i and <tab>
@dschrempf dschrempf added the bug Something isn't working label Sep 25, 2023
@bdarcus
Copy link
Contributor

bdarcus commented Sep 25, 2023

Just in case, OS and (if relevant) distro and desktop?

@dschrempf
Copy link
Author

dschrempf commented Sep 26, 2023

Thanks for having a look!

+ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.54, NixOS, 23.11 (Tapir), 23.11.20230919.5ba549e`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.17.0`
 - nixpkgs: `/nix/store/cz973qsjldbw4x7fx0rwcvhr9k645vz2-source`

I use XMonad.

@bdarcus
Copy link
Contributor

bdarcus commented Sep 27, 2023

When you get a chance, @aikrahguzar, any input?

@aikrahguzar
Copy link
Contributor

This is exactly #707 and I don't know of any completely clean solution for that since it is a workaround for a limitation of completion ui. Changing the default value of citar--multiple-setup to use <tab> is the only option I can think of but I don't know if there are any unintended consequences.

@bdarcus
Copy link
Contributor

bdarcus commented Oct 1, 2023

I don't know of any completely clean solution for that since it is a workaround for a limitation of completion ui. Changing the default value of citar--multiple-setup to use <tab> is the only option I can think of but I don't know if there are any unintended consequences.

@dschrempf - thoughts?

Doesn't seem like there's much we can do about this?

@dschrempf
Copy link
Author

Using the workaround is an option for me, but I do not know if this situation is desired.

I do not know the internals of citar (Does it use keybinding macros?), but in opinion, rebinding a key should not lead to an error in a seemingly independent library. If there is no way to fix this, so be it 🤷. Citar is a great package, thank you!, and I am happy that it works the way it does 😄.

@bdarcus
Copy link
Contributor

bdarcus commented Oct 10, 2023

@aikrahguzar did mention changing the default value as a possibility.

@dschrempf
Copy link
Author

dschrempf commented Oct 10, 2023

This would mean that citar does not anymore work as expected when Emacs is used from the terminal, is that so?

Also: The completion UI that you mentioned. Is this an external library?

@bdarcus
Copy link
Contributor

bdarcus commented Oct 11, 2023

This would mean that citar does not anymore work as expected when Emacs is used from the terminal, is that so?

IDK; that would obviously be a problem if so.

Also: The completion UI that you mentioned. Is this an external library?

I think he meant completing-read.

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

3 participants