Re: Ubuntu: keep lyx 2.2.3 and 2.3.1 in same system

2018-11-03 Thread Alan L Tyree

On 4/11/18 4:35 am, Liviu Andronic wrote:

On 10/13/18, Paul Johnson  wrote:

I have some projects based on LyX 2.2.3 that I want to work on and I
don't want to update to new. However, I also have projects based on
2.3 and I can't edit those with old LyX.

Liviu Andronic worked out a way for this to be possible a few years
ago, but I cannot find documents about it. I wish I could have old and
new lyx installed at same time, to easily run one or the other.
I've tried to do this by installing 2.3.1 from the Ubuntu package and
then compiling 2.2.3 from source and installing off the path, but then
I found the 2 versions should not share a user configuration folder.
After using 2.3.1 and allowing it to revise ~/.lyx, then lyx 2.2.3
cannot start. Error like this:


I didn't continue doing the previous stable release packages as a
separate install (like I did for 1.6 and 2.0) as it didn't seem like
there was enough demand. I may reconsider this going forward.

If you're building from source, it's very easy to achieve this, and
you would only need to use this argument when configuring, e.g.:
--with-version-suffix=2.2

This will take care of most things, like renaming the binary to
'lyx2.2', the share and home folders to 'lyx2.2', etc. It works
surprisingly well. You should even be able to do make install, and in
principle it shouldn't clash with the existing install from the PPA.

Although it's necessarily more complicated, for inspiration you can
always take a look at, e.g., the lyx2.0 packages. Just fetch e.g.:
lyx2.0_2.0.8.1-2~trusty~ppa1.debian.tar.gz

and inspect the 'debian/rules' file. It will list the config options.

Regards,
Liviu



$ ./lyx
Warning: Could not read configuration file

Error while reading the configuration file
preferences.
Please check your installation.

So obviously I need to be more graceful, separate config folders.

I thought about building a new Debian package "lyx223". I'm pretty
sure that's what I think Liviu did.  For me that was a fail because
the deb packaging code for the lyx project has a lot of hard coded
folders like /usr/share/lyx, so it is not too easy to rebuild a
package to use alternate folders.

If you have advice about this, I would be glad to  hear it.

--
Paul E. Johnson   http://pj.freefaculty.org
Director, Center for Research Methods and Data Analysis http://crmda.ku.edu

To write to me directly, please address me at pauljohn at ku.edu.

And consider using GNU Stow. It makes it easy to manage installation and 
removal of compiled packages.


Cheers,

Alan



--
Alan L Tyreehttp://www2.austlii.edu.au/~alan



Re: LyX on iPad

2018-11-03 Thread Daniel Kian Mc Kiernan (the best Daniel of the bunch)

On 11/3/18 4:16 PM, Steve Litt wrote:


Daniel Kian Mc Kiernan (the best Daniel of the bunch) wrote:


On 11/2/18 9:57 AM, Steve Litt wrote:
> 
> Perhaps this is why LyX becomes less relevant every year.   

I don't think that peer-reviewed academic publication is going to 
vanish anytime soon; and, over about the last decade, 


Exactly! A decade ago LyX was about a lot more than peer-reviewed
academic publications, and 15 years ago it was safe to assume that
paper and PDF were enough output formats. More and more, LyX is
relegated to peer-reviewed academic publication.


There's no “Exactly!” here.  LyX becomes increasingly useful in its 
intended application.  The fact that it doesn't become some other 
application as applications of that other class become more popular 
doesn't change that.


You might as well demand that LyX evolve into a first-person shooter 
game.  Those are really popular, y'know.


Re: auto fixing mispelled words

2018-11-03 Thread Daniel Kian Mc Kiernan (the best Daniel of the bunch)

On 11/3/18 5:46 AM, paolo m. wrote:


Daniel Kian Mc Kiernan (the best Daniel of the bunch) wrote:


You've not answered my actual question.  A feature of the sort that
you propose is not likely to be popular; the vast majority of people
would, in constructing the underlying look-up table, find themselves
learning not to make the mistakes in the first place.


Sorry for my delay, i am not a 'heavy'  news readers user.
I do not know whether that feature would be popular, but it would be
useful for a number of lyx users.
I am not able to 'learn' how not to make typos. Do you?


I learn not to make _specific_ typographical errors, and the facility 
that you request would only deal with sets of specific errors.


Is is not a matter of learning, 


Of course it is.


it is our mind functioning that swaps letter
positions or doubles next letters while quickly writing text lines


Typing isn't an inborn skill; it is something that one learns. 
Learning to type a word and learning not to mistype it are the same 
thing.



Restoring the correct letters order for each word quickly would be a
great favour to a number of long paper writers.


In the case of a long paper, as opposed to a set of papers, the 
facility that you request doesn't offer much that global 
find-and-replace doesn't already do.  In either case, you are talking 
about working from an assembled list of corrections. (Recall that your 
original request involved a list assembled by the user of corrections 
to make.)


Re: Problem with spreadtab module and LyX 2.3.1

2018-11-03 Thread Andrew Parsloe




On 4/11/2018 2:15 a.m., Graeme wrote:
The spreadtab module is extremely useful, as it provides a wrapper 
around a conventional table environment, to enable some 
spreadsheet-like capabilities within the table (using the LaTeX 
package spreadtab).

It can be downloaded from wiki.lyx.org/Layouts/Modules.

When creating a long(multipage) table within the sLTable environment 
provided by the spreadtab module, there is one small difference 
between the plain LaTeX code produced by LyX 2.3.0 and 2.3.1.

Specifically, LyX 2.3.0 exports the lines:
\sLTable{}{%
\begin{longtable}{|c|c|c|c|c|}
while LyX 2.3.1 exports the lines
\sLTable{}{%
\begin{longtable}[c]{|c|c|c|c|c|}

In practice I think the LyX 2.3.1 version is correct, but it exposes a 
bug in spreadtab module version 1.4, which cannot handle the optional 
[c] argument following \begin{longtable}.


Thus LyX 2.3.0 can successfully generate a PDF file, while LyX 2.3.1 
fails with a LaTeX error. This applies to LyX under both Windows 10 
with MikTeX, and Linux Mint with TeXLive 2017.


An example LyX file is attached, along with the PDF file generated 
successfully from it using File/Export/PDF(ps2pdf) with LyX 2.3.0.


Unfortunately, I am not sure how to fix the bug in the spreadtab 
module, so help on this would be welcome.


Graeme

I'm the author of the module. I'll have a look. Thanks.

Andrew

---
This email has been checked for viruses by Avast antivirus software.
https://www.avast.com/antivirus



Re: Ubuntu: keep lyx 2.2.3 and 2.3.1 in same system

2018-11-03 Thread Liviu Andronic
On 10/13/18, Paul Johnson  wrote:
> I have some projects based on LyX 2.2.3 that I want to work on and I
> don't want to update to new. However, I also have projects based on
> 2.3 and I can't edit those with old LyX.
>
> Liviu Andronic worked out a way for this to be possible a few years
> ago, but I cannot find documents about it. I wish I could have old and
> new lyx installed at same time, to easily run one or the other.
> I've tried to do this by installing 2.3.1 from the Ubuntu package and
> then compiling 2.2.3 from source and installing off the path, but then
> I found the 2 versions should not share a user configuration folder.
> After using 2.3.1 and allowing it to revise ~/.lyx, then lyx 2.2.3
> cannot start. Error like this:
>

I didn't continue doing the previous stable release packages as a
separate install (like I did for 1.6 and 2.0) as it didn't seem like
there was enough demand. I may reconsider this going forward.

If you're building from source, it's very easy to achieve this, and
you would only need to use this argument when configuring, e.g.:
--with-version-suffix=2.2

This will take care of most things, like renaming the binary to
'lyx2.2', the share and home folders to 'lyx2.2', etc. It works
surprisingly well. You should even be able to do make install, and in
principle it shouldn't clash with the existing install from the PPA.

Although it's necessarily more complicated, for inspiration you can
always take a look at, e.g., the lyx2.0 packages. Just fetch e.g.:
lyx2.0_2.0.8.1-2~trusty~ppa1.debian.tar.gz

and inspect the 'debian/rules' file. It will list the config options.

Regards,
Liviu


> $ ./lyx
> Warning: Could not read configuration file
> 
> Error while reading the configuration file
> preferences.
> Please check your installation.
>
> So obviously I need to be more graceful, separate config folders.
>
> I thought about building a new Debian package "lyx223". I'm pretty
> sure that's what I think Liviu did.  For me that was a fail because
> the deb packaging code for the lyx project has a lot of hard coded
> folders like /usr/share/lyx, so it is not too easy to rebuild a
> package to use alternate folders.
>
> If you have advice about this, I would be glad to  hear it.
>
> --
> Paul E. Johnson   http://pj.freefaculty.org
> Director, Center for Research Methods and Data Analysis http://crmda.ku.edu
>
> To write to me directly, please address me at pauljohn at ku.edu.
>


Re: How to force tex2lyx to read unicode (from within Lyx)?

2018-11-03 Thread Richard Kimberly Heck
On 11/2/18 5:52 PM, Baris Erkus wrote:
> On 11/2/2018 1:33 PM, Baris Erkus wrote:
>> Hello,
>>
>> I am trying to import the a .tex  file into LyX (using file->import). 
>> The file has Turkish characters and I believe it is using UTF8 encoding. 
>> When I import it, it does not show Turkish characters properly. I 
>> attached the file for your play-around.
>>
>> When I import the file on the command line with the UTF8 option tex2lyx 
>> -e UTF8 ch1.tex, the LyX file looks just fine except one or two characters.
>>
>> So is there a way to tell to tex2lyx to use UTF8 encoding from within 
>> LyX? This issue is occured when I import a tex file that has 
>> \input{ch1.tex} in it. So, maybe LyX has and option to force tex2lyx to 
>> read in UTF8 for all imports?
>>
>> I found exactly same question on this post, but the answers seem to be 
>> unrelated:
>>
>> https://lyx-users.lyx.narkive.com/Rg1StNIT/how-to-force-tex2lyx-to-read-unicode-from-within-lyx
>>
>> Thanks
>>
>> Baris
>>
>
> Found the answer:

Well, that's *an* answer: You can set up a custom "utf8" import, if you
want. As JMarc said, though, tex2lyx should detect the encoding. Can you
file a bug report about this so it doesn't get lost?

Riki




Problem with spreadtab module and LyX 2.3.1

2018-11-03 Thread Graeme
The spreadtab module is extremely useful, as it provides a wrapper 
around a conventional table environment, to enable some spreadsheet-like 
capabilities within the table (using the LaTeX package spreadtab).

It can be downloaded from wiki.lyx.org/Layouts/Modules.

When creating a long(multipage) table within the sLTable environment 
provided by the spreadtab module, there is one small difference between 
the plain LaTeX code produced by LyX 2.3.0 and 2.3.1.

Specifically, LyX 2.3.0 exports the lines:
\sLTable{}{%
\begin{longtable}{|c|c|c|c|c|}
while LyX 2.3.1 exports the lines
\sLTable{}{%
\begin{longtable}[c]{|c|c|c|c|c|}

In practice I think the LyX 2.3.1 version is correct, but it exposes a 
bug in spreadtab module version 1.4, which cannot handle the optional 
[c] argument following \begin{longtable}.


Thus LyX 2.3.0 can successfully generate a PDF file, while LyX 2.3.1 
fails with a LaTeX error. This applies to LyX under both Windows 10 with 
MikTeX, and Linux Mint with TeXLive 2017.


An example LyX file is attached, along with the PDF file generated 
successfully from it using File/Export/PDF(ps2pdf) with LyX 2.3.0.


Unfortunately, I am not sure how to fix the bug in the spreadtab module, 
so help on this would be welcome.


Graeme


LyX231spreadtab1_4problem.pdf
Description: Adobe PDF document


LyX231spreadtab1_4problem.lyx
Description: application/lyx


Re: auto fixing mispelled words

2018-11-03 Thread paolo m.
Daniel Kian Mc Kiernan (the best Daniel of the bunch) wrote:

> 
> You've not answered my actual question.  A feature of the sort that
> you propose is not likely to be popular; the vast majority of people
> would, in constructing the underlying look-up table, find themselves
> learning not to make the mistakes in the first place.


Sorry for my delay, i am not a 'heavy'  news readers user. 
I do not know whether that feature would be popular, but it would be 
useful for a number of lyx users.
I am not able to 'learn' how not to make typos. Do you?
Is is not a matter of learning, it is our mind functioning that swaps letter 
positions or doubles next letters while quickly writing text lines
Restoring the correct letters order for each word quickly would be a 
great favour to a number of long paper writers.

regards
paolo m.