Hi all,
I just noticed some strange behavior with the kill builtin and was wondering
whether
this is a bug or not. The following applies to using kill on stopped processes
(I didn't
test it on running processes).
When using 'kill jobspec', the SIGTERM signal is sent to the process followed
b
On 10/1/13 7:04 AM, Job Noorman wrote:
> Hi all,
>
> I just noticed some strange behavior with the kill builtin and was wondering
> whether
> this is a bug or not. The following applies to using kill on stopped
> processes (I didn't
> test it on running processes).
>
> When using 'kill jobspe
On 9/27/13 3:57 AM, Jeremy Lin wrote:
> I'm writing a completion where, in some cases, I'd like to use
> COMPREPLY=() to indicate that no more arguments to a command are
> expected, but in other cases, I'd like to offer the default Readline
> behavior for filename completions.
>
> So, if I have a
On Tue, Oct 1, 2013 at 1:35 PM, Chet Ramey wrote:
> On 9/27/13 3:57 AM, Jeremy Lin wrote:
>> I'm writing a completion where, in some cases, I'd like to use
>> COMPREPLY=() to indicate that no more arguments to a command are
>> expected, but in other cases, I'd like to offer the default Readline
>>
On 10/1/13 4:55 PM, Jeremy Lin wrote:
> Thanks, I actually ended up with the same solution (for Bash 4.0 and above,
> where 'compopt' is available, anyway). I just set '+o default' at the top of
> the
> completion function and then set '-o default' as needed. Unfortunately, for
> earlier versions
