Date: Fri, 15 Feb 2008 11:30:17 +0000 From: Alex Zbyslaw <xfb52@dial.pipex.com> To: "Matthew D. Fuller" <fullermd@over-yonder.net> Cc: freebsd-ports@FreeBSD.org Subject: Re: portupgrade-devel: 2 feature requests Message-ID: <47B577C9.50709@dial.pipex.com> In-Reply-To: <20080215110347.GV62553@over-yonder.net> References: <47B47052.8010404@gmail.com> <47B481E5.3010000@FreeBSD.org> <47B487DE.5090609@gmail.com> <47B4B6A0.6090200@FreeBSD.org> <20080215110347.GV62553@over-yonder.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthew D. Fuller wrote:
>And it
>doesn't tell me anything unless I happen to be watching the terminal
>at just the right time, and read quick before it scrolls off. I have
>to wait 'till the end for any details that.
>
>
portupgrade {your stuff} |& tee /tmp/portupgrade.log # [1]
Now you can just use less on /tmp/portupgrade.log and still have the
on-screen stuff. Of course, stuff like curses option screens look a bit
weird viewed in less, but if all you want is to find the last summary,
that should be easy with less and you could even write an alias to do it
automatically, I'm sure.
You can also go old-skool and just use ^S to stop the output, scroll
your xterm back up to see what you want, then ^Q to restart output. If
you ^S for too long the builds will pause when the output buffer fills
up, so you do have to remember to ^Q. [2]
--Alex
[1] csh syntax. "2>&1 |" for sh
[2] If you're not doing this under X, then scroll-lock, page-up/down
etc, and scroll-lock to restart.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?47B577C9.50709>