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
> Nice trick :) However, it is maybe a bit too hackish to add, in lyx
> 1.0.x...
Yes, that's what I realized once I remembered how I did it. But it got
out the letters . . . On the other hand, I still have no job for this
fall :(
--
> "Richard" == Richard E Hawkins <[EMAIL PROTECTED]> writes:
Richard> Later that night, I recalled exactly how i solved it: before
Richard> the cut/ paste, I insert the text "MAGICMARKERSTRING" or some
Richard> such, then do the cut/paste, then delete the string. It was
Richard> a hack to st
> > "Richard" == Richard E Hawkins <[EMAIL PROTECTED]> writes:
>
> Richard> I'd offer to do it, but at the moment, I'm in over my head.
> Richard> It would be mid-august (at the earliest). But I've attached
> Richard> the tarball for mailmerge, in case anyone else wants to steal
> Richard> t
> "Richard" == Richard E Hawkins <[EMAIL PROTECTED]> writes:
Richard> I'd offer to do it, but at the moment, I'm in over my head.
Richard> It would be mid-august (at the earliest). But I've attached
Richard> the tarball for mailmerge, in case anyone else wants to steal
Richard> the code or s
> Richard> oh, well. I though someone fixed it a few months ago, and
> Richard> figured it had krept back in.
> What I fixed recently is that any inset matched a space in
> Find/Replace.
awe :(
> Richard> I had to fight with this for the mailmerge, too. iirc, it
> Richard> was a matter of
> "Richard" == Richard E Hawkins <[EMAIL PROTECTED]> writes:
Richard> jmarc jmentioned,
>> > "Richard" == Richard E Hawkins <[EMAIL PROTECTED]>
>> writes:
>>
Richard> I found that I had several loose spaces before commas. I
Richard> tried to use find/replace to replace " ," with ",", bu
jmarc jmentioned,
> > "Richard" == Richard E Hawkins <[EMAIL PROTECTED]> writes:
>
> Richard> I found that I had several loose spaces before commas. I
> Richard> tried to use find/replace to replace " ," with ",", but while
> Richard> it found them correctly, it leaves the initial space, an
> "Richard" == Richard E Hawkins <[EMAIL PROTECTED]> writes:
Richard> I found that I had several loose spaces before commas. I
Richard> tried to use find/replace to replace " ," with ",", but while
Richard> it found them correctly, it leaves the initial space, and
Richard> places an addition
I found that I had several loose spaces before commas. I tried to use
find/replace to replace " ," with ",", but while it found them
correctly, it leaves the initial space, and places an additional space
*after* the comma (generally harmless, as it goes away), leaving the
offending space in
13 matches
Mail list logo
