When I need to open a terminal I press CTRL+ALT+T to save time. Most of the time absolutely nothing happens, I try to press same combination again, and still nothing happens. After like 5-8 tries terminal window finally appears.
hi guys, first sorry for my english
I'm a newbie about Linux, i've just installed fedora 18.
I am using Ubuntu 12.04. I was tinkering around learning the commands and stuff in terminal. I was a bit irritated that I couldn't copy and paste using only the keyboard. So I googled on how to add these shortcuts to my terminal.. I came upon these commands on DistroGeeks:
gconftool-2 -s /apps/gnome-terminal/keybindings/copy -t str 'c'
for adding Ctrl + C to copy...
I`m confused there are 3 kind of Terminal i have saw in ubuntu
xTerm,
Terminal (Gnome terminal) ctrl+shift+T and
virtual terminal ctrl+alt+F[1-6]
why are there many terminals and what is the point of those
specially gnome terminal and virtual terminal
Steps to reproduce:
have zsh as default shell
open a new terminal. for example, with Ctrl+Alt+t
press Ctrl+Shift+t to open a new terminal tab
"^T%" appears as the first line
I'm running ubuntu 11.10 with lxde and zsh-4.3.11
gnome-terminal doesn't have this problem
I came across a sentence in vimdoc:
Note: CTRL-S does not work on all terminals and might block
further input, use CTRL-Q to get going again.
and this key indeed hangs my vim. I was thinking that it was the fault of vim,
since there was no problem when I use C-s/C-x C-s in emacs nox.
Hi guys this might seem like a fairly easy question but for the life of me I can't figure out how to invoke CTRL-a in a linux terminal session. I am trying to share a screen using screen.
When I press CTRL-/ in a graphical terminal (e.g. xterm) I get "undo". However, in a virtual terminal (e.g.
I have a program which is supposed to handle SIGINT and gracefully shut down. When I run this program from a terminal without backgrounding it I can shut it down just fine using Ctrl-C. Inspecting the logs shows that everything worked as expected.
When I open a separate terminal and call kill -2 [pid] or kill -s INT [pid] it does nothing.