asger added,
> The real solution for 1.1.x is to have cut and paste work more intelligently.
> When you select something, part of the selection is two flags that denote
> whether the start of the selection is the beginning of a word, and similar
> for the end of the selection.
It may be useful f
> If we are to use such a complicated solution, then the real fix is to
> make cut/copy behave normally and avoid this space collapsing stuff.
>
> And this means too much work for 1.0.x.
The real solution for 1.1.x is to have cut and paste work more intelligently.
When you select something, part
> "Richard" == Richard E Hawkins <[EMAIL PROTECTED]> writes:
Richard> But it's spaces its watching for, so using a space as part of
Richard> the replace string can confuse it. The more I think about it
Richard> (and, damnit, i'm not supposed to be dedicating brain cells
Richard> to this at t
oops, sent it to quick. I wanted to add that using an inset the way I
used the strign might be practical for 1.0.x; the inset doesn't have to
do anything but stay there while the cut/paste happens, and then be
removed--it's just that putting *something* in front of the first
character of the
