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

2017-07-29 Thread Scott Kostyshak
On Wed, Jul 26, 2017 at 10:17:44PM +0200, Uwe Stöhr wrote:
> El 26.07.2017 a las 08:54, Scott Kostyshak escribió:
> 
> > I see. We took a poll of users and got that the average preference is
> > larger than 120. See:
> > 
> >  
> > https://www.mail-archive.com/search?l=mid=20170606202640.45nziu2txu6dohek%40steph
> 
> 4 Win users is not a representative survey.

Agreed. Hopefully we can get more in the future.

Scott


signature.asc
Description: PGP signature


Re: classicthesis-Lyx-v4.2_biblatex_biber

2017-07-29 Thread Kornel Benko
Am Samstag, 29. Juli 2017 um 18:06:57, 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

For ubuntu/debian the package-name is 'biber'.
You may find something appropriate on your system.

Kornel

signature.asc
Description: This is a digitally signed message part.


Re: all-inclusive file format

2017-07-29 Thread Roberto

On 29/07/2017 13:30, Charlie wrote:

On Sat, 29 Jul 2017 12:55:35 +0200
Roberto  wrote:


Before answering think about your grandma having to do it ...


Would she be happy to use msword?

Charlie

She does not use it, because it so unstable, which hinders her learning. 
Instead, when she has a good software, she does learn ... (by the way 
this is real life experience from teaching elder people to use MS 
Windows Vs. Mac OS X)





Re: classicthesis-Lyx-v4.2_biblatex_biber

2017-07-29 Thread 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






Re: classicthesis-Lyx-v4.2_biblatex_biber

2017-07-29 Thread 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


Re: all-inclusive file format

2017-07-29 Thread Annaert Jan
I back Roberto on this one. Despite my pleas, some of my colleagues have 
already shied away from using LyX because of these unnecessary hurdles, and 
that’s a shame in my opinion as LyX has so much more to offer than MS Word and 
similar. And if word can “hide” a zip in a docx-file, perhaps it is useful to 
hide it in a lyxx-file too?

Best regards,

Jan

Jan Annaert

From: "lyx-users@lists.lyx.org"  on behalf of Roberto 

Date: Saturday 29 July 2017 12:44
To: "lyx-users@lists.lyx.org" 
Subject: Re: all-inclusive file format

The current lyx format then does just right for you. That does not mean
that does right for everybody who uses the software. I hate MS Word too,
but I also do not like having folders plenty of pictures that I have to
carefully select when I pass the file to someone or share it in dropbox
and alike.



On 28/07/2017 18:10, Hobbs,Tom wrote:
This is precisely what I was saying.  Rather than have everything hidden
in a file as MS Word does, simply put the needed graphics files in a
folder shared with you lyx document.  No special file formats are
needed.  I agree, I hate MS Word.
On Jul 28, 2017, at 10:02 AM, Joe 
> wrote:


It would appear that on Jul 28, Hobbs,Tom did say:

Goodness gracious. Just put everything in a folder and send that,
which is
precisely what MS Word does without you knowing it.





Re: all-inclusive file format

2017-07-29 Thread Charlie
On Sat, 29 Jul 2017 12:55:35 +0200
Roberto  wrote:

> Before answering think about your grandma having to do it ...

Would she be happy to use msword?

Charlie
-- 
Registered Linux User:- 329524
***

I had three chairs in my house; one for solitude, two for
friendship, three for societyHenry David Thoreau

***

Debian GNU/Linux - Magic indeed.

-


Re: all-inclusive file format

2017-07-29 Thread Roberto




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: all-inclusive file format

2017-07-29 Thread Roberto
The current lyx format then does just right for you. That does not mean 
that does right for everybody who uses the software. I hate MS Word too, 
but I also do not like having folders plenty of pictures that I have to 
carefully select when I pass the file to someone or share it in dropbox 
and alike.




On 28/07/2017 18:10, Hobbs,Tom wrote:
This is precisely what I was saying.  Rather than have everything hidden 
in a file as MS Word does, simply put the needed graphics files in a 
folder shared with you lyx document.  No special file formats are 
needed.  I agree, I hate MS Word.
On Jul 28, 2017, at 10:02 AM, Joe > wrote:



It would appear that on Jul 28, Hobbs,Tom did say:

Goodness gracious. Just put everything in a folder and send that, 
which is

precisely what MS Word does without you knowing it.






classicthesis-Lyx-v4.2_biblatex_biber

2017-07-29 Thread Michael Berger

Hi Philip, hi Jürgen,
thanks for your comments and suggestions. Whatever I tried the 
compilation to PDF fails.
I eventually tried Miede's original file once more - absolutely nothing 
added or removed, nothing changed.

When trying to compile to PDF I get:
BibTeX error: I found no \citation command-while reading file 
ClassicThesis.aux
BibTeX error: I found no \bibdata command-while reading file 
ClassicThesis.aux
BibTeX error: I found no \bibstyle command-while reading file 
ClassicThesis.aux
BibTeX error: I found no \citation command-while reading file 
ClassicThesis.aux
BibTeX error: I found no \bibdata command-while reading file 
ClassicThesis.aux
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

I have Mageia6, KDE
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.


Thanks and Best,
Michael


Re: all-inclusive file format

2017-07-29 Thread Dr Eberhard W Lisse
Cool.

el

-- 
Sent from Dr Lisse's iPad mini 4

> On 29 Jul 2017, at 07:00, Richard Heck  wrote:
> 
>> On 07/28/2017 07:47 PM, Dr Eberhard Lisse wrote:
>> As an option, like "Compressed"?
> 
> Yes, precisely.
> 
> Richard
> 
> 
>>> On 2017-07-27 18:48 , Richard Heck wrote:
>>> [...
>>> I'll think more about this. It's too late for 2.3, but it's something
>>> that could go into 2.4.
>>> 
>>> Richard
>> [...]
> 


Re: all-inclusive file format

2017-07-29 Thread Richard Heck
On 07/28/2017 07:47 PM, Dr Eberhard Lisse wrote:
> As an option, like "Compressed"?

Yes, precisely.

Richard


> On 2017-07-27 18:48 , Richard Heck wrote:
> [...
>> I'll think more about this. It's too late for 2.3, but it's something
>> that could go into 2.4.
>>
>> Richard
> [...]




Re: crash

2017-07-29 Thread Richard Heck
On 07/28/2017 04:57 PM, Patrick Dupre wrote:
> I still have this issue with version 2.2.3 (on fedora 26)

Unfortunately, this sort of crash report doesn't help us. With debug
symbols activated, we can't really tell anything from this backtrace. If
you could compile 2.2.3 yourself, and activate debug symbols, then that
would give us a much more useful crash report. Please also let us know
what you were doing when the crash occurred. It'd be even better if you
could figure out how reproduce it in a reliable way.

Richard


> (  1) lyx: lyx(+0x56d8dc) [0x560f21dbd8dc]
> (  2) lyx: lyx(+0x5d0ea6) [0x560f21e20ea6]
> (  3) lyx: lyx(+0x56c68e) [0x560f21dbc68e]
> (  4) lyx: lyx(+0x25ee38) [0x560f21aaee38]
> (  5) /lib64/libc.so.6: /lib64/libc.so.6(+0x366f0) [0x7f65176c06f0]
> (  6) lyx: lyx(+0x318fa6) [0x560f21b68fa6]
> (  7) lyx: lyx(+0x31a068) [0x560f21b6a068]
> (  8) lyx: lyx(+0x5465be) [0x560f21d965be]
> (  9) lyx: lyx(+0x488968) [0x560f21cd8968]
> ( 10) lyx: lyx(+0x318db0) [0x560f21b68db0]
> ( 11) lyx: lyx(+0x360ab0) [0x560f21bb0ab0]
> ( 12) lyx: lyx(+0x5c7f68) [0x560f21e17f68]
> ( 13) lyx: lyx(+0x5c3de1) [0x560f21e13de1]
> ( 14) /lib64/libQt5Core.so.5: QMetaObject::activate(QObject*, int, int, 
> void**)
> ( 15) /lib64/libQt5Widgets.so.5: QTabWidget::currentChanged(int)
> ( 16) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x2f4e27) 
> [0x7f651915be27]
> ( 17) /lib64/libQt5Core.so.5: QMetaObject::activate(QObject*, int, int, 
> void**)
> ( 18) /lib64/libQt5Widgets.so.5: QTabBar::currentChanged(int)
> ( 19) /lib64/libQt5Widgets.so.5: QTabBar::setCurrentIndex(int)
> ( 20) lyx: lyx(+0x5c3f67) [0x560f21e13f67]
> ( 21) lyx: lyx(+0x5a10a7) [0x560f21df10a7]
> ( 22) lyx: lyx(+0x5a170f) [0x560f21df170f]
> ( 23) lyx: lyx(+0x5a1908) [0x560f21df1908]
> ( 24) lyx: lyx(+0x5a34e9) [0x560f21df34e9]
> ( 25) lyx: lyx(+0x57c2c7) [0x560f21dcc2c7]
> ( 26) lyx: lyx(+0x573ce0) [0x560f21dc3ce0]
> ( 27) lyx: lyx(+0x5feafd) [0x560f21e4eafd]
> ( 28) /lib64/libQt5Core.so.5: QMetaObject::activate(QObject*, int, int, 
> void**)
> ( 29) /lib64/libQt5Widgets.so.5: QAction::triggered(bool)
> ( 30) /lib64/libQt5Widgets.so.5: QAction::activate(QAction::ActionEvent)
> ( 31) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x2c0424) 
> [0x7f6519127424]
> ( 32) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x2c7e8b) 
> [0x7f651912ee8b]
> ( 33) /lib64/libQt5Widgets.so.5: QMenu::mouseReleaseEvent(QMouseEvent*)
> ( 34) /lib64/libQt5Widgets.so.5: QWidget::event(QEvent*)
> ( 35) /lib64/libQt5Widgets.so.5: QMenu::event(QEvent*)
> ( 36) /lib64/libQt5Widgets.so.5: QApplicationPrivate::notify_helper(QObject*, 
> QEvent*)
> ( 37) /lib64/libQt5Widgets.so.5: QApplication::notify(QObject*, QEvent*)
> ( 38) lyx: lyx(+0x57e3aa) [0x560f21dce3aa]
> ( 39) /lib64/libQt5Core.so.5: QCoreApplication::notifyInternal2(QObject*, 
> QEvent*)
> ( 40) /lib64/libQt5Widgets.so.5: 
> QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, 
> QWidget*, QWidget**, QPointer&, bool)
> ( 41) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x1bc073) 
> [0x7f6519023073]
> ( 42) /lib64/libQt5Widgets.so.5: /lib64/libQt5Widgets.so.5(+0x1bea64) 
> [0x7f6519025a64]
> ( 43) /lib64/libQt5Widgets.so.5: QApplicationPrivate::notify_helper(QObject*, 
> QEvent*)
> ( 44) /lib64/libQt5Widgets.so.5: QApplication::notify(QObject*, QEvent*)
> ( 45) lyx: lyx(+0x57e3aa) [0x560f21dce3aa]
> ( 46) /lib64/libQt5Core.so.5: QCoreApplication::notifyInternal2(QObject*, 
> QEvent*)
> ( 47) /lib64/libQt5Gui.so.5: 
> QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*)
> ( 48) /lib64/libQt5Gui.so.5: 
> QGuiApplicationPrivate::processWindowSystemEvent(QWindowSystemInterfacePrivate::WindowSystemEvent*)
> ( 49) /lib64/libQt5Gui.so.5: 
> QWindowSystemInterface::sendWindowSystemEvents(QFlags)
> ( 50) /lib64/libQt5XcbQpa.so.5: /lib64/libQt5XcbQpa.so.5(+0x6e7a0) 
> [0x7f650a2667a0]
> ( 51) /lib64/libglib-2.0.so.0: 
> /lib64/libglib-2.0.so.0(g_main_context_dispatch+0x157) [0x7f6519bd8247]
> ( 52) /lib64/libglib-2.0.so.0: /lib64/libglib-2.0.so.0(+0x4a5e8) 
> [0x7f6519bd85e8]
> ( 53) /lib64/libglib-2.0.so.0: 
> /lib64/libglib-2.0.so.0(g_main_context_iteration+0x2c) [0x7f6519bd867c]
> ( 54) /lib64/libQt5Core.so.5: 
> QEventDispatcherGlib::processEvents(QFlags)
> ( 55) /lib64/libQt5Core.so.5: 
> QEventLoop::exec(QFlags)
> ( 56) /lib64/libQt5Core.so.5: QCoreApplication::exec()
> ( 57) lyx: lyx(+0x266ed5) [0x560f21ab6ed5]
> ( 58) lyx: lyx(+0x11be66) [0x560f2196be66]
> ( 59) /lib64/libc.so.6: /lib64/libc.so.6(__libc_start_main+0xea) 
> [0x7f65176aa4da]
> ( 60) lyx: lyx(+0x12491a) [0x560f2197491a]
>
>
> ===
>  Patrick DUPRÉ | | email: pdu...@gmx.com
>  Laboratoire de Physico-Chimie de l'Atmosphère | |
>  Université du Littoral-Côte d'Opale   | |
>  Tel.  (33)-(0)3 28 23 76 12   | | Fax: 03 28 65 82 44
>  189A, avenue Maurice