Here's a bash feature I'd love to see, but don't have time to
implement myself: a "--free-slot" flag to 'wait' that will wait until
there is at least one free "slot" available, where a slot is basically
a CPU core.
Example usage:
$ for ((n=0; n<100; n++)); do
my_experiment $n > $n.out &
Hello bug-bash,
please find attached a bashbug report. I am not sure how to follow-up
then, could you advise ?
Thanks,
Serge
From: root
To: bug-bash@gnu.org
Subject: bash cores if nscd disabled on Solaris LDAP sasl/gssapi client
Configuration Information [Automatically generated, do not cha
Chet Ramey wrote:
Chet Ramey wrote:
How come you didn't mention '-o nospace' when I was trying to write a
completion for directory names from a non-PWD reference point? ;-)
Did it exist then? :-)
Did it not? I'm running 3.2-22.fc9 (3.2.33(1)-release). I'm referring to
the thread http://pe
> Chet Ramey wrote:
> How come you didn't mention '-o nospace' when I was trying to write a
> completion for directory names from a non-PWD reference point? ;-)
Did it exist then? :-)
Chet
--
``The lyf so short, the craft so long to lerne.'' - Chaucer
Chet Ramey, ITS, CWRU[EMAIL PROTECTE
Chet Ramey wrote:
Description:
I don't know if this is a bug or not, but it has to do with programmable
auto completion. Whenever the options have multiple words I don't get what I
want.
You can get filename-like quoting by specifying that readline should treat
the matches returned by the c
Thank you, that's exactly what I wanted.
On Thu, Oct 2, 2008 at 09:16, Chet Ramey <[EMAIL PROTECTED]> wrote:
> > Description:
> > I don't know if this is a bug or not, but it has to do with
> programmable
> > auto completion. Whenever the options have multiple words I don't get
> what I
> > w
> Description:
> I don't know if this is a bug or not, but it has to do with programmable
> auto completion. Whenever the options have multiple words I don't get what I
> want.
You can get filename-like quoting by specifying that readline should treat
the matches returned by the completion fun
