>2. The LISTOPEN macro should have "D-Delete" and "W-Write" (and
>technically, "E-Edit") for "Brief emulation". I'd also like the LISTOPEN
>macro to center its window on the screen.
But, but, but...  What about speed-search?
I guess we could have a special Brief version of the ListOpenFiles.  I
assume you have already modified yours?
>3. I did this for TSE 2 and I'm doing it for TSE 2.5 :-) :
>
>    proc SmartDosShell()
>        string OurCurrentDrive[1]
>        string OurCurrentDir[80]
>
>        OurCurrentDir=CurrDir()
>        OurCurrentDrive=GetDrive()
>        Shell()
>        LogDrive(OurCurrentDrive)
>        ChDir(OurCurrentDir)
>    end
>
>    it's not really "smart" :-), but it does what I'd like it to do.
>Perhaps this can be included as an alternate shell..
When you say included, what do you mean?  Should we ship an additional
macro (like yours)?  Should we place it on the potpourri?  Or how about
an additional built-in command, Shell2() (what a creative name!) that
keeps the logged drive/directory?
>4. I can't get anything in regards to recent files, state, etc. to work.
>I've enabled all the options, but if I just enter E on the command-line,
>I get the "files to edit" input box, there is a TSEFILES.DAT in the TSE
>directory (where E.EXE is located), but that's about it [and yes, the
>.DAT file seems to be properly updated].
Are you using the 2.5 brief.ui, or a 2.0 based one?  If the latter, make
sure you have updated the WhenLoaded(), to include all the 'extras' in
the 2.5 brief.ui.
>5. The installation program uses double/single corner combo-characters,
>this doesn't look too cool under OS/2 with a non-437 code page selected.
>Either all double or all single works though - no big deal, but..
Thanks, I've made a note about it.
>6. I won't nag about the lack of real undo() since I'm sure you're
Sorry!  It is very hard on our list.  I assure you that once I figure
out the best way to do it, it'll be in there!
>7. I'd like TSE (and TSEjr/2) to support something like $[envvar] in any
>input field, any string, any .CFG setting, etc. to mean "replace with
>value of environment variable [envvar]". I often disconnect my machine
>from the LAN here, in which case I want my swap disk to be C:\TMP, when
>OS/2 is loaded, I want it to be H:\TMP, and when Novell is loaded, I
>want it to be X:\TMP. Now, I set TMP to this externally, so if I could
>tell TSE that my swap path is $[TMP], it'd "auto configure" itself
>depending on where I am. This obviously has other uses too.
See Louis's note to you.  Does that help some?
>8. I won't nag about the lack of TSE Pro/2 :-))
Hey, I want one probably more than you do!  Do you know where I can buy
some time?   I do not have much of it at the present!
>9. How about a "state" option that does something like "Activate local
>state saving if state file exist in current directory, otherwise
>[disable |  enable global]"? That way, I can force it to write a state
>file when I know I want one for a specific directory, but don't need it
>all the time.
Interesting idea.  For now, you could hook _ON_EXIT_CALLED_, and do the
following:
    if Query(SaveState)  _LOCAL_ and FileExists("tsestate.dat")
        Set(SaveState, _LOCAL_)
    endif
>10. BRIEF.UI again - Brief automatically unmarks the current block after
>it has been written to disk - TSE's BRIEF.UI doesn't.
Whoops!  Oh well, the truth is out.  I'm _not_ a Brief expert! 
Thanks for catching this, it should be an easy fix.
>11. I'm still a bit irritated about the fact that TSE cannot
>successfully process an "Access denied" error when attempting to open a
>file. If it gets Access Denied, I think it should try opening the file
>in READONLY/DENYNONE(/NOINHERIT). This has nothing to do with file
>locking, etc. it's simple common sense. I have applications running on
>other machines on the network and sometimes want to look at their logs,
>those files are opened in WRITEONLY/DENYWRITE/NOINHERIT, and TSE refuses
>to open them (TSEjr/2, however, does it).
Sorry about that.  I'll take a look into this.
>12. If a file is opened in R/O mode (see [11, above]), TSE should
>display somewhere on the status line (and pref. set an internal
>variable) that the file or "buffer" has been opened in R/O mode and
>refuse to save it.
Note that 2.5 will not save a read-only file in this version, but will halt
the save with an error message, "Cannot save read-only files" or some such.
As for the statusline flag, that could be implemented by a statusline hook.
But, I do agree that the statusline thing should probably be a standard
feature.
Sammy
--- FidoPCB v1.4 [ff151/a]
---------------