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
How do SIGINT with Ctrl C and use Ctrl C for Copy? #3696
Comments
Don't use |
FWIW, there's some more discussion on this topic in #1919. |
I'm new to alacritt. Tho this seems to work (Ctrl-C to copy, Ctrl-V to paste and ctrl-shift-C to ^C)
|
They don't, they will make your terminal unusable, since you now can't use the ^V binding anymore. |
Does this make it unusable? What is Ctrl-V used for by default? I just tried this myself and it seems to work fine. If it is needed for some terminal applications couldn't we have a Ctrl+Shift+V send ^V instead? It would be nice to have a context aware ctrl-c (if something is running, cancel, if not then copy) but this is a fair compromise. On the discussion, this isn't just a Mac -> Linux thing, I've been using Linux exclusively for 10 years. Every other application across Windows/Mac and Linux uses Ctrl-C to copy. Having to use a different key for one application messes with my muscle memory. |
I think I might actually prefer just swapping them... but I'd need to actually think through the possible consequences of this, beside just confusing the notion of control being One thing that I find ironic right off the bat, is that this suddenly makes my macOS interrupt require one additional key for no good reason, to be consistent. |
@pokebadgerswithspoon Thanks. This works for me and could be highlighted as a quickfix in the docs or somewhere. |
Look I get why it isn't a great idea to not use ctrl-c for copy, but if nothing is selected at the time and you press ctrl-c why not have it ^C interrupt as well? Is it even possible to have the alacritty do both with the way it is right now? (sorry i do not know) BTW -- Alacritty is beautiful / fast / and well it is beautiful. <3 u all. |
My current approach (for those interested):
In my Alacritty setup I do NOT define Nothing seems to have broken. I am glad to junk |
I wanted to achieve the same goal and tried this approach. Then I noticed that alacritty switched to a toml based configuration. Of course it wouldn't accept "\x03" since it is a YAML specific thing I spend a good few hours to make it work with TOML. I want to spare you guys the same effort and show you how it is done in TOML: [keyboard] |
I just installed Alacritty and coming from gnome-terminal. Usually, I can
tail -f *.log
and it would split out the new logs but I would useCtrl+C
to terminate the tail command. I can't do that here because I've setCtrl+C
set toCopy
.System
OS: Linux
Version: alacritty 0.4.1
Linux/BSD: Ubuntu 19.10 Tmux
Logs
Crashes: STDERR, STDOUT
Font/Terminal size:
alacritty -vv
Created log file at "/tmp/Alacritty-28330.log"
[2020-05-07 06:12] [INFO] Welcome to Alacritty
[2020-05-07 06:12] [INFO] Configuration loaded from "/home/nookta/.config/alacritty/alacritty.yml"
[2020-05-07 06:12] [DEBUG] Estimated DPR: 1
[2020-05-07 06:12] [DEBUG] Estimated Cell Size: 10 x 20
[2020-05-07 06:12] [DEBUG] Estimated Dimensions: None
[2020-05-07 06:12] [INFO] Device pixel ratio: 1
[2020-05-07 06:12] [INFO] Initializing glyph cache...
[2020-05-07 06:12] [INFO] ... finished initializing glyph cache in 0.042658813s
[2020-05-07 06:12] [INFO] Cell Size: 10 x 20
[2020-05-07 06:12] [INFO] Padding: 0 x 0
[2020-05-07 06:12] [INFO] Width: 800, Height: 600
[2020-05-07 06:12] [INFO] PTY Dimensions: Line(30) x Column(80)
[2020-05-07 06:12] [INFO] Initialisation complete
[2020-05-07 06:12] [DEBUG] Term::resize dimensions unchanged
[2020-05-07 06:12] [INFO] Width: 800, Height: 600
[2020-05-07 06:12] [DEBUG] New num_cols is 192 and num_lines is 50
[2020-05-07 06:12] [INFO] Width: 1920, Height: 1009
[2020-05-07 06:12] [DEBUG] New num_cols is 80 and num_lines is 30
[2020-05-07 06:12] [INFO] Width: 800, Height: 600
[2020-05-07 06:12] [INFO] Goodbye
Deleted log file at "/tmp/Alacritty-28330.log"
Keyboard and bindings:
alacritty --print-events
The text was updated successfully, but these errors were encountered: