zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: piping question
Date: Sat, 04 Oct 2014 14:01:48 -0700	[thread overview]
Message-ID: <141004140148.ZM7815@torch.brasslantern.com> (raw)
In-Reply-To: <87iojztyzg.fsf@gmail.com>

On Oct 4,  9:29pm, Christian Neukirchen wrote:
} Subject: Re: piping question
}
} Bart Schaefer <schaefer@brasslantern.com> writes:
} 
} >         local procself=/proc/self
} >         procself=${procself:A}  # Resolve symlink to actual PID
} >         local stdin
} >         exec {stdin}<&0
} >         rxvt -e most "$@" $procself/fd/$stdin
} >         exec {stdin}<&-
} 
} This works great with less -f, thanks!

Beware that whatever is on the left side of the pipe may not see EOF
when "less" exits, so you may need to arrange to interrupt it some
other way.

For who may be interested, the parent zsh is holding open the file
descriptor that serves as the read end of the pipe.  This happens only
if you backgroud the entire pipeline, e.g.

   cat /dev/zero | xmost &

The pipe here stays open in the parent shell until the whole job is done,
and trying to close it with <&- gives e.g.

  file descriptor 11 used by shell, not closed

So I think we still have a few bugs along the lines of workers/32171 and
32176 and perhaps 31919.


  reply	other threads:[~2014-10-04 21:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1412259225.3798.0@numa-i>
     [not found] ` <CAHYJk3Rx9iBLgeeKcnnu4N-56CqsgNyNhJof5+_M8H0Y0BBi9Q@mail.gmail.com>
     [not found]   ` <141003082330.ZM15100__40912.263657856$1412349949$gmane$org@torch.brasslantern.com>
2014-10-04 15:50     ` Christian Neukirchen
2014-10-04 18:17       ` Bart Schaefer
2014-10-04 19:29         ` Christian Neukirchen
2014-10-04 21:01           ` Bart Schaefer [this message]
2014-10-05  4:03             ` PATCH " Bart Schaefer
2014-10-05 17:20               ` Peter Stephenson
2014-10-05 12:17       ` Mikael Magnusson
2014-10-05 15:10         ` Christian Neukirchen
2014-10-05 17:04         ` Bart Schaefer
2014-10-05 20:40           ` Mikael Magnusson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=141004140148.ZM7815@torch.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=zsh-workers@zsh.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).