arxt@sphinx.uchicago.edu (patrick palmer) (04/25/88)
Has anyone bound (or rebound) the keys of the numeric pad of the
B2000 so that they correspond exactly to the standard ones of a VT100
for edt editing. I have been using Dave Wecker's v100 v2.6. I would be
very grateful to anyone who would email me info and/or a script file.
Pat Palmer email: arxt@sphinx.uchicago.edu on bitnet
7.20::oddjob::ppalmer on span
(UUCP somehow; clever people can probably figure out
from my originating address - although I
never have been able to.) rss@ece-csc.UUCP (Ralph Scherp) (04/26/88)
In article <4081@sphinx.uchicago.edu> arxt@sphinx.uchicago.edu (patrick palmer) writes:
Has anyone bound (or rebound) the keys of the numeric pad of the
B2000 so that they correspond exactly to the standard ones of a VT100
for edt editing...
HEAR! HEAR! I second this notion. Actually, there's a couple of features
I'd like to see added to VT100:
* On 500/2000 keyboards, let the "(" ")" "/" and "*" keys act as PF1 - PF4
and "+" key be keypad ","
Leave Amiga's F1 - F10 be undefined by default.
I'd like to set up F1-F10, HELP keys to act like equivalent keys on a
VT200 keyboard.
* Add Front/Back gadgets for the VT100 screen, when using CUSTOMSCREEN
option, as well as allowing screen pull-down. (Didn't earlier versions
of VT100 have screen pull-down?) --- Unfortunately, the LEFT-AMIGA-"N"
and LEFT-AMIGA-"N" trick moves the workbench screen to front or back;
rather than just cycling all screens; so if you get your VT100 screen
sandwiched between other screens (which also lack front-back gadgets,
like the Emacs I'm using) you can end up with inaccessible screens.
* Allow multiple "ON string" traps to be active at once. I'd like to
be able to write dialing scripts which can handle various responses
like "CONNECT", "CONNECT 1200", "BUSY", and "NO ANSWER" in
intelligent ways. Perhaps a startup parameter in the init-script
could inform VT100 how many "ON" strings to allow at once.
The command `ON "string"' [with no following command] could be used
to remove a particular trap; `ON' all by itself, to remove all traps.
* Fix string requester gadgets not to add bogus characters in the
strings (for instance, when I select "CD" & type in a directory,
I frequently get error-messages to the effect of "no such directory"
which is not due to the directory being absent, but rather due
to the directory name it tries to CD to not being the same as
that which was displayed in the requester. I don't know what the
exact cause of this problem is, but I've certainly been annoyed with
it!
* Allow 132 column mode, or as close to it as we can get while still
maintaining readability. I suggest that if 132 columns can't be
displayed reasonably, that the visible portion of the Amiga's screen
should be a "window" looking at a portion of the VT100 screen; i.e.
the screen should still have a virtual 132 columns. Hence, for example
if I'm in 132 column mode & auto-wrap is enabled, and the amiga
representation only shows 120 columns; a line wrap should not occur
when I put a character in column 120; instead any characters going in
columns 121-131 would just not show up on the screen, but I'd see the
cursor re-appear on the next line as soon as we wrote in column 132.
A useful option here would be to shift the window left/right so as
to see this clipped text.
Now, I'm running the version of VT100 labeled "V2.7 ACS 870825" so if there
is a later version out there which addresses any of these issues, please
just send me a pointer to 'em & not any flames -- I've got the latest
version I'm aware of.
BTW, I'd like to express my thanks to the developers of "VT100" and say
that it's a job well done. Please don't misconstrue any of my above
comments as criticism. I'm just throwing in my two bits worth for
suggestions for the next release (assuming there is one!)
Thanks
-Mark Lanzo-
(I'm borrowing a friend's acct here--please
don't address replies to "Ralph Scherp")