From: Richard C Bilson <rcbilson@plg2.math.uwaterloo.ca>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] sam hacking - a couple of fixes that may apply t
Date: Thu, 3 Jul 2003 14:30:24 -0400 [thread overview]
Message-ID: <200307031830.OAA05117@plg2.math.uwaterloo.ca> (raw)
> From: steve.simon@snellwilcox.com
>
> If however, the history in the sam window is just text then one is
> quite within ones rights to 'change history', edit it, double click
> to the right of it (to select it) and hit send.
But by double-clicking to the right of the text you pick up the entire
line, plus terminating new-line, right? So you're not relying on the
add-a-newline behavior.
- Richard
[...who doesn't use sam all that often, but often uses win in the
manner that you describe]
next reply other threads:[~2003-07-03 18:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-03 18:30 Richard C Bilson [this message]
2003-07-04 1:47 ` boyd, rounin
2003-07-04 8:59 ` Douglas A. Gwyn
2003-07-04 10:08 ` boyd, rounin
2003-07-04 15:36 ` Derek Fawcus
2003-07-07 8:33 ` Douglas A. Gwyn
[not found] <2149465875@snellwilcox.com>
2003-07-03 17:06 ` steve.simon
2003-07-03 17:41 ` Derek Fawcus
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=200307031830.OAA05117@plg2.math.uwaterloo.ca \
--to=rcbilson@plg2.math.uwaterloo.ca \
--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).