On Sun, Jun 06, 2021 at 05:00:21PM +0300, Ilkka Virta wrote:
> On Sun, Jun 6, 2021 at 2:49 PM Léa Gris wrote:
>
> For the second person, there's of course "thou", but for some reason,
> I've never heard anyone suggest using that in practice.
Hast thou never been to Yorkshire or Lancashire? :-)
On Thu, Mar 10, 2011 at 11:53:22AM -0800, Micah Cowan wrote:
>
> It wouldn't be difficult to write as a separate program, which is really
> how this should be handled. You could redirect a pipeline's STDOUT and
> STDERR to individual named pipes (FIFOs), and have a separate program
> read from bot
I have been playing with a terminal application which runs shells
plumbed as below:
fdwhat
0 pty slave
1 pty slave
2 some pipe
To get the various shells being used to work, some of them require
that '-i' be given for force interactive mode, fair enough.
One problem
I have been playing with a terminal application which runs shells
plumbed as below:
fdwhat
0 pty slave
1 pty slave
2 some pipe
To get the various shells being used to work, some of them require
that '-i' be given for force interactive mode, fair enough.
One problem
On Sun, Nov 11, 2007 at 09:56:11PM -0800, [EMAIL PROTECTED] wrote:
> Can someone provide a hint to this end? My deepest
> thanks for your time and any advice you might be
> able to provide.
I get exactly that behaviour with a program I have been working on.
I traced it to the fact that I ran bas
On Mon, Nov 12, 2007 at 08:03:38PM +, Derek Fawcus wrote:
> On Sun, Nov 11, 2007 at 09:56:11PM -0800, [EMAIL PROTECTED] wrote:
> > Can someone provide a hint to this end? My deepest
> > thanks for your time and any advice you might be
> > able to provide.
>
> I
On Sun, Nov 11, 2007 at 09:56:11PM -0800, [EMAIL PROTECTED] wrote:
>
> I had some difficulties getting job control working at
> first. I found that having the child process do a
> setpgrp() before forking to the bash instance made the
> error message about disabling job control go away.
Try set
