> empty lines. There is no programmable completion mechanism to complete
> on non-empty command names.
I'm wondering if it is worthwhile to add such a feature. I have run
into the problem that it is very slow to command complete an
incomplete command especially when other programs are accessing t
On 1/4/12 9:50 PM, Chet Ramey wrote:
> On 1/4/12 8:42 AM, Stas Sergeev wrote:
>
>> I just meant for the way to make the trap handler
>> executed when the foreground job is running.
>
> So you'd like the shell to act on a signal without `consulting' the
> foreground job? Take a look at http://www
On 1/4/12 8:42 AM, Stas Sergeev wrote:
> I just meant for the way to make the trap handler
> executed when the foreground job is running.
So you'd like the shell to act on a signal without `consulting' the
foreground job? Take a look at http://www.cons.org/cracauer/sigint.html ,
keeping in mind
On 1/4/12 8:54 PM, Peng Yu wrote:
> Hi,
>
> I want to customize the command completion for completing executables,
> I want to search in a file (which includes all the executables in
> PATH) rather than the default PATH variable. But I don't see how to do
> so, as the following help indicates that
Hi,
I want to customize the command completion for completing executables,
I want to search in a file (which includes all the executables in
PATH) rather than the default PATH variable. But I don't see how to do
so, as the following help indicates that it can only configure how to
complete the arg
On Wed, Jan 04, 2012 at 02:38:22PM +0800, jida...@jidanni.org wrote:
> Hmmm, as S. CHAZELAS said seems zsh also gives one a chance to reset an
> arbitrary positional parameter, e.g., the 42nd, whereas in bash one must
> set them all at once:
That is why named arrays are COMPLETELY superior and sho
04.01.2012 17:28, Chet Ramey wrote:
Hello Chet, I double-checked that, and with the attached
quick hack I was able to do:
trap bg USR1
and move the job to the background with just that SIGUSR1.
Do you think such a feature is worth being implemented?
I don't think there's enough need to change bg
On 1/4/12 7:20 AM, Stas Sergeev wrote:
> Hello Chet, I double-checked that, and with the attached
> quick hack I was able to do:
> trap bg USR1
> and move the job to the background with just that SIGUSR1.
> Do you think such a feature is worth being implemented?
I don't think there's enough need
03.01.2012 00:07, Chet Ramey wrote:
I tried:
---
trap bg USR1
---
Now if I first send SIGSTOP to the job and then SIGUSR1 to
bash, that works.
Is it possible to avoid sending SIGSTOP to the job, and make
the trap handler to do both things at once? Not that it is strictly
required since you alread
