sam-fans - fans of the sam editor
 help / color / mirror / Atom feed
From: byron@netapp.com (Byron Rakitzis)
To: john@civil.su.oz.au, sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: saved replacement texts?
Date: Mon, 23 Nov 1992 22:19:58 -0500	[thread overview]
Message-ID: <9211240319.AA07803@netapp.netapp.com> (raw)

>This suggestion, I am afraid, is just plain stupid, emacs or no.

Oh, come off your high-horse. Emacs has a command-line which is
separate from the current window. Obviously Scott was not talking
about replacing the command window with the new file.

>Pike did an excellent job designing the sam interface.

I agree. But I don't think he achieved perfection, nor do I think
that suggestions for improvement are inappropriate.

>The single click to place the usual edit window is just what you want.

I'm sorry, maybe it's what you want, but it's not what I want.

>Sometimes, you want to put the command window in the middle of the top-level
>window, and have edit windows above and below.

Yes, about 1% of the time. Does it make sense to have the user interface
revolve around this remote possibility?

>It's not broken and doesn't need any fixing.

Obviously a matter of opinion.

I would prefer either of two options:

1) automatic placement

2) non-placement, i.e., leaving the files in the menu with a minus-sign.
(this makes opening the file into a two-click operation, assuming that
sam points the "lasthit" of the menu at the newly opened file)

In both cases, it means that I don't have to automatically reach for
the mouse after typing B. (though I prefer solution #1)

For example, I often want to make a quick change to a file with commands
of the form

	B file
	cmd
	D

at *least* as often as I want to tile or otherwise futz with the sam
layers.


             reply	other threads:[~1992-11-24  3:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1992-11-24  3:19 Byron Rakitzis [this message]
1992-11-24  4:02 ` John Mackin
  -- strict thread matches above, loose matches on Subject: below --
1992-11-24  5:18 Byron Rakitzis
1992-11-24  3:05 Byron Rakitzis
1992-11-23 23:31 Arnold Robbins
1992-11-23 22:03 Byron Rakitzis
1992-11-24  0:16 ` Scott Schwartz
1992-11-24  2:02 ` noel
1992-11-24  2:11   ` Chris Siebenmann
1992-11-24  2:41     ` Jeremy Fitzhardinge
1992-11-24  2:46       ` Scott Schwartz
1992-11-24  2:41     ` Scott Schwartz
1992-11-24  2:47       ` John Mackin
1992-11-24  3:10         ` Scott Schwartz
1992-11-23 21:51 Arnold Robbins
1992-11-23 21:53 ` noel

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=9211240319.AA07803@netapp.netapp.com \
    --to=byron@netapp.com \
    --cc=john@civil.su.oz.au \
    --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).