displaying or excluding all lines that match a regexp/search string would be good. Then being able to refine the currently displayed selection of lines with additional searches.
CJ,
Greetings from the Canada's other coast. It would be nice. The cost of Komodo is $295.00 for 2.3 Professional Edition,hopefully if Helios decides to implement the feature it will not increase the price that dramatically.
diek
This feature is found in a few text editors, especially HTML editors such as Macromedia HomeSite.
I agree! I was just going to post a new thread on this subject. It would be a GREAT addition to this fine product and would certainly help me work more productively!
Firstly, this fits quite nicely alongside the "highligh matching bracket" functionality that's being asked for: if you're already maintaining a stack of "brackets" (be it {} pairs, or <tag> </tag>) internally, you can automagically generate folding points from these.
However, I'd also like the ability to fold at arbitrary points - it's the one thing I'd need to ditch Word as an outliner. Oh, and I'd like my fold points to be namable and persistent. Off the top of my head, this could be implemented transparently using a second stream in the .txt file (though this would require NTFS).
As far as I'm concerned, an outlining mode is the only thing still missing from Textpad.
However, as JonK said, it would be important that it also supports folding at arbitrary points.
It should have Collapse/Expand Current/All nodes - and keyboard navigation would be important to work effectively. And drag + drop should move everything in a folded branch.
And if you do it, Helios - please ensure that folding status is stored with the file...
please ensure that folding status is stored with the file...
Absolutely NOT!
Textpad is a text editor, not a word processor...
In the textfile NOTHING must be stored besides the text.
If folding status were stored within the text file, it would ruin the text files.
What should a browser do with folding information within a html file?
Or a perl interpreter with folding information within a perl file?
...
Folding status should be stored in the workspace, NOT in the text file.
In the textfile NOTHING must be stored besides the text. [...] Folding status should be stored in the workspace, NOT in the text file.
OK, for the sake of, err, ASCII purity - you're right.
And the workspace will do. As long as it is stored *somewhere*.
I was simply getting carried away ... Thinking of large, complex documents, e.g. in DocBook, where it would be much easier if you could jump exactly to the section where you left off.
Maybe we could point the Helios team to a few top-notch Outliners, just to give them some inspiration? E.g. I used to work with Action Outline, which has a simple and effective GUI. I just didn't want another format to store my files.
MudGuard wrote:Textpad is a text editor, not a word processor... In the textfile NOTHING must be stored besides the text.
If folding status were stored within the text file, it would ruin the text files. What should a browser do with folding information within a html file? Or a perl interpreter with folding information within a perl file?
Folding status should be stored in the workspace, NOT in the text file.
See my previous comment about using an additional stream - thereby being completely transparent to your browser/Perl interpreter/Notepad.exe/whatever. Read up on Structured Storage (http://msdn.microsoft.com/library/en-us ... frame=true) on the MSDN if you're interested in how this works: if you're not interested in the hows and whys then trust me, it does work transparently.
JonK wrote:See my previous comment about using an additional stream - thereby being completely transparent to your browser/Perl interpreter/Notepad.exe/whatever. Read up on Structured Storage (http://msdn.microsoft.com/library/en-us ... frame=true) on the MSDN if you're interested in how this works: if you're not interested in the hows and whys then trust me, it does work transparently.
Sure, as long as you're using NTFS (as you noted earlier). While this may not be a problem for some, much of my work is stored on NFS and SaMBa shares, so it's useless. The workspace files make much more sense.
Never mind that hidden data as described smacks of more MS Big Brother techniques. MS would rather hide things from you than have them readily accessible (file streams, the registry, Palladium...). Thanks, but no thanks.
SanctimoniousApe wrote:... hidden data ... MS Big Brother techniques... rather hide things from you than have them readily accessible ... Palladium...
Tin-foil hat? Mine's the one over there ----> thanks
(really, is RegEdit any more difficult to use than vi and the mess that is /etc. And as for these so-called "hidden" streams - tried "type myFile.txt:1"?)
Problem with workspaces is that you've then tied your text file to both a second file and, by extension, you've baked in a path - which sucks even harder if you want to share the file. Way I see it, if you artificially hobble yourself, then don't complain that you can't get the benefit of advanced features. If you like *nixen then use vi. Making folding require NTFS is like making transparent dialogs require W2K or better.
