Re: .setedit dir in home

[salvador <sal...@in...>]

ma...@pl... wrote:

> Right now the editor dumps all it's files (keybind.dat, the
> main tcedit.dst and the er* files) in the homedirectory of the user
> (linux).

True and the ammount of files is starting to be quite annoying.
That's why last night I modified it. But I forgot er* files, I'm putting it
in my schedule.
Also note that er* files are very important, and now the Linux ones are as
important as the DOS ones.
Now the editor not only tries to dump unsaved text to these files but also
the stack trace. I also created a small Linux application equivalent to
djgpp's symify to convert the addresses dumped there into source+line. And
what is even better: now the Linux version of the editor can be configured
to use gdb to dump the full calling stack (including values of the arguments
and local variables) to these er* files. Is also possible to automagically
call gdb and pass the control to gdb. The last two options must be enabled
by the user and the installed editor must install a binary with debug info
and have nm and gdb tools installed but that's really powerful because you
can go directly to gdb if the editor generates a SIGSEGV or gets a
SIGINT from a kill. What's even more funny is that: if the editor is under X
a separated xterm is launched to run the gdb there ;-), is really funny to
see the second window popping with gdb showing the stack frame and offering
a propmpt to analize why the editor died.

> Would it be very hard to out them in a .setedit directory
> instead?

Is done. I hope I'll put in in the CVS in less than a week.

> This would also fix another annoying feature:
> When you use the editor for the first time in a new directory
> it copies the tcedit file from your home directory, including
> any files that may be open there.

True, now the default tcedit.dst is first loaded from ~/.setedit/tcedit.dst
avoiding loading the one in ~/tcedit.dst which usually contains some opened
windows.

> This is hardly ever what you want,
> so it would be more logical to put the defaults in a ~HOME/.setedit
>  directiry (IMHO ofcourse)

Yes, and that's how is supposed to work now. Of course it will need a lot of
beta testing.
Additionally I added a new detail. As you could have files like deflopts.txt
as hidden files in your home (~/.dflopts.txt) from old versions a surprising
behavior will be exposed: the editor will load this file (which is
intentionally plain text) and if you modify it the file will be stored in
~/.setedit/deflopts.txt. So if you load manually the old file you'll get
surprised, the modifications aren't there, but they are working. So now when
the editor loads a configuration file from a directory and stores the
modified in another place a dialog informs the user where the file was
stored.

SET

--
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Visit my home page: http://welcome.to/SetSoft or
http://www.geocities.com/SiliconValley/Vista/6552/
Alternative e-mail: set...@bi... se...@co...
                    se...@ie...
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA Phone: +(5411) 4759 0013