I don't understand the first part of your question, but as to the second 
part I have a question of my own: How would BBEdit know that the last 
closing DIV (in your example) is incorrect? What if that last DIV is in 
fact correct, but you erroneously left a closing DIV elsewhere in the 
document? FWIW, I use code folding to find the incorrect tags in situations 
such as this. This works especially well if your closing DIVs have comments 
after them as to which opening DIV they are supposed to match.

On Saturday, August 22, 2020 at 4:50:33 AM UTC-7 [email protected] 
wrote:

> I have 2 questions. I have a very large Lua file. I duplicated it and 
> commented most of it out. Then I made some changes. I am trying to find the 
> changes between the 2 documents but the difference engine keeps gobbling up 
> more on one side than the other and then the comparison is useless because 
> it's no longer in sync. This seems to happen most when one side has lines 
> with just new lines and the other side has a comment "--". Is it possible 
> to tell BBEdit to pin text in both documents at certain places so that no 
> matter what the text is on either side, it will restart it's comparison at 
> that point? Or is there some other way to manipulate how it's comparing 
> things?
>
> Second, it would be so nice if a text editor showed when an html tag was 
> not correct, like
> <div><div></div></div></div>. If the last one was highlighted in red or 
> something it would be great. Is this possible now?
>

-- 
This is the BBEdit Talk public discussion group. If you have a feature request 
or need technical support, please email "[email protected]" rather than 
posting here. Follow @bbedit on Twitter: <https://twitter.com/bbedit>
--- 
You received this message because you are subscribed to the Google Groups 
"BBEdit Talk" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/bbedit/f1a105d2-dc8b-4ca3-b272-c88c254cd9f1n%40googlegroups.com.

Reply via email to