Re: Hunspell dictionaries browser can't be opened

2018-09-19 Thread Jean-Marc Lasgouttes
Le 19/09/2018 à 20:34, Wolfgang Engelmann a écrit : Clicking in the field where the path is to be set does not do anything, the cursor does not appear in this field, in contrast to all the other fields. Wolfgang Is hunspell enabled in your build? What OS is that? JMarc

Re: Hunspell dictionaries browser can't be opened

2018-09-19 Thread Wolfgang Engelmann
On 19.09.2018 19:16, Jürgen Spitzmüller wrote: Am Mittwoch, den 19.09.2018, 15:49 +0200 schrieb Wolfgang Engelmann: I try to insert the path to the Hunspell dictionaries, but the browse... can't be opened (clicking does not do anything). All the other browse... are klickable. I am using Lyx

Re: Hunspell dictionaries browser can't be opened

2018-09-19 Thread Jürgen Spitzmüller
Am Mittwoch, den 19.09.2018, 15:49 +0200 schrieb Wolfgang Engelmann: > I try to insert the path to the Hunspell dictionaries, but the > browse... > can't be opened (clicking does not do anything). All the other > browse... > are klickable. > > I am using Lyx 2.3.0 under Linux-Mint. Did you

Hunspell dictionaries browser can't be opened

2018-09-19 Thread Wolfgang Engelmann
I try to insert the path to the Hunspell dictionaries, but the browse... can't be opened (clicking does not do anything). All the other browse... are klickable. I am using Lyx 2.3.0 under Linux-Mint. What could I do? Wolfgang

Re: Supporting the cleverref package?

2018-09-19 Thread Klaus-Dieter Bauer
Another nice aspect of cleveref is, that it automatically calls references to appendix sections "appendix". This may become important, when I later decide to move whole sections to the appendix. On Wed, Sep 19, 2018 at 3:32 PM Klaus-Dieter Bauer < bauer.klaus.die...@gmail.com> wrote: > On Mon,

Re: Supporting the cleverref package?

2018-09-19 Thread Klaus-Dieter Bauer
On Mon, Sep 17, 2018 at 5:09 PM Richard Kimberly Heck wrote: > On 9/17/18 6:11 AM, Klaus-Dieter Bauer wrote: > > Thanks, I wasn't aware of \prettyref support :) > > > > For my purposes this fits the bill, as the commands seem to be > > effectively interchangeable and only really differ in how