Conference hydra::amiga_v1

Well, not too much has happened with SEDT. I have the V4.0 sources, and did
make a pass at making it work on the Amiga. Unfortunatly, after getting all
my code in there, I lost my hard disk (with no backup of course) so had to
start over again. However, the real problem with SEDT v4.0, is that the
entire mechanism for reading keyboard input was changed. The way in which
it works now is very tightly coupled to the PC, and does not lend itself
well at all to how things work on the Amiga. The code for reading a character
from the keyboard was very well isolated in pre-v4 code. Now its spread around,
and makes the assumption that each and every scan code has one and only one
character associated with it. This is true most of the time, but when your
doing a key sequence on the Amiga is not true. If I want to properly support
all keymaps (and special key sequences) on the Amiga, I would have to make
major changes to SEDT. I have made a number of attempts at trying to fake
out all the higher level routines with little luck. I haven't really had
the amount of time needed to work out the issues with Anker and try to make
v4 work on the Amiga. That's not to say that I won't try and get v4 up at
some point, but I'm just not sure when.

What are the primary features of v4 that are lacking in v3. Is v3 sufficient
for most peoples needs?

How many folks out there are actually using Amiga SEDT these days? Is it
worth my effort to port V4?

Frank
Amiga SEDT port dude.

    I use SEDT almost exclusively. I don't really care what versionyou use
    as a starting point, but I would really like some more support for
    using the mouse. 
    

    I got bit by SEDT writing a partial file on me (and also too many
    GURUs) and went back to using MEMACS instead.  
    
    I use SEDT as my editor on VMS and MS-DOS, so I'm very interested in 
    seeing SEDT enhanced to keep up with its other cousins.
    
    I also know Anker from back in the days when we traded keyboard
    handlers back and forth between the MS-DOS terminal emulator, SETHOST,
    and SEDT, so I'll work on him to make sure he's more aware of this 
    portability issue.
    
    Just out of curiousity, could you give an example of a scan code 
    that has multiple characters associated with it?  
    I'm very familiar with the nightmare of PC keyboards, but have never 
    really looked closely at how the Amiga handles keyboard input.
    
    thanks,
    dennis

    I love having SEDT in the Amiga.   

    I've not had a GURU with the current version that I am running (FT5)
    since I bumped up my stack to 10K.  I do notice that the FT5 version
    that I use seems to take 5 to 6 seconds to load from my pretty fast
    Conner HD.   I seem to recall that several versions we released with
    varying amounts of debug code enabled an or inserted.  Would an earlier
    version load faster and use less memory?  What is the latest version
    with the least or perhaps no  'debug' code in it?  Could you give us a
    net pointer?

    I'm not sure what the new features are with V4.  Is it worth it?
    Can you enlighten us? 

    Keep up the great work. It's _greatly_ appreciated.

    Thanks
    		-Bruce

    Ditto. I use SEDT on the office VAX, on the laptop PC, and on my Amiga.
    And, the V3.2 I have for the Amiga has never gurued. I do wish I could
    have it come up in an interlaced screen though!
    

    I use SEDT FT5 exclusively on my Amiga.  I have had no problems(except
    for operator error) with it.
    
    mark
    

    
    	SEDT is the only word-processing software I use on the
    	AMIGA and RAINBOW.  Haven't had any problems with either.
    
    	Thanks for the good work.
    
    		-Terry

    another vote of thanks for it.
    
    It's very stable for me too, not sure what I did way back when to get
    that - I suspect it was to use a large stack.
    
    I'm not familiar with what's new with SEDT v4.0, I'm still trying to 
    figure out a number of the features in 3.0 :-)
    
    Has anybody figured out a way to get it to run on a custom screen?  I
    normally run a 640x400 workbench, but I would like SEDT to come up
    on it's own 640x200 screen.
    
    Dave

    
    	Despite having a couple of other word processors (used mostly by
    the wife and kids) I use SEDT exclusively also.  I liked it so much I
    pasted together an interface to the ARP file requestor (see note 4354) 
    and call it right from the title bar using MyMenu.
    
    							mt
    

       I'll add my vote of thanks as well for the AMIGA version of SEDT.
       
       My main concern - given that I use SEDT on the VAX, my VAXmate at
       work, my AMIGA and my T1000 laptop - is the ability to keep them
       in all in synch.  
       
       As new commands -- supported only under the latest versions of
       SEDT -- are added by Anker, and used either by themselves or
       inconjunction with others to perform a function (either by Anker
       for the EDT style, or Dick Danek for the WPS style) the AMIGA
       version will get out of wack.
       
       That's the bad news.  The good news is that so far this has not
       proven to be of major significance. 
       
       Art
       
       
       
       
       

    re: interlace.
    
    Edit the SEDT.CNF file to include SCREEN=INTERLACED. 
    
    RE: speed
    
    I set up a script to copy SEDT and all of it's associated files to RAM:
    then change some assignments to make SEDT_DIR references point to RAM:. 
    If I'm going into a heavy editing session, like when I'm trying to
    write C code, execute the script, and everything happens....FAST.
    
    I'd very much like some mouse support???
    
    Cheers,
    Glenn

	I've been running (FT5 i think) w/ a custom screen. I like SEDT vy
much as I use LSE's EDT keypad at work.

	Is there NO mouse support at all? (If there is how do I turn it on?)
I vy much would like the following mouse support (In priority order):

	1. cursor  positioning, (miss this most).
	2. text selection (starting char thru ending char)
	3. rectangular text selection (corner character to corner char.)
	4.a text Clip or copy and paste (to/from Amiga Clipboard), or a menu
		item to get txt to/from the clipboard.
	4.b text cut/paste (to SEDT cut/paste buffer ).
	4.c text copy (to SEDT cut/paste buffer ).

Cursor Positioning comments - It would be nice if it took something like
a quick double click to move the current postion curser, and something like
a click and hold to select a region - suggest copying the SNAP mouse
semantics for selection and cut/past.

	BTW, I currently use SNAP which is why selection/cut-past are
relatively low on my list- I have them sort of: With SNAP
run into what looks like some form of SEDT input buffer limitation.
When I select over about 16-24  characters (haven't counted, but it's
about 1/3 of a line). The inserted text is truncated to the first ~16-24
chars. are inserted into SEDT. I can include the full SNAPed SEDT screen
txt into other windows, which is why I think it's the SEDT input buffer.
- This may have something to do with the amount of txt that is accepted
before a journal entry is made. Anyway, this is a real pain when I'm
editing code and just want to grab a copy of a previous line or 2.

Other stuff:
	In amiga key maps, include ALL amiga key combinations w/unused
ones commented out. It took me a LONG time to figure out how to designate
the ^Z key to match the DEC EDT ^Z. It would be nice if there were
a DEC keymap file that has the most often used std DEC EDT (or LSE) and cmd
line editing keys (such as ^Z for EXIT, ^A toggles insert/overstrike mode,
^L is form feed, etc.) Also, a color preferences for the custom screen
mode would be a nice touch.

	A way to make the ruler disappear so can get extra txt lines
displayed. (I seldom change the ruler).

Regards, Verell Boaen

    re:.13
    
    how did you get it to run on a custom screen?  Is it some command in
    SEDT.CNF?
    
    Thanks,
     Dave

Thanks everyone for the positive votes for Amiga SEDT. I really appreciate it.
As soon as I can find some time I will certainly try to address some of the
issues brought up in the last replies.

To answer a few of the questions:

.4

Dennis, the problem with the keyboard handler in v4 of SEDT is that it expects
that every keystroke can immediately be translated to one and only one
character. Perhaps this is true on other platforms, but is not so on the
Amiga. A case in point is when you enter Alt-K and some other key and
get an alternate translation. On the Amiga you can take a scan code and
call a system routine (RawKeyConvert) to return you the translation of the
key via the current key map. Now certain keys like the funtion keys, and
keypad keys will return you an escape sequence if you call RawKeyConvert
with their scan code. For something like Alt-K, you will receive nothing
when you pass in the Alt code and the K code, but will when you pass it the
next code. At that point it will either determine that you just entered a
valid Alt-K sequence and return the alternate translation, or toss out the
Alt and return a K. So, the translation is actually delayed till it has
enough information to do the proper translation. The SEDT v4 input parser
has been conpletely rewritten from V3, and does not give you any reasonable
way of handling this sort of behaviour. It basically wants to get a scan code,
check its table of scan code translations (in the keyboard file) and if
not found there, get the ONE character translation for this key! In v3 it
was up to the input handler to handle the whole translation mess. SEDT
would call it expecting to get back either a character, or an internal
function code indicating a function key etc had been typed. This worked
fine for me, cause I would just get a scan code, translate it into a seperate
buffer and return one character at a time from the buffer to SEDT. If the
scan code translation did not return a character(s), then I would loop for
another scan code. If it returned a series of characters, I would return
one at a time to SEDT. Very simple.

.9

Dave, you can have SEDT open a custom or interlaced screen by default. Add
one of the following lines in SEDT.CNF.

SCREEN=CUSTOM		; 24 line custom screen
SCREEN=INTERLACED	; 48 line custom screen
SCREEN=WORKBENCH	; 23 line workbench window

The custom screens will use the first four workbench colors.

all

Mouse support does seem to be high on everyones list, so I'll look into
doing this. Do I have more votes for adding mouse support to V3, or
getting V4 up and running?

The lastest version of SEDT is still FT5A, and it can be found at

CANIS::DUA1:[AMIGA.SEDT]

There you will find the readme file, an archive with the SEDT documentation,
and an archive with the binaries.

Thanks for the feedback,
Frank

    I knew I should have RTFMed :-), just haven't had the time lately. 
    Many thanks for info.
    
    As to mouse vs. v4.0, are there any great, new features in 4.0 that we 
    should be drooling over getting on the amiga?  If not, I vote for mouse
    support and other Amigaizing enhancements.  I'm basically using it as
    an EDT clone, so I haven't be using a lot of the strange commands.
    
    Dave

    i use SEDT V3.3 247-FT5A since Apr/May-1989 and had NEVER any problem
    with it. I use the EDT-like keymap and my only wish is that the Keypad
    8 (scroll down/back) will work like the same function in EDT. the one
    in SEDT scrolls to the next paragraph i would like to scroll only 8 -
    12 lines. 
    
    
    Many thanks for the EXCELLENT work Frank,
    
    Ralf
    ====

->     I use the EDT-like keymap and my only wish is that the Keypad
->     8 (scroll down/back) will work like the same function in EDT. the one
->     in SEDT scrolls to the next paragraph i would like to scroll only 8 -
->     12 lines. 
    

I too am a constant user of SEDT. Could'nt live without it. 
Re: .-1 heres a mod for your A2KEY.EDT file to have the KP8 Key and KP7
key behave as it does under EDT.


F038(:UOFF@PAG:CT:UON).                                       
;Keypad 7:      ** Goto next FF (^L) (also put cursor at top) 
F039@SCR.                                                     
;Keypad 8:      ** Goto next Screen like EDT (was next paragraph)

Steve.

    Thank You Steve
    
    Ralf
    ====

re: .18

Steve,

I have a somewhat different problem.  I LIKE the SEDT style keys for KP7 and KP8
but have difficulty when logged in from home using SEDT on the VAX displaying
on the Amiga.  At home or at work KP8 is next paragraph BUT connected thru
VLTjr to work and KP8 is now next screen.  What gives?  Any idea how to fix this
one?  I been bit bigtime when working from home on something and I lose my 
connection.  The next day at work I forget and try a recovery with the journal
file which is fatal!  


...Ed

  Ed,

  Probably what is happening is that when you use VLTjr from home it responds
  as a VT100 id, and thus SEDT uses the SEDT$VT1XXKEYS (logical name) keys
  vs the SEDT$VT2XXKEYS when logged in from work. Just locate the files
  and make them the same. You could just point the SEDT$VT1XXKEYS logical to
  the same file as SEDT$VT2XXKEYS logical.

  Steve.
 
  Now, if we could only get MIS to put SEDT (back) on our production systems,
  	(grumble grumble)

    Yes!!!
    
    Thanks Steve.  You just solved a long standing problem I've had with
    SEDT.  I should have figger'd that one out.
    
    Thanks again,
    
    ...Ed

    Speaking of SEDT --
    
    Is there anyway to define PF1/7 so that an "exit" or "quit"� command
    will work? I get tired of reaching for the mouse just because I want
    to leave the program.
    
    
    Thanks
    
    Keith
    

->     Is there anyway to define PF1/7 so that an "exit" or "quit"� command
->     will work? I get tired of reaching for the mouse just because I want
->     to leave the program.

 No need to use mouse, GOLD-Q for "quit" or GOLD-F "exit" (save and exit).
 (Gold being PF1)

 Steve.

    Better yet F8 "Quit" or F10 "Save file and Exit". 8^)

    
    Can someone tell me where FT5 SEDT is located?
    
    Thanks,
    ~Ray
    

Ray, SEDT FT5A can be found at:

CANIS::DUA1:[AMIGA.SEDT]SEDTFT5A.LZH		Sedt distribution
CANIS::DUA1:[AMIGA.SEDT]SEDTDOC.LZH		Sedt documentation
CANIS::DUA1:[AMIGA.SEDT]READMEFT5A.		Installation notes etc.


I created LHARC archives for SEDT in addition to the ARC files there since
they are much smaller, and no one really uses ARC anymore! The ARC files
are still there case there is a problem with the LHARC files.

Frank (AMIGA SEDT dude)

I've suspected for a while that SEDT does something incorrectly with
memory. I've experienced random guru's with extensive use, even with stacks
>25000. I happen to be running enforcer and got a hit with it.


Here's an enforcer output:


PC (approximate) = 78F254A		Fault address = 1
User Stack Ptr = 793AC58		DOS process address = 78D77E0
Data: 0792A260 000000FF 00000001 0000000D 00000010 00000000 00000000 000000E9
ADDR: 0792A260 00000001 07922638 0793AC9C 07929768 0793AC6C 078007F0 078021F8
STCK: 078007F0 00000100 F8208000 078007BA 0792A260 0793ACAC 078F24AA 07929BEE
STATUS REGISTER = $18       SPECIAL STATUS WORD = $749 (READ-LONG)
PROCESS/CLI = BACKGROUND CLI, "SEDT"
HUNK-O-MATIC SAYS: PC ADDRESS IS IN HUNK #4, NEAR OFFSET $872


Any chance this will get fixed?