On 8 January 2016 at 04:21, Eduardo A. Bustamante López
wrote:
>
> I now understand your points.
>
Thanks very much for taking a look at this.
> dualbus@hp ...src/gnu/bash % cat ~/.bash_history
> echo 1
> #1452197044
> echo a; sleep 1
> #1452197045
> echo b; sleep 1
>
On 1/7/16 9:16 AM, Andrew Kurn wrote:
> Bash Version: 4.3
> Patch Level: 30
> Release Status: release
>
> Description:
> When I put an extra space in the bind command, it fails silently
> and corrupts the keyboard map. Lower-case h no longer works.
>
> Repeat-By:
> bind Control-a: forward-searc
For what it's worth, It might be useful to have something like
'command' that (or maybe a flag to 'command', like "-f & -F" that would
search for functions for the 'command' either before ("-f")
the PATH search, or after ("-F"), for the case of the command not
being found in the PATH.
Reuti wro
hello Linda,
On Fri, Jan 8, 2016 at 9:14 PM, Linda Walsh wrote:
>
> For what it's worth, It might be useful to have something like
> 'command' [..]
that would be useful, a keyword like:
function p params;
that always calls function no matter what. maybe best would be to have
something like:
On Thu, Jan 7, 2016 at 9:32 PM, Chet Ramey wrote:
> On 1/5/16 8:08 AM, Greg Wooledge wrote:
>
>> imadev:~$ zap me
>> bash: zap: command not found
>> imadev:~$ history -d -1
>> bash: history: -1: history position out of range
>> imadev:~$ history -d end
>> bash: history: end: history position out o
