Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: problem building zsh in background
- X-seq: zsh-users 6823
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Zsh-users <zsh-users@xxxxxxxxxx>
- Subject: Re: problem building zsh in background
- Date: Mon, 1 Dec 2003 06:56:06 +0000
- In-reply-to: <87fzg5ax4d.fsf@xxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <m3d6bgq2tk.wl%petersen@xxxxxxxxxx> <87d6bgrxml.fsf@xxxxxxxxxxxxxxxx> <m3vfp7o6c8.wl%petersen@xxxxxxxxxx> <877k1ngcp5.fsf@xxxxxxxxxxxxxxxx> <m365h68uk6.wl%petersen@xxxxxxxxxx> <m3y8u26r3t.wl%petersen@xxxxxxxxxx> <87zneewgvd.fsf@xxxxxxxxxxxxxxxx> <20031130185652.GA26891@xxxxxxxxxxxxxxxxxx> <87fzg5ax4d.fsf@xxxxxxxxxxxxxxxx>
On Nov 30, 10:08pm, Philippe Troin wrote:
}
} Okay, what about the following behavior:
}
} - keep the second patch (will fail if ran from cron or any other
} situation where there is no ctty)
}
} - add a --with-working-tcsetpgrp / --without-working-tcsetpgrp switch
} to force configure to skip the test (instead of failing) and assume
} a working / non-working tcsetpgrp
}
} Would that satisfy everyone?
Other than that it should just be --with-tcsetpgroup (what's the point of
"working"? Is there a --with-broken-tcsetpgroup option?), I think that
sounds fine.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author