9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: revcomninos@gmail.com
To: 9fans <9fans@9fans.net>
Subject: [9fans] A few questions about sam 
Date: Thu, 22 Jul 2021 09:38:22 -0400	[thread overview]
Message-ID: <16269611020.38ad.33188@composer.9fans.topicbox.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1466 bytes --]

I have a few questions about sam which have not thus far been answered for me as I am reading the documentation. I thought that instead of putting them in separate posts, I could just put them into one.  I hope this is acceptable. Please let me know if is not. 

 * The sam window is not always responsive to commands. Under what specific conditions is this the case?
 * Must every sam file end with a newline? I.e. even files with simple text? I sometimes get the "?newline expected" error, which I would like to avoid if possible.
 * Is there a way to repeat the last entered command in sam without having to snarf and paste? I know one can repeat the last search with //.
 * The sam tutorial speaks of sam being "downloaded". (*A tutorial for the sam language*.) I am not exactly sure what "downloaded" means in this context.
 * In ed the "e" command allows one to switch files. It replaces the current file with another. To add a file to the list in sam, one should use B not e. Is that correct? I.e. it would seem "e" is allowed but not sam's natural way of doing things?
 * Is there a way of saving the state of one's windows in sam?
I have used "Emacs" for the last 8 years, but must confess that *sam* is very special. 
------------------------------------------
9fans: 9fans
Permalink: https://9fans.topicbox.com/groups/9fans/T60b5c1929a63b077-Mf1461873910abb65e9700e7e
Delivery options: https://9fans.topicbox.com/groups/9fans/subscription

[-- Attachment #2: Type: text/html, Size: 2119 bytes --]

             reply	other threads:[~2021-07-22 13:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-22 13:38 revcomninos [this message]
2021-07-22 13:57 ` Sigrid Solveig Haflínudóttir
2021-07-22 14:59   ` revcomninos
2021-07-22 19:10 ` mcz
2021-07-22 19:18   ` Charles Forsyth
2021-07-22 19:24 ` Charles Forsyth
2021-07-22 20:18   ` revcomninos
2021-07-22 23:45     ` Silas McCroskey
2021-07-23  4:47       ` revcomninos
2021-07-23  5:42         ` Silas McCroskey
2021-07-23  9:53           ` revcomninos
2021-07-27  0:56 ` Ethan Gardener
2021-07-27  6:34   ` revcomninos

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=16269611020.38ad.33188@composer.9fans.topicbox.com \
    --to=revcomninos@gmail.com \
    --cc=9fans@9fans.net \
    /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).