Il 19/05/2011 12:42, Vincent van Ravesteijn ha scritto:
Why don't we get rid of the string-based encoding, at least when the
functionality is invoked from the GUI ?
I mean, something where we put into the LFun a direct pointer to this new
struct you're talking about, then
we use that in lyxfin
> Why don't we get rid of the string-based encoding, at least when the
> functionality is invoked from the GUI ?
>
> I mean, something where we put into the LFun a direct pointer to this new
> struct you're talking about, then
> we use that in lyxfind.cpp instead of encoding/decoding strings.
>
Il 19/05/2011 10:21, Abdel Younes ha scritto:
On May 19, 2011, at 10:01 AM, Vincent van Ravesteijn wrote:
On 19-5-2011 9:39, Abdel Younes wrote:
On May 18, 2011, at 10:33 PM, sw...@lyx.org wrote:
Author: switt
FuncRequest(LFUN_WORD_REPLACE,
re
On May 19, 2011, at 10:01 AM, Vincent van Ravesteijn wrote:
> On 19-5-2011 9:39, Abdel Younes wrote:
>>
>> On May 18, 2011, at 10:33 PM, sw...@lyx.org wrote:
>>
>>> Author: switt
>>> Date: Wed May 18 22:33:57 2011
>>> New Revision: 38781
>>> URL: http://www.lyx.org/trac/changeset/38781
>>>
>>>
On 19-5-2011 9:39, Abdel Younes wrote:
>
> On May 18, 2011, at 10:33 PM, sw...@lyx.org wrote:
>
>> Author: switt
>> Date: Wed May 18 22:33:57 2011
>> New Revision: 38781
>> URL: http://www.lyx.org/trac/changeset/38781
>>
>> Log:
>> #7564 make the move forward to next match after text replacement
On May 18, 2011, at 10:33 PM, sw...@lyx.org wrote:
> Author: switt
> Date: Wed May 18 22:33:57 2011
> New Revision: 38781
> URL: http://www.lyx.org/trac/changeset/38781
>
> Log:
> #7564 make the move forward to next match after text replacement optional and
> suppress it when replace a word by
