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 01:29:58 +0800 [thread overview]
Message-ID: <b954b2060802280929k6a5259fax7073692362bac00d@mail.gmail.com> (raw)
In-Reply-To: <20080228085815.GA830@shodan.homeunix.net>
Hi,
Thanks. But it seems that this instruction only works in ed. With
sam, however, the printed area will be increasely expanded each time
rather than be disjoined ones.
On Thu, Feb 28, 2008 at 4:58 PM, Martin Neubauer <m.ne@gmx.net> wrote:
> .,.+20p
>
>
>
> > I checked the upe, and also the document of GNU ed. It seems that the
> > `b' command is really a new feature. Then, when such a browse command
> > was not here yet, how conveniently did users browse in page to page
> > manner in ed or sam -d?
> >
> > Thanks.
>
--
HZ
next prev parent reply other threads:[~2008-02-28 17:29 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 [this message]
2008-02-28 19:39 ` Martin Neubauer
2008-02-29 3:24 ` Hongzheng Wang
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=b954b2060802280929k6a5259fax7073692362bac00d@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).