On 4/23/15 3:28 AM, Valentin Bajrami wrote:
> Chet,
>
> 'history' is not the builtin command in this case. 'history' is a normal
> file containing awk code (see my first post). I named it history because
> it does some calculations and shows the 10 most used commands. The file is
> expecting some
Chet,
'history' is not the builtin command in this case. 'history' is a normal
file containing awk code (see my first post). I named it history because
it does some calculations and shows the 10 most used commands. The file is
expecting some input from a command (pipe) like the 'history' builtin
On 4/21/15 4:30 AM, Valentin Bajrami wrote:
> The behaviour on bash 4.2.53(1)-release seems to be different. For example
>
> $ ./history | his
> bash: his: command not found...
> [ Here I press enter to get back to the terminal. This wasn't the case on
> 4.3.x ]
>
> [1]+ Stopped
The behaviour on bash 4.2.53(1)-release seems to be different. For
example
$ ./history | his
bash: his: command not found...
[ Here I press enter to get back to the terminal. This wasn't the case on
4.3.x ]
[1]+ Stopped ./history | his
$ jobs -l
[1]+ 4784 Stopped (tty input)
On 4/20/15 5:24 PM, Valentin Bajrami wrote:
> Hi Chet,
>
> I see. But how would I avoid this? Using Fedora 21 here and my
> command_not_found_handle() is
It's hard to say without knowing what pk-command-not-found does. What
does this do when you just run `his' from the command line and let it
e
Hi Chet,
I see. But how would I avoid this? Using Fedora 21 here and my
command_not_found_handle() is
command_not_found_handle ()
{
local runcnf=1;
local retval=127;
[[ $- =~ i ]] || runcnf=0;
[ ! -S /var/run/dbus/system_bus_socket ] && runcnf=0;
[ ! -x /usr/libexec/packageki
On 4/20/15 5:01 PM, Valentin Bajrami wrote:
> Now when running ./history | his where his is not an existing command it
> fails and adds an entry in the job list.
>
> $ ./history | his
>
> [2]+ Stopped ./history | his
> bash: his: command not found...
>
>
> Running twice the o
Hi everyone,
While testing an awk script and piping the script to a command the
following seem to occur. Not sure if this is even a bash problem. Here are
some details about my configuration:
$ echo "$BASH_VERSION"
4.3.33(1)-release
The file called 'history' contains the following code
$ cat hi
