On Sat, 28 Feb 2015 11:29:14 +0100, Jean Delvare wrote:
> I think we will stay away from background sleep and wait for now, and
> instead use:
>
> read -t 1 -N 0
>
> This was suggested by an lm-sensors user and as far as I can tell it
> fits the bill with no downside.
For the record: it do
Hi Chet & everyone,
The goal is to notify the user if a long-running command (e.g. a
compilation) finishes, and the notification should mention the given
command.
$BASH_COMMAND seems to contain the command that's about to be
executed, whereas what we'd need is the command that just terminated.
$B
On 2/27/15 12:10 PM, Dave Anderson wrote:
>
> This issue was first reported with respect to the crash utility,
> which is an interactive program that uses the readline library.
>
> The problem occurs only if the crash utility is run from within
> an executable bash script, i.e., like so:
>
>
On 2/5/15 8:18 AM, Debarshi Ray wrote:
> What do you think? Having bash offer a way to reliably find the last
> foreground command interactively run by the user would be helpful.
>
I took a quick look at this, and I think what you want is $BASH_COMMAND
unless the last command is `fg'? If that's
Those two URLs are the same!
--
Ryan Cunningham
> On Mar 1, 2015, at 1:28 AM, Jonathan Hadida
> wrote:
>
> Hi there
>
> There is a dead link in the online bash manual for shopt:
> http://www.gnu.org/software/bash/manual/html_node/The-Shopt-Builtin.html
> [promptvars] "Controlling the Prompt
Hi there
There is a dead link in the online bash manual for shopt:
http://www.gnu.org/software/bash/manual/html_node/The-Shopt-Builtin.html
[promptvars] "Controlling the Prompt" should point to
http://www.gnu.org/software/bash/manual/bashref.html#Controlling-the-Prompt
It currently points to
h
