bug-bash
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Question (and maybe, a suggestion)


From: Henning Bekel
Subject: Re: Question (and maybe, a suggestion)
Date: Sat, 15 Aug 2009 19:28:37 +0200
User-agent: KNode/4.3.0

Pablo Rodríguez Fernández wrote:

> Why there are some keyboard shortcuts that don't appear on man
> and web page manual? I've found some shortcuts very useful (and
> widely knowed by bash users) on this blog:
> http://linuxhelp.blogspot.com/2005/08/bash-shell-shortcuts.html
> and most of them are on man, but some of them are not or are not
> described like really works, for example Ctrl+C to stop a
> process or ctrl+D to exit and logout a process and bash,
> respectively (on job control environment). So:
> 
> Are these shortcuts non-standards on bash? If they are, why are
> they not explained on man or web manual

These keys are defined and handled by your terminal, not bash. 
Ctrl+C sends a SIGINT signal. See man bash, section SIGNALS on how 
bash handles it. Ctrl+D sends EOF (end of file). See the output of 
'stty -a' for other keys that are handled by your terminal before 
they even reach bash.

Note that for example Ctrl+S stops execution, while Ctrl+Q resumes 
it. In the bash manual you'll find that Ctrl+S is bound to the 
readline function forward-search-history by default, but since the 
terminal already handles this keyseq, it never 'gets through' to 
bash unless you'd disable/change it for your terminal via stty.

So these keys aren't documented in man bash since they aren't part 
of bash (or readline for that matter).

Regards,
Henning




reply via email to

[Prev in Thread] Current Thread [Next in Thread]