> I guess we could have a special Brief version of the
 > ListOpenFiles.  I assume you have already modified yours?
Yes - it wasn't all that much to modify.
 >>3. I did this for TSE 2 and I'm doing it for TSE 2.5 :-) :
 >>    proc SmartDosShell()
[..]
 > 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?
Shell2() would be fine..
 >>4. I can't get anything in regards to recent files, state, etc. to work.
 > Are you using the 2.5 brief.ui, or a 2.0 based one?
Got it working now.
 >>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!
Yeah - I'm just so anxious about getting rid of Brief once and for all, 
that's the main reason I keep reminding you of this. I understand perfectly 
well that a real undo/redo is not the easiest thing in the world to write, so 
I'll be (somewhat :-) patient.
 > See Louis's note to you.  Does that help some?
Indeed it does.
 >>8. I won't nag about the lack of TSE Pro/2 :-))
 > Hey, I want one probably more than you do!
Not possible :-)
 > Do you know where I can buy some time?   I do not have much
 > of it at the present!
Well, you're asking the wrong person :-)
But, should you find a reasonably priced time source, please let me know :-)
 > 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
Ah, thanks.
 >>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!
 > 
:-)
 >>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.
 > Sorry about that.  I'll take a look into this.
Excellent.
 > 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.
OK. But the file in this case isn't really read-only, but the buffer should 
be marked as such (and it'd be nice if that could be queried somehow).
 > As for the statusline flag, that could be implemented by a
 > statusline hook.
Yes.
 > But, I do agree that the statusline thing should probably be a
 > standard feature.
Great.
                %JoHo%
                joho@abs.lu
---
---------------