Re: classicthesis-Lyx-v4.2_biblatex_biber

2017-07-30 Thread Michael Berger

Hi Jürgen, hi Philip,

in openSUSE Leap 42.2 I've tried countless times to produce PDF outputs 
with both, classicthesis-Lyx-v4.2_biblatex-biber and 
classicthesis-Lyx-v4.2_biblatex-bibtex8  but always ended up in endless 
loops.


After two weeks I tried openSUSE Leap 42.2 once more last night (out of 
desperation and frustration) and to my surprise both, biblatex-biber and 
biblatex-bibtex8, generated perfect PDF outputs - and very quickly.


In Documents > Settings > Bibliography > Bibliography Generation > 
Processor it offers


 * Default
 * biber !
 * bibtex
 * bibtex8

while in Mageia6 'biber' is still missing.
So, looks like one must wait till "biber" is made available in Mageia6 
and working.


Thanks a lot for your continuous support, and cheers!

Michael


Am 29.07.2017 um 18:06 schrieb Michael Berger:


Jürgen,

I did as you told me

- I installed all the groups of texlive packages Mageia is offering 
but I don't know for certain whether or not "biber" is installed; I 
find no way to look for a single package called texlive-biber or 
texlive-biblatex


- I did reconfigure several times

- I cannot set the Bibliography Processor to "biber" in Documents 
Settings because it is not a choice - all I see is: Default, bibtex, 
bibtex8. And in Tools > Preferences > Output > LaTeX > Processor I see 
only Custom, bibtex, bibtex8.


I hope I am not too stupid and sorry for bothering you!

Michael

Am 29.07.2017 um 13:51 schrieb Jürgen Spitzmüller:
Am 29.07.2017 10:42 vorm. schrieb "Michael Berger" >:


BibTeX error: I found no \bibstyle command-while reading file
ClassicThesis.aux

If I force the PDf output everything looks fine except that there
is no bibliography shown

LogType LaTeX shows some warnings but no errors
LogType BibTex shows some warnings but no errors


Obviously, you need to install biber, then reconfigure LyX and 
repeate the procedure I described.



I have Mageia6, KDE


Look for a package called texlive-biber or texlive-biblatex.

Document Settings Module: Linguistics

Funny enough, classicthesis-LyX-v4.2_biblatex_bibtex8 outputs a
perfect PDF, even if I completely remove/replace the LaTeX Preamble.


That's not funny, it is expected, if bibtex8 is installed.

Jürgen


Thanks and Best,
Michael








Compilación automática en Lyx Windows con Latexmk

2017-07-30 Thread Johnny Flores
buenas tardes amigos.


el presente es para solicitarles ayuda en lo respectivo a la instalación y
uso del paquete latexmk (o bien algún otro método existente) para lograr
que mi documento se compile automáticamente sin la necesidad de estarlo
haciendo yo. Yo trabajo en Windows 10, Lyx 2.2.2, Miktex 2.9.6100,

Agradezco cualquier ayuda y/o sugerencia para solucionar mi propósito.


Re: Help improve LyX's defaults by sharing your preferences

2017-07-30 Thread Stephan Witt
Am 30.07.2017 um 19:45 schrieb Uwe Stöhr :
> 
> El 29.07.2017 a las 23:47, Scott Kostyshak escribió:
> 
>> Agreed. Hopefully we can get more in the future.
> 
> As on no OS people are using 100% and as 120% was the reported the minimal 
> used zoom level, I again vote to make the new 100% the current 120%.

How do you want to achieve this? I’m not so confident it’s good to change the 
current computation of screen zoom. Every preference saved to disk would be 
„invalid“ after a change.

I’m not against a decision what the best default zoom level is.

Stephan

> 
> I opened an enhancement accordingly:
> http://www.lyx.org/trac/ticket/10737
> 
> (For the records: on Manjaro Linux KDE I have set 150% zoom.)
> 
> regards Uwe



Re: all-inclusive file format

2017-07-30 Thread Ricardo Berlasso
2017-07-30 19:13 GMT+02:00 Dr Eberhard Lisse :

> Roberto,
>
> If you use dropbox, can't you just put ALL the files there and edit
> from there?
>
> I am using a Mac and I can open and save files from LyX on the dropbox
> directories, including generating the PDF, so I am sure something
> similar will work on Windoze.
>
> I would them use Version Control and make sure your collaborators use
> that when editing their files.
>
> https://wiki.lyx.org/LyX/VersionControlInstallationAndUsage
>
> Now that you mention it, my mother, 23 years ago, at 64, never having
> touched a computer before, figured out how to use UUPC and MicroEmacs
> on DOS, so she could email me in Namibia :-)-O.
>
> For full disclosure I must confess that I wrote her a wrapper script
> (3000 lines BAT :-)-O), bought her the modem (1200/2400 baud and I
> think at that stage still illegal in Germany) and set up her uucp
> neighbor.
>
> To ask for a rewrite because (presumably academic) collaborators, can't
> handle a few clicks makes no sense to me.
>
> "computer-unsavvy" is Latin for lazy, right?
>

It may also mean "people without spare time trying to move on with their
lives".

Seriously, and forgive me for the off-topic here, but it seems that on this
thread is slowly surfacing one of the worst sins of open source
communities: the attitude of "it's easy for me, then it must be easy for
you too, you lazy looser".

Well, usually it's not easy. And people is neither lazy nor lousy nor
anything. For most people on the world computers are just boxes they use to
complete a task they don't even want to do. There is nothing they should be
ashamed of if they don't care about the "superiority of X approach compared
to the evil Y", specially if X requires a long learning process.

You cannot tell a normal person "if you want to write in collaboration,
just use git". You cannot say to anyone, not even to me, someone that's
been using Linux as his main system for the last two decades, to "use
make". That attitude is not only wrong, it is one of the main reasons why
we are still a minority on the consumer market. If your answers are
targeted to computer wise persons, only computer wise person will listen to
you.

As I said, I started to use F(L)OSS almost two decades ago. I'm using LyX
since before it switched to Qt. Back then I compiled every new version by
myself. But even with my experience I would have loved to have an
"everything within the file" file format when, twelve years ago, I was
writing my PhD thesis on LyX: at the time I did not had an internet
connection at home so syncing all the files was a real PITA. Even now, in a
time with automated backup utilities, usb drives and cloud storage I found
the lack of an easy way to work on a "project" instead of "fiddling with
several folders, each with dozens if not hundreds of files" quite
cumbersome.

And another thing: the fact that MS implemented some idea does not means
the idea is bad, saying so it's silly. A lot of F(L)OSS projects use "all
within the file" file formats: ODF, and open source ISO standard, it's just
a bunch of xml files and folders comfortably packed on a zip file. Also,
can you even imagine what would be to work on krita or gimp if those
projects just save all layers and masks on different files?

Please, people, think a bit on real users, not just on yourselves.

Thanks. [end of off-topic]

Regards,
Ricardo



>
> el
>
>
> On 2017-07-29 11:55 , Roberto wrote:
> >
> >>
> >> Make is your friend.
> >
> > I collaborate on dropbox with make-unfriendly computer-unsavvy people,
> > make is not an option - and this is not such an uncommon case I guess!
> > Instead, an _editable_ file format that __guarantees__ you have all is
> > needed to compile the file is a haven for data integrity.
> >
> > All the rest, I am sorry, is too geeky-pretensions-minded in my
> > opinion.  This kind of thinking in my opinion is ultimately the
> > reason of the same attitude that causes some people never get over
> > the learning curve of LaTeX. Do you want to collaborate with just
> > computer skilled people? or you want to collaborate on writing just
> > as effectively with just anybody? if you opt for the second, then LyX
> > is a great solution, but the need to carry around figures is still
> > a burden for some. Is this clear? (I said for some, maybe is not a
> > problem for me, not a problem for you, but is a problem for the other
> > half of the world! try to wear their shoes every now and then!)
> >
> > So, if you wanted to use make, then for most users you can as well
> > suggest to use LaTeX on vi :) is as much difficulty (infinity!)! Going
> > by this token one always ends up saying "my current implementation
> > can do it, just do 1), 2). 3) n) steps, but what effort does it
> > take? Before answering think about your grandma having to do it ...
>
>


Re: Help improve LyX's defaults by sharing your preferences

2017-07-30 Thread Uwe Stöhr

El 29.07.2017 a las 23:47, Scott Kostyshak escribió:


Agreed. Hopefully we can get more in the future.


As on no OS people are using 100% and as 120% was the reported the 
minimal used zoom level, I again vote to make the new 100% the current 120%.


I opened an enhancement accordingly:
http://www.lyx.org/trac/ticket/10737

(For the records: on Manjaro Linux KDE I have set 150% zoom.)

regards Uwe


Re: all-inclusive file format

2017-07-30 Thread Dr Eberhard Lisse
Roberto,

If you use dropbox, can't you just put ALL the files there and edit
from there?

I am using a Mac and I can open and save files from LyX on the dropbox
directories, including generating the PDF, so I am sure something
similar will work on Windoze.

I would them use Version Control and make sure your collaborators use
that when editing their files.

https://wiki.lyx.org/LyX/VersionControlInstallationAndUsage

Now that you mention it, my mother, 23 years ago, at 64, never having
touched a computer before, figured out how to use UUPC and MicroEmacs
on DOS, so she could email me in Namibia :-)-O.

For full disclosure I must confess that I wrote her a wrapper script
(3000 lines BAT :-)-O), bought her the modem (1200/2400 baud and I
think at that stage still illegal in Germany) and set up her uucp
neighbor.

To ask for a rewrite because (presumably academic) collaborators, can't
handle a few clicks makes no sense to me.

"computer-unsavvy" is Latin for lazy, right?

el


On 2017-07-29 11:55 , Roberto wrote:
> 
>>
>> Make is your friend.
>
> I collaborate on dropbox with make-unfriendly computer-unsavvy people,
> make is not an option - and this is not such an uncommon case I guess!
> Instead, an _editable_ file format that __guarantees__ you have all is
> needed to compile the file is a haven for data integrity.
>
> All the rest, I am sorry, is too geeky-pretensions-minded in my
> opinion.  This kind of thinking in my opinion is ultimately the
> reason of the same attitude that causes some people never get over
> the learning curve of LaTeX. Do you want to collaborate with just
> computer skilled people? or you want to collaborate on writing just
> as effectively with just anybody? if you opt for the second, then LyX
> is a great solution, but the need to carry around figures is still
> a burden for some. Is this clear? (I said for some, maybe is not a
> problem for me, not a problem for you, but is a problem for the other
> half of the world! try to wear their shoes every now and then!)
>
> So, if you wanted to use make, then for most users you can as well
> suggest to use LaTeX on vi :) is as much difficulty (infinity!)! Going
> by this token one always ends up saying "my current implementation
> can do it, just do 1), 2). 3) n) steps, but what effort does it
> take? Before answering think about your grandma having to do it ...



Re: LyX truncates spacing in Local Layout and in Listings

2017-07-30 Thread Richard Heck
On 07/28/2017 05:21 AM, haim.ros...@gmail.com wrote:
>
> I noticed that whenever I enter contents to
>
> * Document -> Settings -> Local Layout
>
> * Document -> Settings -> Listings
>
> * Program Listings Inset -> Settings -> Advanced
>
> All the leading tabs are deleted by the validation. This disturbs the
> reading of this content. Is there any solution for this?
>

It works with spaces, but not with tabs. Same problem with the preamble,
actually.

JMarc, this seems to be because Lexer::getLongString trips leading tabs.
Is there an easy way around that?

> Another issue is that the tab stops are fairly far away from each
> other. I think that cutting them to two thirds is much better.
>

If we get tabs working, it will be easy to fix this. (Note to self:
tabstop width property = 40.)

Richard