Re: Change Algorithm Numbering
On 09/20/2018 10:14 AM, Pascal Francq (Mailing lists) wrote:
Hi,
I try to change the change the numbering schema of algorithms in the
form 'A1', 'A2', etc.
So I add the following command in the preamble of the document:
\renewcommand{\thealgorithm}{A\arabic{algorithm}}
But LyX says it "thealgorithm" is undefined.
Any one an idea?
Thanks in advance.
Can you post a minimal example showing the current version of what you
are trying to change, and then indicate in it somewhere "I want to
change this piece here to A1" or whatever?
Paul
Change Algorithm Numbering
Hi,
I try to change the change the numbering schema of algorithms in the
form 'A1', 'A2', etc.
So I add the following command in the preamble of the document:
\renewcommand{\thealgorithm}{A\arabic{algorithm}}
But LyX says it "thealgorithm" is undefined.
Any one an idea?
Thanks in advance.
--
Pascal Francq
Re: Hunspell dictionaries browser can't be opened
Le 20/09/2018 à 13:16, Wolfgang Engelmann a écrit : You mean, possible errors or so after ./configure? At the end of the configure run, there is a summary that is displayed, like this: Configuration Host type: x86_64-pc-linux-gnu Special build flags: build=development std-regex warnings assertions stdlib-debug use-hunspell use-enchant Bundled libraries:boost C++ Compiler:g++ (5.4.0) C++ Compiler flags: -Wall -Wextra -g -O -std=c++14 C++ Compiler user flags: Linker flags: Linker user flags: Qt Frontend: Qt version: 4.8.7 Packaging: posix LyX binary dir: /usr/local/bin LyX files dir: /usr/local/share/lyx-master What is interesting here is the flags "use-hunspell" and "use-enchant" that say that these two have been found. If you send the config.log file to me or to the list, I will probably be able to tell you what went wrong. JMarc
Re: Hunspell dictionaries browser can't be opened
On 20.09.2018 11:04, Jean-Marc Lasgouttes wrote: Le 20/09/2018 à 10:49, Wolfgang Engelmann a écrit : Thanks Jürgen, will try it with the 2.3.1 version of LyX. /you don't have to compile hunspell, but LyX must be compiled with hunspell support enabled/ you mean hunspell must be installed (e.g. with synaptics)? Wolfgang When you configure, LyX checks what development files are available to interface with spellcheckers. Possibilities are enchant (package libenchant-dev on debian), hunspell (libhunspell-dev), aspell (libaspell-dev). In general enchant is fine. Could you show what is the result of configuring LyX before building? (you are building yourself, right?) You mean, possible errors or so after ./configure? Wolfgang JMarc
Re: Hunspell dictionaries browser can't be opened
On 20.09.2018 11:04, Jürgen Spitzmüller wrote: Am Do., 20. Sep. 2018 um 10:50 Uhr schrieb Wolfgang Engelmann mailto:engelm...@uni-tuebingen.de>>: /you don't have to compile hunspell, but LyX must be compiled with hunspell support enabled/ you mean hunspell must be installed (e.g. with synaptics)? On your side, definitely. As I explained, hunspell must also be enabled additionally by the person who built your binary. I haven't seen any binary yet for linux-Mint of the 2.3.1 Version, therefore i compile it from source Jürgen Wolfgang
Re: Hunspell dictionaries browser can't be opened
Le 20/09/2018 à 10:49, Wolfgang Engelmann a écrit : Thanks Jürgen, will try it with the 2.3.1 version of LyX. /you don't have to compile hunspell, but LyX must be compiled with hunspell support enabled/ you mean hunspell must be installed (e.g. with synaptics)? Wolfgang When you configure, LyX checks what development files are available to interface with spellcheckers. Possibilities are enchant (package libenchant-dev on debian), hunspell (libhunspell-dev), aspell (libaspell-dev). In general enchant is fine. Could you show what is the result of configuring LyX before building? (you are building yourself, right?) JMarc
Re: Hunspell dictionaries browser can't be opened
Am Do., 20. Sep. 2018 um 10:50 Uhr schrieb Wolfgang Engelmann < engelm...@uni-tuebingen.de>: > *you don't have to compile hunspell, but LyX must be compiled with > hunspell support enabled* > you mean hunspell must be installed (e.g. with synaptics)? > On your side, definitely. As I explained, hunspell must also be enabled additionally by the person who built your binary. Jürgen > Wolfgang >
Re: Hunspell dictionaries browser can't be opened
On 20.09.2018 10:31, Jürgen Spitzmüller wrote: Am Do., 20. Sep. 2018 um 09:05 Uhr schrieb Wolfgang Engelmann mailto:engelm...@uni-tuebingen.de>>: > /home/wolfgang/lyx-2.3.0/3rdparty/hunspell/1.6.2 > I did not know that I have to compile hunspell; I had never to do it > before. You don't have to compile hunspell, but LyX must be compiled with hunspell support enabled (or, for that matter, hunspell support, which is enabled by default, can be disabled at compile time). If hunspell is enabled, LyX will check if the hunspell libraries are there, and if so, hunspell support will be enabled. This is the job of your package manager, if you use a binary. If you compile LyX yourself, assure hunspell-devel is installed. p.s. could I install enchant instead of hunspell (enchant is apparently also using hunspell among others) or is lyx fixed to hunspell? LyX supports aspell, enchant, and hunspell. You can switch the engines in preferences (if the respective engine is supported on your box). Jürgen Wolfgang Thanks Jürgen, will try it with the 2.3.1 version of LyX. /you don't have to compile hunspell, but LyX must be compiled with hunspell support enabled/ you mean hunspell must be installed (e.g. with synaptics)? Wolfgang
Re: Hunspell dictionaries browser can't be opened
Am Do., 20. Sep. 2018 um 09:05 Uhr schrieb Wolfgang Engelmann < engelm...@uni-tuebingen.de>: > > /home/wolfgang/lyx-2.3.0/3rdparty/hunspell/1.6.2 > > I did not know that I have to compile hunspell; I had never to do it > > before. You don't have to compile hunspell, but LyX must be compiled with hunspell support enabled (or, for that matter, hunspell support, which is enabled by default, can be disabled at compile time). If hunspell is enabled, LyX will check if the hunspell libraries are there, and if so, hunspell support will be enabled. This is the job of your package manager, if you use a binary. If you compile LyX yourself, assure hunspell-devel is installed. > p.s. could I install enchant instead of hunspell (enchant is apparently > also using hunspell among others) or is lyx fixed to hunspell? > LyX supports aspell, enchant, and hunspell. You can switch the engines in preferences (if the respective engine is supported on your box). Jürgen > Wolfgang >
Re: Hunspell dictionaries browser can't be opened
On 20.09.2018 08:43, Wolfgang Engelmann wrote: On 19.09.2018 22:01, Jean-Marc Lasgouttes wrote: 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 cat /etc/issue Linux Mint 18.3 Sylvia \n \l /home/wolfgang/lyx-2.3.0/3rdparty/hunspell/1.6.2 I did not know that I have to compile hunspell; I had never to do it before. If I use the instructions in the readme file of hunspell and do wolfgang@wolfgang-Mr-Whisper-Ultra-SSD-II:~/lyx-2.3.0/3rdparty/hunspell/1.6.2$ autoreconf -vfi I get autoreconf: 'configure.ac' or 'configure.in' is required don't know how to proceed here. Wolfgang p.s. could I install enchant instead of hunspell (enchant is apparently also using hunspell among others) or is lyx fixed to hunspell? Wolfgang
