headers
Gregor Gorjanc | 1 Dec 2006 01:48
Picon
Gravatar

Re: Wish: add newline after \begin{centering} and before \end{centering}

Herbert Voss <hvoss <at> ...> writes:
> > That is the output if I center scrap (modified to allow that) environment:
> > 
> > \begin{figure}
> > \begin{centering}<<fig=true>>=
> > boxplot(Sepal.Length~Species,data=iris)
> >  <at> \par\end{centering}
> > 
> > 
> > \caption{bla bla}
> > \end{figure}
> 
> stupid code ...

Why?

> I suppose you do not know the difference between centering and center

You are right, I do not know the diff. Can anyone enlight me please?

Thanks, Gregor
Permalink | Reply | 28 comments |
headers
Gregor Gorjanc | 1 Dec 2006 01:55
Picon
Gravatar

Optional LatexParam in layouts

Hello!

When writing layout files we can use LatexParam directive to provide additional
options that might be used in environments. My env with options looks like 

\begin{Scode}{echo=true, eval=false, ...}
\end{Scode}

where ... means other options. How can I define this with LatexParam directive?
Is it possible to modfy this values later when a user is writting a file with
this environment?

Thanks, Gregor
Permalink | Reply | 9 comments |
headers
Enrico Forestieri | 1 Dec 2006 02:59
Picon

Re: Some math symbols are not shown

On Sat, Nov 18, 2006 at 12:38:58PM +0100, Georg Baum wrote:
> Am Freitag, 17. November 2006 20:57 schrieb Enrico Forestieri:
> > I noticed that some math symbols are not shown on screen. This seems
> > to be platform dependent. The following is a table illustrating the
> > situation on three different platforms. Here "no" means that the
> > symbol is not shown on screen (the symbol is invisible but occupies
> > space: it is as a sort of \phantom), and "yes" that it is shown.
> > 
> > ---------------------------------------
> > Symbol         Linux   Solaris   Cygwin
> > ---------------------------------------
> > \Omega          no       no        no
> > \int            yes      yes       no
> > \oint           yes      yes       no
> > \otimes         no       no        no
> > \nleqslant      no       no        no
> > \spadesuit(*)   yes      no        yes
> > ---------------------------------------
> > (*) On solaris, a square is shown on screen instead of nothing.
> 
> Interesting. I can confirm that for \Omega (did not try the others). This 
> is exactly what I got when I tried to create a true type version of the 
> esint10 font, and I suspect that the reason is the same. \Omega works fine 
> in 1.4.3.
> I debugged this as far that I am pretty sure that qt is to blame here. I 
> added an entry to the status file.

I investigated why \int and \oint are not shown on Windows, contrarily
to *nix. It turned out that the following check performed in
GuiFontLoader.C:
(Continue reading)

Permalink | Reply | 11 comments |
headers
Bennett Helm | 1 Dec 2006 04:14

Re: Quit cleanup

On Nov 30, 2006, at 6:34 PM, Peter Kümmel wrote:

> In the last patch is a bug for Mac.
> Here the corrected.

I'm not sure what this was supposed to fix, but I'm not seeing any  
difference in behavior after applying the patch. Thus:

* session info still isn't saved
* starting LyX, creating a new document, typing a few characters, and  
quitting still exits without asking whether or not to save

In both cases, gdb indicates that "Program exited normally."

I assume the patch was supposed to address the first of these,  
right? ... Am I missing something?

Bennett
Permalink | Reply | 1 comment |
headers
Michael Gerz | 1 Dec 2006 09:11

Re: Assertion violated in filename.C:44

Georg Baum schrieb:
> Can you please produce a backtrace and the value of name_ that makes the
> assertion fail? Without that I don't know how to find the problem.
>   

In buffer::save(),  removeAutosaveFile() is invoked with a Windows (i.e. 
non-POSIX) absolute file name.However, onlyPath() which is called from 
removeAutosaveFile() can only handle "/" (not "\").

I guess it is not onlyPath() to blame. I guess some external filename 
isn't converted properly into an internal filename, right?

Michael

PS: This bug is fundamental on Windows and proves that nobody is 
actually using LyX 1.5.0svn on Windows :-(
Permalink | Reply | 1 comment |
headers
Jean-Marc Lasgouttes | 1 Dec 2006 09:27
Favicon

Re: Wish: add newline after \begin{centering} and before \end{centering}

>>>>> "Gregor" == Gregor Gorjanc <gregor.gorjanc@...> writes:

Gregor> Herbert Voss <hvoss <at> ...> writes:
>> > That is the output if I center scrap (modified to allow that)
>> environment:
>> > 
>> > \begin{figure} > \begin{centering}<<fig=true>>= >
>> boxplot(Sepal.Length~Species,data=iris) > <at> \par\end{centering}
>> > 
>> > 
>> > \caption{bla bla} > \end{figure}
>> 
>> stupid code ...
>> I suppose you do not know the difference between centering and
>> center

First, I want to point out that this is the code output by LyX, not
Gregor's doing. And I do not think that his particular problem is
about center vs centering.

Gregor> You are right, I do not know the diff. Can anyone enlight me
Gregor> please?

I guess Herbert is balking at the use of centering as an environment.
In my view, using 
  \begin{centering}...\end{centering}
is equivalent to the more traditional
  {\centering ...}
except that at least the first one is a proper markup. I agree
nevertheless that I never saw this documented anywhere and I have to
(Continue reading)

Permalink | Reply | 27 comments |
headers
Jean-Marc Lasgouttes | 1 Dec 2006 09:30
Favicon

Re: Optional LatexParam in layouts

>>>>> "Gregor" == Gregor Gorjanc <gregor.gorjanc@...> writes:

Gregor> Hello! When writing layout files we can use LatexParam
Gregor> directive to provide additional options that might be used in
Gregor> environments. My env with options looks like

Gregor> \begin{Scode}{echo=true, eval=false, ...} \end{Scode}

Gregor> where ... means other options. How can I define this with
Gregor> LatexParam directive? Is it possible to modfy this values
Gregor> later when a user is writting a file with this environment?

We do not have for now a way to create environments with options that
can be set by the user. It is possible though in 1.5 to make
environments with optional arguments like
\begin{foo}[argument]
...
\end{foo}

JMarc
Permalink | Reply | 7 comments |
headers
Georg Baum | 1 Dec 2006 09:39
Picon
Picon

Re: Assertion violated in filename.C:44

Michael Gerz wrote:

> In buffer::save(),  removeAutosaveFile() is invoked with a Windows (i.e.
> non-POSIX) absolute file name.However, onlyPath() which is called from
> removeAutosaveFile() can only handle "/" (not "\").
> 
> I guess it is not onlyPath() to blame. I guess some external filename
> isn't converted properly into an internal filename, right?

Exactly. All LyX filename handling assumes paths with /, not \, so all
filenames coming from external sources (command line, config files, file
dialog) need to be converted to internal paths.
With the attached patch it should be easy to find out where this comes from.

Georg
Attachment (x.diff): text/x-diff, 515 bytes
Permalink | Reply | 0 comments |
headers
Max Hoffmann | 1 Dec 2006 09:43
Picon

Re: Optional LatexParam in layouts

Hi!

On Fr, 2006-12-01 at 00:55 +0000, Gregor Gorjanc wrote:
> where ... means other options. How can I define this with LatexParam directive?
> Is it possible to modfy this values later when a user is writting a file with
> this environment?

I would like to add to Gregor's request: After having read in the
customization.lyx I don't see how one can write a layout file for an
environment with one additional (obligatory) argument. I am trying to
get the flashcards.cls to work with LyX smoothly.

The flashcards class, written by Alexander M. Budge, expects entries of
the following form:

\begin{flashcard}{whats on  the front}
whats on 
the back
\end{flashcard}  

but front and back are entered by the user. Is this at all possible in
LyX or planned in near future?

Or do I have to rewrite  the flashcards.cls? I saw that e.g. amsart
environments like "defn" take the first paragraph as the head and the
others as body. Can someone point me in the direction of how to
implement this in LaTeX2e? I am pretty new to both, layout file and
LaTeX2e classes.

Best regards,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Georg Baum | 1 Dec 2006 10:17
Picon
Picon

Re: Some math symbols are not shown

Enrico Forestieri wrote:

> I investigated why \int and \oint are not shown on Windows, contrarily
> to *nix. It turned out that the following check performed in
> GuiFontLoader.C:
> 
> bool isChosenFont(QFont & font, string const & family)
> {
>         ...
>         // So we check rawName first
>         if (contains(fromqstr(font.rawName()), family)) {
>                 lyxerr[Debug::FONT] << " got it ";
>                 return true;
>         }
>         ...
> 
> always succeeds on windows, whatever font is asked for, existing or not.

This is documented for QFont::setRawName:

If Qt's internal font database cannot resolve the raw name, the font becomes
a raw font with name as its family.

I guess that this applies also if you request a font by other means that
setRawName().

> In this way, LyX thinks that the esint font is existing on the system,
> thus the "iffont esint" test in lib/symbols succeeds, and the integral
> sign glyphs are assigned to a missing font file...
>
(Continue reading)

Permalink | Reply | 7 comments |

Gmane