Re: Beta1 is slow on undo

[Jean-Marc Lasgouttes]

Le 9 octobre 2017 20:25:41 GMT+02:00, racoon  a écrit :
>I think Richard mentioned as well that he does not get that much delay 
>either. It might be due to my archaic system (Windows 7 Core 2 Duo @
>1.8 
>GHz). I know I should try to get a new one.. But so far I have been
>able 
>to use LyX with full satisfaction. And there may be others on slow
>machines.
>
>Daniel

This is not supposed to be slow. Let's see what we can do.

JMarc

Re: Beta1 is slow on undo

[racoon]

On 09.10.2017 07:28, Scott Kostyshak wrote:

On Sun, Oct 08, 2017 at 03:01:49PM +, Richard Heck wrote:

On 10/08/2017 10:19 AM, racoon wrote:

On 08.10.2017 00:19, Scott Kostyshak wrote:

On Sat, Oct 07, 2017 at 05:57:48PM +, Richard Heck wrote:

On 10/07/2017 12:09 PM, racoon wrote:

Hi,

I noticed that beta1 shows some slowness when undoing with some of my
documents. While undoing is instantaneous in 2.2.3, 2.3 takes about a
second to respond to it.

Did anyone notice this? I don't have a very fast computer though.


Yes, I have also seen that, and my machines are pretty fast.


I can't reproduce. My test case was to open the user guide, selected
all, delete, and undo. Both were instantaneous for me. Do you have a
better test case for me?


Okay, I think I have narrowed it down to the inclusion of any
bibliography. Test case attached.


That would make sense, at least in so far as bibliography handling was
changed a lot. But it's hard to imagine why it would affect undo. Do we
re-read the bibliography or something now after an undo?


Bisect points to 02847641. I want to emphasize though that I only see a
very minor increase in slowness. I would not have realized it if it
weren't pointed out. It is certainly not a second delay for me. So
perhaps this is not the change that Richard and racoon are seeing.


I think Richard mentioned as well that he does not get that much delay 
either. It might be due to my archaic system (Windows 7 Core 2 Duo @ 1.8 
GHz). I know I should try to get a new one.. But so far I have been able 
to use LyX with full satisfaction. And there may be others on slow machines.


Daniel

Re: Fwd: Failures of seminar example file

[Scott Kostyshak]

On Mon, Oct 09, 2017 at 03:01:03PM +, Kornel Benko wrote:

> That's wonderful fast. Many thanks

Thanks, Kornel!

Scott


signature.asc
Description: PGP signature

Re: Failures of seminar example file

[Scott Kostyshak]

On Mon, Oct 09, 2017 at 08:00:32AM +, Guenter Milde wrote:

> > I see many messages in the log (creating pdf2)
> > Missing character: There is no 0 in font nullfont!
> 
> This is a false positive from the PNG package http://ctan.org/pkg/pgf.
> We already added an exception to the LyX error reporting for it.

I wonder if we want "Next Error" in the error dialog to skip this.
Otherwise it can be challenging to find the error in LyX's dialog if
there are a lot of such messages.

Scott


signature.asc
Description: PGP signature

Re: Fwd: Failures of seminar example file

[Kornel Benko]

Am Montag, 9. Oktober 2017 um 16:58:25, schrieb Herbert Voss 

> Am 09.10.2017 um 16:04 schrieb Kornel Benko:
> >
> >> \ifpst@psfonts is already defined in the current pstricks.sty!  Your fix
> >> doesn't make sense. There must be something different!
> >>
> >> I suppose that you are running latex but
> >> loading PSTricks with \input{pstricks.tex}  which cannot work. It
> >> should be included by \usepackage. Only for running TeX \input
> >> is the right macro.
> >>
> >> Without a _complete_ example  ;-)
> >>
> > OK, here it comes.
> 
> Uh, example is correct, but minimal is something different ...   ;-)

Ahm, sorry

> seminar.cls  is a really ancient class and shouldn't be used for
> new presentations. However, it loads pst-ovl and that
> package does \input{pstricks.tex} which is the problem. it should be
> in pst-ovl.sty:
> 
> [...]
> \RequirePackage{pstricks}
> \input{pst-ovl}
> [...]
> 
> I'll upload a new version.
> 
> Herbert

That's wonderful fast. Many thanks

Kornel

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

Re: Fwd: Failures of seminar example file

[Kornel Benko]

Am Montag, 9. Oktober 2017 um 15:56:56, schrieb Herbert Voss 

> Am 09.10.2017 um 15:39 schrieb Kornel Benko:
> > we have problems with pstricks.sty after the last update of TL17.
> >
> > 'Correcting' texmf-dist/tex/generic/pstricks/pstricks.tex:34 to
> > \expandafter\ifx\csname @latexerr\endcsname\relax % do we have TeX? 
> > then @latexerr isn't defined
> >   \input pstricks-tex.def
> > \else
> >   \newif\ifpst@psfonts  \pst@psfontsfalse
> > \fi
> > cures the compilation for me. Would you like to take a look please?
> >
> > Kornel
>
> Hi Kornel,
>
> \ifpst@psfonts is already defined in the current pstricks.sty!  Your fix
> doesn't make sense. There must be something different!
>
> I suppose that you are running latex but
> loading PSTricks with \input{pstricks.tex}  which cannot work. It
> should be included by \usepackage. Only for running TeX \input
> is the right macro.
>
> Without a _complete_ example  ;-)
>
> Herbert

OK, here it comes.

Kornel

signature.asc
Description: This is a digitally signed message part.
%% LyX 2.4.0dev created this file.  For more info, see http://www.lyx.org/.
%% Do not edit unless you really know what you are doing.
\documentclass[a4paper,english,slidesec]{seminar}
\usepackage{lmodern}
\renewcommand{\sfdefault}{lmss}
\renewcommand{\ttdefault}{lmtt}
\usepackage[T1]{fontenc}
\usepackage[latin9]{inputenc}
\pagestyle{empty}
\usepackage{color}
\usepackage{babel}
\usepackage{booktabs}
\usepackage{textcomp}
\usepackage{bbding}
\usepackage[unicode=true,pdfusetitle,
 bookmarks=true,bookmarksnumbered=false,bookmarksopen=false,
 breaklinks=false,pdfborder={0 0 0},pdfborderstyle={},backref=false,colorlinks=true]
 {hyperref}

\makeatletter

%% LyX specific LaTeX commands.
\pdfpageheight\paperheight
\pdfpagewidth\paperwidth

\newcommand{\noun}[1]{\textsc{#1}}
\DeclareRobustCommand*{\lyxarrow}{%
\@ifstar
{\leavevmode\,$\triangleleft$\,\allowbreak}
{\leavevmode\,$\triangleright$\,\allowbreak}}
%% Because html converters don't know tabularnewline
\providecommand{\tabularnewline}{\\}

%% Textclass specific LaTeX commands.
\newenvironment{lyxcode}
	{\par\begin{list}{}{
		\setlength{\rightmargin}{\leftmargin}
		\setlength{\listparindent}{0pt}% needed for AMS classes
		\raggedright
		\setlength{\itemsep}{0pt}
		\setlength{\parsep}{0pt}
		\normalfont\ttfamily}%
	 \item[]}
	{\end{list}}
\newenvironment{lyxlist}[1]
	{\begin{list}{}
		{\settowidth{\labelwidth}{#1}
		 \setlength{\leftmargin}{\labelwidth}
		 \addtolength{\leftmargin}{\labelsep}
		 \renewcommand{\makelabel}[1]{##1\hfil}}}
	{\end{list}}

%% User specified LaTeX commands.
\renewcommand{\printlandscape}{\special{landscape}}

% if slides come out in the viewer upside down, try:
%\sliderotation{right}

\makeatother

\begin{document}
\begin{slide}

\title{Slides and Notes with the \textsf{\noun{Seminar}} class}

\author{Günter Milde}

\date{2016/09/29}\maketitle
\end{slide}

\tableofcontents{}

\begin{slide}

\slideheading{Seminar}
\begin{itemize}
\item The \href{http://www.ctan.org/pkg/seminar}{seminar} class is designed
to produce overhead slides (transparencies). For PowerPoint-like presentations,
a document class like\textsf{ beamer} or\textsf{ powerdot} may be
better suited.
\item Insert a slide with a \textbf{LandscapeSlide} or \textbf{PortraitSlide}
inset (Insert\lyxarrow Custom~Insets).
\item Virtually everything that can appear in normal \LaTeX{} (except floats)
can also be on a slide.

Additional styles: \textsf{SlideHeading, SlideSubheading}
\item The seminar handbook \href{https://www.ctan.org/tex-archive/macros/latex/contrib/seminar/doc/seminar-doc.pdf}{sem-user.pdf}
is somewhat outdated but still a helpful reading.
\end{itemize}
\end{slide}

\begin{slide}

\slideheading{Warnings}
\begin{itemize}
\item \textsf{Seminar} uses \href{http://ctan.org/pkg/pgf}{PGF} graphic
specials: size and orientation of the slides show problems depending
on the output format and viewing application (see Troubleshooting
and the Appendix below).
\item Assure that the document page margins are set to default.
\end{itemize}
\end{slide}
\textsf{Seminar} puts everything that is not nested inside a \textsf{Slide}
environment on extra pages as \emph{notes.} (See Configuration below
on how to print only slides, only notes, or both.) 

\section{Configuration}

\begin{slide}

\slideheading{Output options\label{sli:output-options}}

The following options can be added to the \textsf{Class Options\lyxarrow Custom}
field in \textsf{Document\lyxarrow Settings\lyxarrow Document~Class}:
\begin{description}
\item [{notes}] Both notes and slides are printed (default).
\item [{slidesonly}] Only the slides are printed.
\item [{notesonly}] Only the notes are printed.
\item [{notesonly{*}}] Produces a slide marker for each slide environment.
\item [{portrait}] Portrait page orientation (default is landscape).

Fwd: Failures of seminar example file

[Kornel Benko]

Hi Herbert, we have problems with pstricks.sty after the last update of TL17.

'Correcting' texmf-dist/tex/generic/pstricks/pstricks.tex:34 to
\expandafter\ifx\csname @latexerr\endcsname\relax % do we have TeX? 
then @latexerr isn't defined
  \input pstricks-tex.def
\else
  \newif\ifpst@psfonts  \pst@psfontsfalse
\fi
cures the compilation for me. Would you like to take a look please?

Kornel

signature.asc
Description: This is a digitally signed message part.
--- Begin Message ---
Am Sonntag, 8. Oktober 2017 um 08:41:39, schrieb Guenter Milde 

> On 2017-10-08, Scott Kostyshak wrote:
> 
> > After at tlmgr update, I now get the following:
> 
> > $ ctest -R "seminar"
> 
> > I get "20 tests failed out of 33":
> 
> > 3631 - UNRELIABLE.WRONG_OUTPUT_export/examples/seminar_dvi (Failed)
> ...
> > 5025 - UNRELIABLE.WRONG_OUTPUT_export/examples/fr/seminar_pdf5_systemF 
> > (Failed)
> 
> > Before the tlmgr update, I did not have any failures. The tests are
> > marked as unreliable, so perhaps this change in behavior should not be a
> > surprise? I might not be so surprised if a few formats failed, but it
> > seems that all exports to PDF fail.
> 
> It seems that all exports using LaTeX fail (also DVI and Postscript).
> It would be interesting to see the reason (log) but I cannot reproduce with
> my Debian/stable texlive.

I see the same as Scott; Tested first with non-updated TL, everything pass.
Updated, now all 'seminar_[pd]' tests fail.

I see many messages in the log (creating pdf2)
Missing character: There is no 0 in font nullfont!
but also the following:
! Undefined control sequence.
l.2805 \ifpst@psfonts
 
The control sequence at the end of the top line
of your error message was never \def'ed. If you have
misspelled it (e.g., `\hobx'), type `I' and the correct
spelling (e.g., `I\hbox'). Otherwise just continue,
and I'll forget about whatever was undefined.

! Extra \else.
l.2807 \else

I'm ignoring this; it doesn't match any \if.

\everypsbox=\toks27
\psframesep=\dimen135
\pslabelsep=\dimen136
\sh@wgridXunit=\dimen137
\sh@wgridYunit=\dimen138
\pst@shift=\dimen139
)
! Extra \fi.

This line is in 
/usr/local/texlive/2017/texmf-dist/tex/generic/pstricks/pstricks.tex
The command \ifpst@psfonts is defined in pstricks/pricks-tex.def with comment 
that
it is defined in pstricks.sty, but there it is not defined.
Could not find the use or the definition of this command in TL16.

> I added a new clause in unreliable:varying-versions.
> 
> > Also, our entry in unreliableTests is:
> 
> > # seminar.sty uses Postscript specials or PGF
> > # -> wrong output with DVI and PDF (ps2pdf) (de-placed landscape
> > # slides).
> > export/examples/(|fr/)seminar_(dvi|pdf).*
> 
> > The comment makes me think that we only expect wrong output with DVI and
> > PDF (ps2pdf). Am I interpreting that wrong or should we remove the ".*"
> > at the end of that pattern?
> 
> The comment is imprecise. While DVI and ps2pdf are the export formats with
> most problems, no export format works reliably in all use cases.
> On the other hand, all export formats have use cases that work if the
> correct settings are used. 
>   The Appendix in examples/seminar.lyx lists details for on-screen viewing
> vs. printing of landscape slides, portrait slides, and notes.
> 
> I changed the comment but we may also just remove the clause from
> unreliable:wrong-output.
> 
> Günter

Kornel

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

Re: additional manual - link correction for elyxer

[Guenter Milde]

On 2017-10-08, Pavel Sanda wrote:
> Uwe Stöhr wrote:
>> Yes. Our HTML export is still not usable. I opened some bug reports:
>> http://www.lyx.org/trac/query?status=accepted=assigned=new=reopened=~html=~uwestoehr=id=summary=reporter=status=type=severity=keywords=reporter

> I see. So we will wait for a little more until elyxer chokes completely ;)

Why not fix the native HTML export *before* elyxer chokes completely?


Günter

Re: additional manual - link correction for elyxer

[Guenter Milde]

On 2017-10-07, Pavel Sanda wrote:
> Guenter Milde wrote:

>> I propose to use labels similar to what we have for PDF with current
>> LyXHTML either becoming just HTML or HTML (LyX):

>>   HTML, HTML (elyxer), [HTML (tth), ...]

> That's OK with me.

>> > And manuals should perhaps state that elyxer is outdated and can't cope
>> > with new lyx features.

>> Rather than that, the export configuration should be changed to use lyx2lyx
>> to export to the file format understood by elyxer.

> I'd say we should invest our energy to current html export instead of
> finding ways how to support converter which is dead for years.

The local fix is trivial, the relevant part of "~/.lyx/preferences" is:

#
# FORMATS SECTION ##
#

\format "html" "html, htm" "HTML (elyxer)" "H" "firefox" "" 
"document,menu=export" "text/html"
\format "xhtml" "xhtml" "XHTML" "y" "firefox" "" "document,menu=export" 
"application/xhtml+xml"

#
# CONVERTERS SECTION ##
#

\converter "lyx21x" "html" "elyxer --nofooter --directory $$r $$i $$o" ""
\converter "lyx" "html" "" ""

#

How can we get this as default entries with configure.py?

Thanks,
Günter

Re: Update on the 2.3.0rc1 situation

[Guenter Milde]

On 2017-10-07, Scott Kostyshak wrote:

> Any other important issues to consider before releasing rc1?

The current default behaviour for dash export is a regression on
changeset 798ad9755a1ff43a06d2b from 16.06.2007
  
  unicodesymbols: use commands for the dashes for consistency reasons and
  to avoid potential problems with some LaTeX-packages
  
We should either change the default value of 
Document->Settings->Fonts->Output em- and en-dash as ligatures
to "false" or document the change in the release notes (patch below).

I vote for changing the default.

Günter


diff --git a/lib/RELEASE-NOTES b/lib/RELEASE-NOTES
index c605cb4850..12699f07f0 100644
--- a/lib/RELEASE-NOTES
+++ b/lib/RELEASE-NOTES
@@ -212,10 +212,14 @@
   the external_templates file, you will have to move the modifications to
   the respective *.xtemplate file manually.
 
-* If you used literal em- and en-dashes in pre-2.2 documents,
-  you must manually unselect
-  "Document->Settings->Fonts->Output em- and en-dash as ligatures"
-  to ensure unchanged behaviour.
+* LyX 2.3 forces output of all en and em dashes as -- and --- when exporting
+  to LaTeX by default (exceptions are documents last saved with LyX 2.2 and
+  documents using non-TeX fonts). This can lead to incorrect line breaks,
+  wrong characters in typewriter fonts, and problems with
+  some LaTeX packages.
+  Unselect "Document->Settings->Fonts->Output em- and en-dash as ligatures"
+  to ensure unchanged behaviour. See chapter 3.9.1.1 "Dashes and line
+  breaks" of the User Guide for details.
 
 * ZWSP characters (u200b) following literal em- and en-dashes are deleted by
   lyx2lyx when converting to 2.3 format. If you used them as optional line

Re: [LyX/master] Add Qt-based fallback-converter for Mac to compensate missing ImageMagick convert utility

[Pavel Sanda]

Stephan Witt wrote:
> > Honestly I do not care about doxygen header.
> > I just meant if I bump into this code I would like to know what is it for
> > and how to use it, i.e. syntax for the output binary... Pavel
> 
> I did it. HTH.

Yes, thanks :) Pavel

Re: [LyX/master] Sort the language nesting mess with polyglossia

[Jean-Pierre Chrétien]

Le 09/10/2017 à 09:54, Guenter Milde a écrit :


The same as with babel vs. polyglossia: a wrong nesting tolerated in a
previous version but problematic in the new one. Could be tested on the
LaTeX source level...


As far as lettre.lyx is concerned, thats's what I'm planning to do.

--
Jean-Pierre

Re: Failures of seminar example file

[Guenter Milde]

On 2017-10-08, Kornel Benko wrote:
> Am Sonntag, 8. Oktober 2017 um 08:41:39, schrieb Guenter Milde 
> 
>> On 2017-10-08, Scott Kostyshak wrote:

>> > After at tlmgr update, I now get the following:

>> > $ ctest -R "seminar"

>> > I get "20 tests failed out of 33":

>> > 3631 - UNRELIABLE.WRONG_OUTPUT_export/examples/seminar_dvi (Failed)
>> ...
>> > 5025 - UNRELIABLE.WRONG_OUTPUT_export/examples/fr/seminar_pdf5_systemF 
>> > (Failed)

>> > Before the tlmgr update, I did not have any failures. The tests are
>> > marked as unreliable, so perhaps this change in behavior should not be a
>> > surprise? I might not be so surprised if a few formats failed, but it
>> > seems that all exports to PDF fail.

>> It seems that all exports using LaTeX fail (also DVI and Postscript).
>> It would be interesting to see the reason (log) but I cannot reproduce with
>> my Debian/stable texlive.

> I see the same as Scott; Tested first with non-updated TL, everything pass.
> Updated, now all 'seminar_[pd]' tests fail.

Thank you for testing.

> I see many messages in the log (creating pdf2)
>   Missing character: There is no 0 in font nullfont!

This is a false positive from the PNG package http://ctan.org/pkg/pgf.
We already added an exception to the LyX error reporting for it.

> but also the following:
> ! Undefined control sequence.
> l.2805 \ifpst@psfonts

...

> This line is in
> /usr/local/texlive/2017/texmf-dist/tex/generic/pstricks/pstricks.tex
> The command \ifpst@psfonts is defined in pstricks/pricks-tex.def with
> comment that it is defined in pstricks.sty, but there it is not
> defined. Could not find the use or the definition of this command in
> TL16.

So, it may be a bug in pstricks or an intended change that requires an
adaption in seminar.sty.

>> I added a new clause in unreliable:varying-versions.

Günter

Re: [LyX/master] Sort the language nesting mess with polyglossia

[Guenter Milde]

On 2017-10-08, Scott Kostyshak wrote:
> On Sun, Oct 08, 2017 at 08:59:47PM +, Jean-Pierre Chrétien wrote:
>> Le 08/10/2017 à 05:39, Scott Kostyshak a écrit :

>> > >  Sort the language nesting mess with polyglossia
>> > >  When using polyglossia, lyx was making a real mess when changing
>> > >  language inside nested insets. The \begin{language} and
>> > >  \end{language} commands were not well paired such that they could
>> > >  easily occur just before and after the start or end of an
>> > >  environment. Of course this was causing latex errors such that
>> > >  "\begin{otherlanguage} ended by \end{environment}".
>> > >  There may still be some cases I did not take into account.

If I remember right, the output for babel and polyglossia was the same but
babel is more tolerant towards mix up of nesting.

>> It seems that the Xetex error that I get with the lettre template is
>> of that kind. I was about to write to the class author about this, but
>> it seems thus that is is a LyX bug, right?

> I don't know. From what I remember lettre started failing for me after a
> TeX Live update. If it were a LyX bug, I wonder why it worked before.

The same as with babel vs. polyglossia: a wrong nesting tolerated in a
previous version but problematic in the new one. Could be tested on the
LaTeX source level...

Günter

Re: [LyX/master] Add Qt-based fallback-converter for Mac to compensate missing ImageMagick convert utility

[Stephan Witt]

Am 08.10.2017 um 20:56 schrieb Pavel Sanda :
> 
> Stephan Witt wrote:
>>> Would you mind to put here couple lines wit description and syntax? Thanks, 
>>> Pavel
>> 
>> I???ve changed it to match the style of all other c++ sources.
>> 
>> Did you have more in mind? If you did, please give me a hint
>> what doxygen keywords I should use??? thanks.
> 
> Honestly I do not care about doxygen header.
> I just meant if I bump into this code I would like to know what is it for
> and how to use it, i.e. syntax for the output binary... Pavel

I did it. HTH.

Stephan