9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Blake McBride <blake@integra-online.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Sam & Acme & 8c questions
Date: Mon, 17 Jun 2002 09:14:48 +0000	[thread overview]
Message-ID: <ugmvtpl0eq1se2@news.supernews.com> (raw)

Okay, I'm getting into this.  I used sam for a while and
got used to it but going in and out was a pain - enter acme.
Anyway, I have some questions and comments.

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.
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.  Perhaps if more than one file is specified it should
just auto-display the first and allow manual selection of the
other files.  Perhaps this should be done with a command
line optional argument (although I don't think so).

Question 1.  In sam (or acme) how can I select more lines
than can fit on the screen?  For example let's say I'm editing
a file with 1000 lines and 40 are being displayed (because
that is all that will fit).  Let's say I want to snarf an 80 line
function.  How can I do that?

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?

Question 3:  Most C compilers (or actually their pre-processors)
have some standard defines so that your program can tell what
it's being compiled for at compile time (like _unix_ or __WIN32).
Does the Plan 9 compiler have some standard defines?

Thanks a lot.

Blake McBride
blake@intega-online.com


             reply	other threads:[~2002-06-17  9:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-17  9:14 Blake McBride [this message]
2002-06-17 10:52 ` [9fans] " Douglas A. Gwyn
2002-06-17  9:36 [9fans] " forsyth
2002-06-17 13:58 rob pike, esq.
2002-06-17 14:11 andrey mirtchovski
2002-06-17 14:35 ` Axel Belinfante

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=ugmvtpl0eq1se2@news.supernews.com \
    --to=blake@integra-online.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).