9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "rob pike, esq." <rob@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Sam & Acme & 8c questions
Date: Mon, 17 Jun 2002 09:58:11 -0400	[thread overview]
Message-ID: <cc92403e17e9d91a94b24aa5d7016320@plan9.bell-labs.com> (raw)

> Comment:  If you start sam with a single file argument it
> would be VERY convinient to have sam automatically
> open and display that file taking up its entire data area.

It would be reasonable to do that. You could change the code.
As forsyth observed, though, most people don't start sam to
edit a single file.  It's intended to be started and left around
as an editor at beck-and-call all the time.  The B shell
command is helpful here (B stands for 'boon').

Now read on.

> This would make quick edits a lot easier.  You could just
> type sam file.c and just start editing it.  Calling sam, selecting
> the single file, specifing the window size each time is a real
> pain.

It sounds like you don't know that you can specify the size
of the window with a click.  When you have the box/arrow
cursor, just click the mouse to maximize the cursor in the
area under the mouse.  'Maximize' means take up as much
area as possible without covering the command window.

> Question 2:  If I start a new copy of acme it isn't defaulting
> an rc shell window like it is when the system boots.  This is
> fine, but how do I start one?

% window acme

-rob



             reply	other threads:[~2002-06-17 13:58 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-17 13:58 rob pike, esq. [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-06-17 14:11 andrey mirtchovski
2002-06-17 14:35 ` Axel Belinfante
2002-06-17  9:36 forsyth
2002-06-17  9:14 Blake McBride

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=cc92403e17e9d91a94b24aa5d7016320@plan9.bell-labs.com \
    --to=rob@plan9.bell-labs.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).