🚀 go-pugleaf

In article <JAN.92Aug12103429@pallas.neuroinformatik.ruhr-uni-bochum.de>, jan@pallas.neuroinformatik.ruhr-uni-bochum.de (Jan Vorbrueggen) writes:

|>    > On a similar note the TDS, like every new and elegant code managing tool;
|>    > once one is fluent with it's workings, has its own continually growing set
|>    > of advantages over traditional editors.
|> 
|>    I think I'll complain about this one too :)
|> 
|>    TDS is not a bad tool; it does have a reasonably good editor and file management
|>    system. My objection is why?. Who needs a new editor?; I mean just how many 
|>    ways can you do a cutandpaste operation!. Personally I like to keep the
|>    option of using any editor I wish (this may ore may not be origami) and I 
|>    like to have more direct control over the files on my disk. As soon as the 
|>    toolset came out, I gladly converted away from the TDS.
|> 
|> Actually, I think the control of disk files is what the TDS does best. When
|> 
|>  Jan Vorbrueggen
|>  jan@neuroinformatik.ruhrunibochum.de



Really??? Admittedly, I use OPS (Meikos' version of TDS) but the number of times that
I've lost files (yes, complete files) due to OPS being unable to update a file (eg due
to the underlying filestore being full) has been really really annoying!!!

And wouldn't it be great to be able to jump to exactly where you wanted in the 24th
nested fold (in one go)!


Now, who wants to inform me a bit more about this toolset....

Michael