Jean-Marc Lasgouttes wrote:
> ATM there is no way to inhibit completion but you can set "minimum
> characters for words that should be completed" to 100 to effectively
> disable the feature.
Ok, I see, my misconception was that completion somehow uses spellcheck
dictionary. This explains why I
Le 03/07/2018 à 17:44, Pavel Sanda a écrit :
Jean-Marc Lasgouttes wrote:
Could you give me a step-by-step example where triangle does not appear
before you switch tab?
Super easy, just launch lyx, create new file, write "hel" and no triangle.
This is normal, since completion is done
Le 04/07/2018 à 04:40, Richard Kimberly Heck a écrit :
On 07/03/2018 07:18 PM, Pavel Sanda wrote:
Jean-Marc Lasgouttes wrote:
Le 03/07/2018 ?? 15:01, Pavel Sanda a écrit :
So it might be that indentation vs completion issue was here always,
but for some reason the new patch enables (by
On 07/03/2018 07:18 PM, Pavel Sanda wrote:
> Jean-Marc Lasgouttes wrote:
>> Le 03/07/2018 ?? 15:01, Pavel Sanda a écrit :
>>> So it might be that indentation vs completion issue was here always,
>>> but for some reason the new patch enables (by default disabled) completion
>>> even for users like
Jean-Marc Lasgouttes wrote:
> Le 03/07/2018 ?? 15:01, Pavel Sanda a écrit :
>> So it might be that indentation vs completion issue was here always,
>> but for some reason the new patch enables (by default disabled) completion
>> even for users like me who never used it in the text...
>
> Now in
Jean-Marc Lasgouttes wrote:
> Are you sure this did not happen in 2.3.0 or 2.2.x?
I did more testing now and you are right, the commit in question does not
introduce the problem I reported. Not sure where my initial testing went
wrong.
Pavel
Jean-Marc Lasgouttes wrote:
> Could you give me a step-by-step example where triangle does not appear
> before you switch tab?
Super easy, just launch lyx, create new file, write "hel" and no triangle.
Open the example with figure+note, edit the note, triangle appears.
Go back to tab1, hit enter
Le 03/07/2018 à 15:01, Pavel Sanda a écrit :
I have disabled Automatic inline completion for text in Preferences.
I create first new document and no completion rtiangle is there.
I open different document with that figure+note I used to show the triangle
painting problem recently and suddenly
Le 03/07/2018 à 15:01, Pavel Sanda a écrit :
So it might be that indentation vs completion issue was here always,
but for some reason the new patch enables (by default disabled) completion
even for users like me who never used it in the text...
Now in texted in master, completion is off when
Le 03/07/2018 à 15:01, Pavel Sanda a écrit :
I am puzzled by the completion behaviour in the current master.
I have disabled Automatic inline completion for text in Preferences.
I create first new document and no completion rtiangle is there.
I open different document with that figure+note I
On 03/07/2018 12:25, Jean-Marc Lasgouttes wrote:
Le 03/07/2018 à 12:24, Daniel a écrit :
On 14/06/2018 17:46, Pavel Sanda wrote:
Could we disable completion when the cursor stands
at the end of selected text, so the lfun for nesting in command-sequence
takes priority over completion?
The
Jean-Marc Lasgouttes wrote:
> Le 03/07/2018 ?? 10:32, Pavel Sanda a écrit :
>> Well, this is design question. Should nesting have priority over completion
>> or not? I think it's fine if completion wins in case you are in the middle
>> of writing some word. But clearly you doing something
Le 03/07/2018 à 12:24, Daniel a écrit :
On 14/06/2018 17:46, Pavel Sanda wrote:
Could we disable completion when the cursor stands
at the end of selected text, so the lfun for nesting in command-sequence
takes priority over completion?
The cursor can be at the beginning of a selection and
On 14/06/2018 17:46, Pavel Sanda wrote:
Could we disable completion when the cursor stands
at the end of selected text, so the lfun for nesting in command-sequence
takes priority over completion?
The cursor can be at the beginning of a selection and still I would
expect it to behave the same
Le 03/07/2018 à 10:32, Pavel Sanda a écrit :
Well, this is design question. Should nesting have priority over completion or
not?
I think it's fine if completion wins in case you are in the middle of writing
some
word. But clearly you doing something different when the block is selected.
I
Jean-Marc Lasgouttes wrote:
> Le 02/07/2018 ?? 22:59, Pavel Sanda a écrit :
>> Pavel Sanda wrote:
>>> Often now when you hit tab completion menu appears instead of nesting
>>> which is annoying. Could we disable completion when the cursor stands
>>> at the end of selected text, so the lfun for
Le 02/07/2018 à 22:59, Pavel Sanda a écrit :
Pavel Sanda wrote:
Often now when you hit tab completion menu appears instead of nesting
which is annoying. Could we disable completion when the cursor stands
at the end of selected text, so the lfun for nesting in command-sequence
takes priority
Pavel Sanda wrote:
> Jean-Marc Lasgouttes wrote:
> > commit f1ea7fee5cda3fbbeb9fdbb8bec2bd91c0745e56
> > Author: Jean-Marc Lasgouttes
> > Date: Fri Jun 8 10:32:47 2018 +0200
> >
> > Unbreak completion in text mode
> >
> > Completion uses a complicated async scheme based on timers
Jean-Marc Lasgouttes wrote:
> commit f1ea7fee5cda3fbbeb9fdbb8bec2bd91c0745e56
> Author: Jean-Marc Lasgouttes
> Date: Fri Jun 8 10:32:47 2018 +0200
>
> Unbreak completion in text mode
>
> Completion uses a complicated async scheme based on timers to update
> itself. This is
19 matches
Mail list logo
