[clug] .bash_aliases and .bashrc
scott.ferguson.clug at gmail.com
Sun Oct 19 01:39:52 MDT 2014
On 19/10/14 19:16, Francis Whittle wrote:
> On Sun, 2014-10-19 at 13:36 +1100, Scott Ferguson wrote:
>>> Humour about "the Any key" aside,
>> I'm sorry that bothers you.
> Bothers, no. Just noted :)
I've become hypersensitive of late after being accused of "rough tones"
(huh - tone in writing exists in the mind of the reader doesn't it). And
sarcasm (which I'm capable of, but wasn't being at the time) the
complainant just couldn't reconcile a post that criticized their comment
and was signed "kind regards"
>>> surely this should make the current terminal wait for a signal?
>> I don't understand your question? (I'm a bit thick)
>> Yes - the pause function makes the terminal wait for a *key-press*
>> signal, by design.
>> Is that what you mean?
> This is more of a "If it looks like a C library function, it should
> behave like that function" jibe.
Whoosh! (see - I 'told' you I can be a bit thick!)
Humorous jibe aside (ha!) - I could make it a function that takes a
message parameter (or maybe a parameter that defines the key press to
> pause(void) from unistd.h suspends the current process until a signal
> (e.g. SIGINT, SIGQUIT, SIGCONT, SIGALRM - actually pause + SIGALRM is
> how sleep works on most systems, ...) is received.
What I should/will do, is upper-case the first letter. Something I
usually do to avoid conflict with real commands.
Thanks for answering my question. Much appreciated.
"Sarcasm is the lowest form of humour" ~ Joseph Stalin
More information about the linux