sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: hc05@summitis.com
To: sam-fans@hawkwind.utcs.toronto.edu (Sam mailing list)
Subject: Re: Editors compendium & sam
Date: Mon, 27 Mar 1995 15:40:47 -0500	[thread overview]
Message-ID: <9503272013.AA21809@cheetah> (raw)

Thanks for the replies so far on the editor compendium.  I'll respond to both
Erik & Rob here.  A few of the suggestions don't work in all situations, so 
we'll have to decide how to state them.

Beirne

From: Erik Quanstrom <uunet!sartre.minerva.bah.com!quanstro>

>>Goto column number: It says you can do this, but I don't know how.  I know
>>	I can put the cursor anywhere I want with the mouse, but don't know
>>	how to go to the nth column on a line.
>-/^/+#10
>
>go to 10th column

Good, but it won't work on the first line, if this matters.

>>Goto begin next line: ?
>+,/^/ (0th postion on next line)

This doesn't work if you are at the beginning of a line.  How about just /^/

>
>but for god sakes, use the mouse.

Agreed.

>
>>Goto begin prev line: ?
>-
>-,/^/

This selects the previous and current lines.

>
>>Move cursor up by page: yes, using the mouse on the scrollbar.
>using up on keyboard, too
>>Move cursor dn by page: yes, using the mouse on the scrollbar.
>using down on keyboard, too

Of course!

>
>>Scroll curr line to TOS/MOS/BOS: Yes/No/No.
>use the mouse

You can use the mouse to move the current line to the top of the screen, but
there is not a simple way to move the current line to the middle or bottom,
short of a bunch of trial-and-error clicks, unless there is something I am
missing.
>
>>Binary editor: They give three categories.  I think this one is closest:
>>	"displays binary characters doesn't do CR/LF conversion on binary files"
>elides \0.

Good.  I'll have to remember this.

From: uunet!plan9.att.com!rob

>it seems that sam doesn't fit their model very well, which doesn't surprise me.
>one thing they can't encompass is that the mouse language and command
>language solve different sets of problems.
>
I agree, since sam has almost no features and almost infinite capabilities.

>general comments: there is no such thing (in sam as i wrote it, at least) as a
>sam macro, so i'm not sure what you mean by the word 'macro'.

I looked at the compendium again, and found a better choice than to say macros,
which is to use the following, so I will substitute this wherever I said macro.

     ^     The editor does not have a specific command to do this, but
           it can be very easily done with a couple of keystrokes.
           I.e.  Clear buffer may be implemented as:
                     select buffer contents command,
                     delete selection.

The compendium does have one item as being implemented with a macro, which is
"Spell check select text".  I did this with an external script that I wrote
that is a front end to ispell, but this should go in the filter category in
the compendium rather than as a macro.

>
>details:
>
>	Goto column number: It says you can do this, but I don't know how.  I know
>		I can put the cursor anywhere I want with the mouse, but don't know
>		how to go to the nth column on a line.
>sam has no notion of column, only characters.
>	Goto begin next line: ?

This highlights the next line.

>+
>	Goto begin prev line: ?
>-

This highlights the previous line.

>	Tag search: Yes, with the help of an external program.
>if the program's not there, does that count?

Good question.  I just looked, and I got the tag program with the samx
extensions, which I am not counting here, although I couldn't live without
them.

>
>	Interactive debugging: No.
>with acid, the external B command does a nice job.

Is acid available for UNIX?  This does make me realize that I should add Plan 9
to the OS list.

>
>	Syntax highlighting: No.
>it's really 'no', but i don't miss it in C because of the double-clicking rules

Agreed.  Also, I've found regular expressions to convey the C constructs I care
about.

>	Srch select region: No.
>x/pattern/p

This one could be a yes.  It depends on what they mean.  This command selects
the last occurrence in the selected region, which may be fine.

>
>	List all occurances: Yes.
>occurrences.  tell me this is your typo.

Its not my typo. I cut & pasted it from the compendium.


oh yes, i missed the 'begin' :


>Goto begin next line: ?
+0+#0

Good, but it won't work if you are at the beginning of a line.

>Goto begin prev line: ?
-0-#0

Good, but it won't work if you are at the beginning of a line.


-- 
-------------------------------------------------------------------------------
Beirne Konarski                 | Reading maketh a full man, conference a
beirnek@summitis.com            | ready man, and writing an exact man.
"Untouched by Scandal"          |       -- Francis Bacon
-------------------------------------------------------------------------------



             reply	other threads:[~1995-03-27 20:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1995-03-27 20:40 hc05 [this message]
  -- strict thread matches above, loose matches on Subject: below --
1995-03-28  7:50 Steve_Kilbane
1995-03-27 21:02 rob
1995-03-27 17:01 Erik Quanstrom
1995-03-27 16:45 rob
1995-03-27 16:12 hc05

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=9503272013.AA21809@cheetah \
    --to=hc05@summitis.com \
    --cc=sam-fans@hawkwind.utcs.toronto.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).