zsh-workers
 help / color / mirror / code / Atom feed
From: ZyX <zyx.vim@gmail.com>
To: zsh-workers@zsh.org
Subject: Re: Tee all output to log file?
Date: Wed, 2 Feb 2011 21:05:41 +0300	[thread overview]
Message-ID: <201102022105.41927@-zyx> (raw)
In-Reply-To: <alpine.LNX.2.01.1102021203580.2792@hp>

[-- Attachment #1: Type: Text/Plain, Size: 2157 bytes --]

Reply to message «Re: Tee all output to log file?», 
sent 20:28:13 02 February 2011, Wednesday
by Benjamin R. Haskell:

>     && exec env doinglogging=true ...
I used to write this as «doinglogging=true exec ...» or with
    doinglogging=true
    exec ...
Any reason why env command should envoked here I am not aware of?

Original message:
> On Wed, 2 Feb 2011, ZyX wrote:
> > Reply to message «Tee all output to log file?»,
> > sent 02:41:26 02 February 2011, Wednesday
> > 
> > by Benjamin R. Haskell:
> >> Is there something straightforward that I'm overlooking?  Is there a
> >> commonly used utility for this?  (`script` comes to mind, but I
> >> recall klunkiness when trying it in the past.)
> > 
> > If you don't like script, maybe you should try screen:
> >    (( $+logfile )) && \
> >    
> >        exec screen -L -c =(echo "logfile $logfile") -m -S script-$0 $0 $@
> 
> I find `screen` even more annoying than `script` for scripting purposes,
> wonderful though it is for interactive use.
> 
> I really just want the redirection, not the many extra features that
> `screen` adds.
> 
> Adding
> 
> > Does anybody know, why it does not work when I start screen in detached
> > mode?
> 
> Cf. above annoyance.  For doing something with Vim under Apache (using
> 
> :TOhtml), I recently resorted to this hackery:
> screen -q -d -m -S $sessionname vim -u NONE -N +'so $scriptname'
> (Then, loop, waiting for one of:
> 1: the Vim script to touch a marker file that indicated completion
> 2: a specified timeout, in case something errored out, preventing a
> clean Vim exit
> )
> screen -X -S $sessionname quit
> 
> 
> 
> Despite my annoyance (I'm easily annoyed), I tried your above
> suggestion.  It didn't capture stderr, so I added a flag that logging
> was in progress and added a redirect for it (also added '-q' to the
> `screen` commands):
> 
> (( $+logfile && ! $+doinglogging )) \
>     && exec env doinglogging=true screen -L -c =(echo "logfile $logfile")
> -q -m -S script-$0 $0 $@ (( $+doinglogging )) && exec 2>&1
> 
> Seems okay for what I'm doing.
> 
> Thanks,
> Ben

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2011-02-02 18:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LNX.2.01.1102011836170.2792@hp>
2011-02-02  5:04 ` ZyX
2011-02-02 17:28   ` Benjamin R. Haskell
2011-02-02 18:05     ` ZyX [this message]
2011-02-02 18:13       ` Benjamin R. Haskell

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=201102022105.41927@-zyx \
    --to=zyx.vim@gmail.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).