From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14516 invoked by alias); 20 Sep 2015 06:25:31 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 36568 Received: (qmail 21335 invoked from network); 20 Sep 2015 06:25:31 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham autolearn_force=no version=3.4.0 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version:content-type; bh=oMebcV9JwUQuu6y3NZ3VwxNklx4PzLyQygdr/WyYJVI=; b=Fgtx9OAQ5k5Suub0s4MoQJsQbEW49WSxMOk1N+wK7Zv/YJ0206hbmL980UcqKhpGaD lJfrif99iLn0dmjFYQqrFp3iE3P4mTCeqjREZbTSeFKtfTuv4Gs8tvx4odg7xgg8GB29 URV9OrYjO5clOf+iBO+VhrYbboyQkd269tErzeSNYvbeQYA1rS2e4CzjJoJ8S1s97Yue WxxSFHYOaVn9AKJ5VLqcU8fROpK+wP64FDKfxGCZ95Zs+mq2Tkc6E2wqJB4MXsIaUgG1 mquGaXT0l1CEIvhVG/U+pyCO8QUEWpRyeJWNiWn1OMGYiCC/m0cJjGhWqbWh4E4QwaXE rMrg== X-Gm-Message-State: ALoCoQkI5XOImKU9Xg/x8VvOhiHU5AGsxWQXX0VODMslP8JlLFlRlEvW9xE3hj7Soh9Y6RDtWyHN X-Received: by 10.182.97.97 with SMTP id dz1mr7996417obb.17.1442730327614; Sat, 19 Sep 2015 23:25:27 -0700 (PDT) From: Bart Schaefer Message-Id: <150919232525.ZM5096@torch.brasslantern.com> Date: Sat, 19 Sep 2015 23:25:25 -0700 In-Reply-To: Comments: In reply to Sebastian Gniazdowski "print returning via REPLY" (Sep 20, 7:59am) References: X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: print returning via REPLY MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Sep 20, 7:59am, Sebastian Gniazdowski wrote: } } The code of print builtin is rich into various states. I was thinking } about adding REPLY support to it, but it seems to be too complicated } for me. Maybe someone has better overview of the various states of the } function, and could add the REPLY support? Maybe it isn't actually } hard? My motivation behind this is to be able to quickly expand tabs - } doing a fork to read print's output is slow. This would require moving the first block of HAVE_OPEN_MEMSTREAM stuff (and it's #else, of course) from below the OPT_HASARG(ops, 'x') test to above it, so that the result of the tab processing is captured; and then figuring out how/where to do the corresponding cleanup (maybe just a "goto" that jumps to the near the end of the function). Aside, the doc doesn't actually say that -x can't be used with -z/-s/-f (and print doesn't complain about the attempt) even though that is the case.