Mail Archives: djgpp/1998/08/03/17:31:14
Brett Porter <blp01 AT uow DOT edu DOT au> wrote:
> I'm sending this to the DJGPP list so that SET can see it and also so that
> other users of SET Edit can comment on the suggestions within.
>
> I've recently stopped using RHIDE and started using RHGDB and SETEdit
> because I am finding makefiles more flexible for the large projects I am
> working on. Having extensively used SETEdit for the first time, I have a
> series of suggestions to make. My apologies if they already exist and I'm
> to blind to find them.
>
> 1. Include a goto line feature, like in RHIDE.
Goto line is Ctrl+J like in RHIDE (because the things are the reverse: the
editor imposses Ctrl+J ;-) You can add an entrie in the menu for it.
> Sometimes I run make from a
> DOS shell and get errors, but can't go straight to the source line
> involved. Also, programs like bison have a different way of returning
> errors and SETEDIT can't find the line automatically.
bison violates the GNU standards! too bad.
> 2. Allow GREP to be assigned to a key (eg SHIFT-F2 like in RHIDE). It is
> very powerful in SETEDIT, so I use it frequently.
I'll see if I make it default, but in SET Edit you can modify all the menu so
you can add short cuts. Just take a look to the menubind.smn file.
> 3. Poll the mouse in the screen saver, not only require a keypress to end it.
That's complex in TVision but I'll put it in the todo.
> 4. ***BUG*** I windowed SETEDIT in Windows95, and it switched to the screen
> saver (Plasma), which stayed in the window. I then pressed a key to end it,
> and the dreaded blue screen appeared: a fault in the VMM VxD. As far as I
> know this is the Virtual Memory MAnager, which can't be a good thing to
> crash, although Windows seemed to recover alright for once, just killing
> SETEDIT. If no one else can replicate this: don't worry about it. It is
> probably just my horrible crash-prone 486.
Is not a bug in the editor the bug is in your Windows' video driver. Some
drivers doesn't even support graphic modes in windows. The Asus 3D Explore
handles it *amazingly* the plasma is displayed at a good frame rate and you
get the correct text mode after exiting.
> 5. ***BUG*** Auto-indent mode is on, but if you create a new file and press
> <TAB>k<ENTER> it doesn't indent on the first line. Anything does this, not
> just k.
Ok, I'll check it.
> 6. ***BUG*** Sometimes pressing <HOME> after the editor auto-indents and
> then typing has the cursor at the start of the line, but the letters
> appearing one tab space in. IT happens quite a bit, but as usual when I try
> to replicate it it doesn't work.
I never experimented it, please try to find some reproductable mechanism.
> Hope this is all useful to users of SETEDIT.
Yes is useful.
Greetings, SET
------------------------------------ 0 --------------------------------
Visit my home page: http://set-soft.home.ml.org/
or
http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
ICQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013
- Raw text -