On Wed, Mar 4, 2020 at 5:36 PM ‘Chad Baker’ via BBEdit Talk
wrote:
> The file opens fine without the ¿ gremlins in BBEdit without any intervention
> on my part. And I
> can search it fine in BBEdit. What Console does differently , that I like, is
> that when I search
> it will filter the file
Thanks, I'll give those a try.
-Chad
On Wednesday, March 4, 2020 at 2:45:43 PM UTC-8, Steve wrote:
>
> A few hints:
>
> 1. You can open using the UTF-16 encoding and then use the little drop
> down in the file's footer to change the encoding and resave it.
> 2. You can use the Find dialog
A few hints:
1. You can open using the UTF-16 encoding and then use the little drop
down in the file's footer to change the encoding and resave it.
2. You can use the Find dialog (cmd-f, use the "Find All" button) to
bring up a results browser on "error" and then you can just jump from
one to the
The file opens fine without the ¿ gremlins in BBEdit without any
intervention on my part. And I can search it fine in BBEdit. What Console
does differently , that I like, is that when I search it will filter the
file so that it only shows log lines that have a matching word, and hides
the
On 3/4/20 at 5:04 PM, bbedit@googlegroups.com ('Chad Baker' via
BBEdit Talk) wrote:
I work in tech support and I have to search log files for
things like "error". When I get log files from Windows
computers, the Mac Console won't find any matches. I search for
"Error" and it says 0 results
I work in tech support and I have to search log files for things like
"error". When I get log files from Windows computers, the Mac Console won't
find any matches. I search for "Error" and it says 0 results because it
sees E¿r¿r¿o¿r not Error. If I zap the gremlins, then it will match all
