Am 15.01.2017 um 00:05 schrieb Stephan Witt :
>
> Am 14.01.2017 um 17:42 schrieb pdv :
>>
>> The current master fails to start-up (on macOS) if the default Python is
>> Python3.x, because prefs2prefs.py is not compatible with Python3.
>
> This looks
Am 14.01.2017 um 17:42 schrieb pdv :
>
> The current master fails to start-up (on macOS) if the default Python is
> Python3.x, because prefs2prefs.py is not compatible with Python3.
This looks strange. The python people say python 2.7 is the default on Mac
(including the
On Fri, Jan 13, 2017 at 06:24:32PM +0100, Juergen Spitzmueller wrote:
> commit fc546b7dcc793a77b44c2f3e3abc780d768a18ed
> Author: Juergen Spitzmueller
> Date: Fri Jan 13 18:23:42 2017 +0100
>
> Basic support for natbib & jurabib options
>
> This re-uses the options
Le 14/01/2017 à 16:26, Kornel Benko a écrit :
I don't see it. Here it displays as a 6-liner in Slovak translation.
QT5.7
OS Mint17.3
desktop MATE
Kornel
Thanks Kornel and Jürgen for the replies. I will stop my investigation
but do not hesitate to report issues like this in the
Am Samstag, den 14.01.2017, 10:52 -0500 schrieb Richard Heck:
> Sorry, thought the change was to a BufferParam, but it's to a
> preference, isn't it?
Yes. I nevertheless bumped the prefs format meanwhile.
Jürgen
>
> rh
>
signature.asc
Description: This is a digitally signed message part
On 01/14/2017 06:01 AM, Guenter Milde wrote:
On 2017-01-14, Pavel Sanda wrote:
Guenter Milde wrote:
A more general question to all developers:
When checking for default viewer/editor applications during (re)configure,
should LyX
a) prefer feature rich applications, or
b) prefer small and
The current master fails to start-up (on macOS) if the default Python is
Python3.x, because prefs2prefs.py is not compatible with Python3.
In python23() in os.cpp both Python 2 and Python 3 are accepted.
As a temporarily workaround I've built with PYTHON="/usr/bin/python"
which is the
On 01/14/2017 09:44 AM, Guillaume Munch wrote:
> Le 13/01/2017 à 23:28, Richard Heck a écrit :
>>
>> Format change?
>>
>
> It does not look like it to me.
Sorry, thought the change was to a BufferParam, but it's to a
preference, isn't it?
rh
Am Samstag, 14. Januar 2017 um 15:44:33, schrieb Guillaume Munch
> Le 14/01/2017 à 10:07, Jürgen Spitzmüller a écrit :
> > Am Freitag, den 13.01.2017, 22:02 +0100 schrieb Guillaume Munch:
> >> Weird, it displays fine here at 119dfcb1. Are there precise steps
> >> that I
> >> must
Am Samstag, den 14.01.2017, 15:44 +0100 schrieb Guillaume Munch:
> Have you noticed this issue at other places?
No.
>
> What is the Qt version, locale, OS, and desktop environment?
Qt 5.7.1, both en_EN and de_DE, Linux (openSuse Tumbleweed), GNOME
3.22.
However, I cannot reproduce myself any
Le 13/01/2017 à 23:28, Richard Heck a écrit :
Format change?
It does not look like it to me. However:
/// Return the actual bibtex command (lyxrc or buffer param)
- std::string const & bibtexCommand() const;
+ std::string const bibtexCommand() const;
I saw const-value
Le 14/01/2017 à 10:07, Jürgen Spitzmüller a écrit :
Am Freitag, den 13.01.2017, 22:02 +0100 schrieb Guillaume Munch:
Weird, it displays fine here at 119dfcb1. Are there precise steps
that I
must follow to reproduce the bug?
* Open the BibTeX inset dialog
* Hit "Add"
* On the sub-dialog, hover
Am Samstag, den 14.01.2017, 07:39 -0500 schrieb PhilipPirrip:
> On 01/14/2017 05:39 AM, Jürgen Spitzmüller wrote:
> > I prefer to get them without jumping through such hoops.
>
> I'm sorry, I was switching from t'bird to some other news readdder.
> Attaching the files again.
Thanks! Should be
On 01/14/2017 05:39 AM, Jürgen Spitzmüller wrote:
I prefer to get them without jumping through such hoops.
I'm sorry, I was switching from t'bird to some other news readdder.
Attaching the files again.
childOne.lyx
Description: application/lyx
childTwo.lyx
Description: application/lyx
On 2017-01-14, Guenter Milde wrote:
> On 2017-01-14, Richard Heck wrote:
>> On 01/14/2017 12:11 AM, Scott Kostyshak wrote:
>>> On Sat, Jan 14, 2017 at 05:56:21PM +1300, gordon cooper wrote:
...
>> Could we at least say what the character was? Or report its location in
>> the file?
> With an
On 2017-01-14, Jürgen Spitzmüller wrote:
> Am Freitag, den 13.01.2017, 18:56 -0500 schrieb Richard Heck:
>> The attached files illustrate a problem that I raised, and was told
>> not to worry about, when "---" was exchanged for \textemdash. The
>> problem is that the latter does not break the way
On 2017-01-14, Pavel Sanda wrote:
> Guenter Milde wrote:
>> A more general question to all developers:
>> When checking for default viewer/editor applications during (re)configure,
>> should LyX
>> a) prefer feature rich applications, or
>> b) prefer small and fast-starting applications.
> As I
Am Samstag, den 14.01.2017, 10:45 +0100 schrieb Kornel Benko:
> They did. How to get the data:
> 1.) save the mail to a file, e.g. /tmp/childOne.lyx
> 2.) use uudeview on that file (in another directory)
> ==> you get the undecoded childOne.lyx
I prefer to get them without jumping through
On 2017-01-14, Richard Heck wrote:
> On 01/14/2017 12:11 AM, Scott Kostyshak wrote:
>> On Sat, Jan 14, 2017 at 05:56:21PM +1300, gordon cooper wrote:
>> Thanks for reporting this problem. Next time it would be helpful if you
>> sent an example file. I went ahead and created an example file and I
Am Samstag, 14. Januar 2017 um 10:15:29, schrieb Jürgen Spitzmüller
> Am Freitag, den 13.01.2017, 20:17 + schrieb PhilipPirrip:
> > I'm reporting that the master document won't compile with a child
> > document containing some commands specific to natbib.
> > In the attached
Am Freitag, den 13.01.2017, 18:56 -0500 schrieb Richard Heck:
> The attached files illustrate a problem that I raised, and was told
> not
> to worry about, when "---" was exchanged for \textemdash. The problem
> is
> that the latter does not break the way the former does. What can we
> do
> about
Am Freitag, den 13.01.2017, 20:17 + schrieb PhilipPirrip:
> I'm reporting that the master document won't compile with a child
> document containing some commands specific to natbib.
> In the attached examples, it will be because of a citation command
> in
> childOne.lyx.
> Can this be
Am Freitag, den 13.01.2017, 22:02 +0100 schrieb Guillaume Munch:
> Weird, it displays fine here at 119dfcb1. Are there precise steps
> that I
> must follow to reproduce the bug?
* Open the BibTeX inset dialog
* Hit "Add"
* On the sub-dialog, hover over the list widget
I get a long one-liner
Am Freitag, den 13.01.2017, 19:32 + schrieb PhilipPirrip:
> Hope you don't mind if I report other findings here. Reporting on
> lyx.org
> bug tracker takes too much time:
No, that's perfect.
> New document. Choose biblatex in Document Settings. Insert an
> option,
> Apply. Delete the
24 matches
Mail list logo