text: fix spurious regex anchor matches

The regex anchors ^ and $ must not match at the start/end of the search
range unless it is preceded/succeeded by a new line.

This is implemented at the text-motion layer by passing the appropriate
REG_NOT{B,E}OL flags to the search backend, meaning the caller can
influence the anchor behavior depending on the context. This is important
as for example in the command language the anchors apply to existing
selections, not line boundaries.

0 files changed, 0 insertions, 0 deletions