Failing to understand the oddities of the "line" chunk

[Bob Sneidar]

If I may be so bold, remember the discussion about the filter command returning different results depending on whether or not the chunk ended in a CR or not? Some argued that that was how it ought to behave. Are we now saying that consistency is the order of the day? So let it be written! So let it be done! But let's go with consistency in ALL things. 

Bob


On Mar 20, 2012, at 6:40 AM, Peter M. Brigham, MD wrote:

> Right, but if you have an insertion point in a field (no text selected), then "the selectedChunk" will contain something like
>   char 13 to 12 of field 2
> This is designed so that the selectedChunk is always in the form
>   char <startchar> to <endchar> of fld <fldNbr>
> That's just the way it works. After dealing with chunks for a while it does make sense, and it's consistent.
> 
> Jacque's point still holds, though -- the implementation of this form using lines instead of chars is *not* consistent.