-
Notifications
You must be signed in to change notification settings - Fork 207
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
Can't find a way to "copy/open" the url added to an event #1291
Comments
What OS/shell/terminal are you using? AFAIC this is not the job ob the TUI application but should be handled by the terminal. |
Sorry, typo, i meant to say that it's in ikhal, due to the "interactive" mouse, not khal (the pure cli). I use alacritty anyway. |
The terminal should handle this. Using foot, I can press Ctrl+Shift+o and it highlights all visible links. |
Well, that works as a workaround too, i was opening it in my terminal editor and yanking the url from there. Thanks! |
This is a bit old, but i found something while -indirectly- investigating this issue that may be related. I tested this through kitty, alacritty and wezterm with bash, fish and zsh in all combinations and it's the same, and i realized something, i "can't" click links in ikhal, but if i shift-click them, they work. This only happens in some cli apps, while in others a simple click works. Any idea if this is some ikhal behaviour or similar? |
Hi,
I'm pretty new to ikhal, but i'm having an issue which i'm not sure if that's how it normally is or if i'm missing something.
Let's say i add an event to the calendar and i add an url to it, how can i copy/get/open/retrieve that url from the event later? I can't seem to be able to use the mouse to select the url text, i can't open it, parse it, or nothing, it's just there and i can't seem to find a way to integract with it.
This seems really odd, it'd be a killer feature for me, since it's pretty much the reason why i'm switching to khal (to store meeting urls).
Edit: Sorry, wrote khal, i mean ikhal, the interactive khal mode.
The text was updated successfully, but these errors were encountered: