> On Dec 28, 2019, at 5:15 PM, Stanton Sanderson
>>
>> What is the behaviour you are observing?
>
> Away from my machine. Will report ASAP.
Davide,
As you stated, the edited file is temporary and must be saved first to replace
an existing pdf. Sorry for the noise.
Stan
Stan
> On Dec 28, 2019, at 3:45 PM, Davide Liessi wrote:
>
> What is the behaviour you are observing?
Away from my machine. Will report ASAP.
Il giorno sab 28 dic 2019 alle ore 22:30 Stanton Sanderson
ha scritto:
> Another behavior noted (change from previous versions): the new pdf generated
> when editing an existing file does not replace the old pdf.
I cannot reproduce this.
If I change an existing document, save it and compile it,
On 12/28/19 13:11, Stanton Sanderson wrote:
> An anomaly noted: document conversion from 2.19.2 to 2.19.83 fails with the
> following error message reported:
>> ImportError: Bad magic number in
>> /Applications/Frescobaldi.app/Contents/Resources/site.pyc
Il giorno sab 28 dic 2019 alle ore
> On Dec 28, 2019, at 3:23 PM, John Helly wrote:
>
> I confirm same behavior.
> J.
>
> On 12/28/19 13:11, Stanton Sanderson wrote:
>> (Mac OS Mojave (current), Frescobaldi 3.1 from dmg)
Another behavior noted (change from previous versions): the new pdf generated
when editing an existing
I confirm same behavior.
J.
On 12/28/19 13:11, Stanton Sanderson wrote:
> (Mac OS Mojave (current), Frescobaldi 3.1 from dmg)
>
> An anomaly noted: document conversion from 2.19.2 to 2.19.83 fails with the
> following error message reported:
>
>> ImportError: Bad magic number in
>>
(Mac OS Mojave (current), Frescobaldi 3.1 from dmg)
An anomaly noted: document conversion from 2.19.2 to 2.19.83 fails with the
following error message reported:
> ImportError: Bad magic number in
> /Applications/Frescobaldi.app/Contents/Resources/site.pyc
>
>
> The document has not been
