From: Andrew Higham <andrew@epcfta.edinburgh.ac.uk>
To: laden@math.tau.ac.il, sam-fans@hawkwind.utcs.toronto.edu
Subject: Re: samx2 patches
Date: Fri, 18 Mar 1994 08:51:18 -0500 [thread overview]
Message-ID: <4422.9403181351@epcfta.ed.ac.uk> (raw)
In-Reply-To: laden@il.ac.tau.math's message of Thu, 17 Mar 1994 19:25:33 -0500
> btw: a useful patch i have not seen is the removal of 'click-to-type'
> i am _very_ new to sam so i dont realy know if this would somehow break
> some functionality, but it seems like a simple fix which could save plenty
> of mouse clicks. anyone done this?
The following patch is a combination of a couple of patches discussed here
before.
Sam works fine without click-to-type. The only small problem is that it is
a bit too easy to change the focus of commands by moving the mouse pointer
through another file window on its way to the ~sam~ window. But I find the
default click-to-type has more problems for someone who uses a point-to-type
window manager.
Andrew
# to apply: patch -d newsam -p1 < thispatch
*** sam4.1/samterm/main.c Fri Mar 18 11:37:28 1994
--- newsam/samterm/main.c Fri Mar 18 12:25:02 1994
***************
*** 102,107 ****
--- 102,109 ----
scroll(which, 3, fwdbut == 3 ? 3 : 1);
else
menu3hit();
+ }else if(nwhich && nwhich!=which){
+ current(nwhich);
}
mouseunblock();
}
***************
*** 128,134 ****
flborder(which, 0);
if(nw){
flushtyping(1);
- flupfront(nw);
flborder(nw, 1);
buttons(Up);
t = (Text *)nw->user1;
--- 130,135 ----
*** sam4.1/samterm/menu.c Fri Mar 18 11:37:28 1994
--- newsam/samterm/menu.c Fri Mar 18 12:25:06 1994
***************
*** 178,183 ****
--- 178,184 ----
i = 0;
while(i!=t->front && t->l[i].textfn==0);
current(&t->l[i]);
+ flupfront(&t->l[i]);
}else if(!lock)
sweeptext(0, tag[m-NMENU3]);
break;
next reply other threads:[~1994-03-18 15:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-03-18 13:51 Andrew Higham [this message]
-- strict thread matches above, loose matches on Subject: below --
1994-03-18 0:25 laden
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=4422.9403181351@epcfta.ed.ac.uk \
--to=andrew@epcfta.edinburgh.ac.uk \
--cc=laden@math.tau.ac.il \
--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).