On Mar 12, 2017, at 15:39, Rob Lewis > wrote:
> It would also be useful to have an inverse operation to process lines that do
> not contain the search string.
Hey Rob,
If you know enough about regular expression then it's doable:
On Mar 12, 2017, at 4:39 PM, Rob Lewis wrote:
>
> The "Process lines containing..." command is very useful. It would also be
> useful to have an inverse operation to process lines that do not contain the
> search string.
How about select "Delete matched lines"?
Make a
On Mar 12, 2017, at 4:39 PM, Rob Lewis wrote:
>
> The "Process lines containing..." command is very useful. It would also be
> useful to have an inverse operation to process lines that do not contain the
> search string.
>
> I know that grep's -v option does this, but it
The "Process lines containing..." command is very useful. It would also be
useful to have an inverse operation to process lines that do not contain
the search string.
I know that grep's -v option does this, but it doesn't seem to work here.
--
This is the BBEdit Talk public discussion
Could you please give us back the on set auto clipping.
I just can't imagine seeing million of clipping spread all over the
clipping window.
You could add a tab panel to the clipping window; one with the too much all
clipping; and another one filled with only the active set ( of language )
tx