From: "Hongzheng Wang" <wanghz@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Fwd: Does sam have browse command
Date: Fri, 29 Feb 2008 11:24:14 +0800 [thread overview]
Message-ID: <b954b2060802281924u70d07ffn87e4f3a5f543c694@mail.gmail.com> (raw)
In-Reply-To: <20080228193946.GA851@shodan.homeunix.net>
Thanks. It works. So an encapsulated browse command might be more
convenient for sam.
Just a wish :-)
On Fri, Feb 29, 2008 at 3:39 AM, Martin Neubauer <m.ne@gmx.net> wrote:
> Well, for what b provides this is probably good enough. You can use .+,.+20p for
> disjoined chunks, or .+-,.+20p for what b does in ed. It's all in the man
> page, though.
--
HZ
prev parent reply other threads:[~2008-02-29 3:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-27 3:40 [9fans] " Hongzheng Wang
2008-02-28 2:56 ` [9fans] Fwd: " Hongzheng Wang
2008-02-28 8:58 ` Martin Neubauer
2008-02-28 17:29 ` Hongzheng Wang
2008-02-28 19:39 ` Martin Neubauer
2008-02-29 3:24 ` Hongzheng Wang [this message]
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=b954b2060802281924u70d07ffn87e4f3a5f543c694@mail.gmail.com \
--to=wanghz@gmail.com \
--cc=9fans@cse.psu.edu \
/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.
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).