Hi Horst! Thanks for participating.
Horst.Epp wrote: ↑
2019-01-14, 09:27 UTC
MarkFilipak wrote: ↑
2019-01-13, 21:08 UTC
As a topic for general discussion... (I think poking brains is fun)
In the world of GUI, why are we still dragging around '\n' & '\t'? Why can't we simply feed text -- any text -- into a text-box and click "Find"? By "any text" I include new-lines and tabs and control chars and... anything. The current search input methods are CLI relics that can be abandoned.
So, what would submit the search string? Not '\n' -- that's so 'CLI'. What would submit the search string would be [ Find ].
I don't agree with this general assumption.
That has nothing to do with CLI or any other environment conditions. ...
Oh? Doesn't it? Well, let me ask: Why does '\n' even exist? I think it's because '\n' is the only way to include end-of-line in a search string. And that's only because, for a command line, an actual end-of-line ('Enter' key) terminates the command line! But what if we stop insisting that CLI commands consist solely of printable characters? What if we include non-printable characters?
What about this: Type in the first 'line' of target text but for end-of-line, press Ctrl+Enter; then continue typing in the next 'line' of target text, etc. When all the 'lines' of target text have been entered, then press Enter (without Ctrl) to terminate the command line. IMHO, that's the way Perl RegEx should have been from the git-go.
Next conceptual step: Type in the first 'line' of target text including Enter; then continue typing in the next 'line' of target text, etc. -- just as you would enter text into a text editor. When all the 'lines' of target text have been entered, then press the [Find] button to submit the search command.
'\n' to insert end-of-line into a search string is a relic of a bygone era.
Hi Christian! Delighted customer since 1999. License #37627