Pavel Sanda wrote:
> I was already thinking about using item-like type, unfortunately there is
> often optional stuff between \begin{Leftside} and first \pstart, not just
> \beginnumbering.
You could define your own environment MyLeftside, which lets you enter such
optional stuff as an optional a
Jürgen Spitzmüller wrote:
> Pavel Sanda wrote:
> > When you typeset bilingual edition via (e)ledpar the structure is like this
> >
> > \begin{pages}
> >
> > \begin{Leftside}
> > \beginnumbering
> > \pstart paragraph1 \pend
> > \pstart paragraph2 \pend
> > \pstart paragraph3 \pend
> > ...
> > \end
On Thu, Jan 3, 2013 at 6:42 AM, Kornel Benko wrote:
> Am Donnerstag, 3. Januar 2013 um 11:47:22, schrieb Kornel Benko
>
>
>> BUT, as I see, you create "lyx2.1", but the "runtests.py" is using "lyx"
>> (hardcoded).
>
>> If you add a symbolic link lyx -> lyx2.1 in the bin-dir, it should work
>> for
On Thu, Jan 3, 2013 at 11:53 AM, Kornel Benko wrote:
> Am Donnerstag, 3. Januar 2013 um 13:11:48, schrieb Kornel Benko
>
>
>> Hi,
>
>> if we compile with program suffix, the at least on cmake build
>
>> tex2lyx2.1 is not able to find lyx2.1. Instead, it is searching for
>
>> "lyx2.1.1"
>
>>
>
>
>
On 01/02/2013 02:57 PM, Nico Williams wrote:
git push --tags theremote thebranch
Done, thanks.
rh
Jürgen Spitzmüller wrote:
> I don't know yet how to solve the \beginnumbering issue, but the \pstart
> ... \pend thing could be produced (kind of misusing the current means) by
> something like this:
Having said that, I think that (e)ledpar is so special that it strikes me a
major endeavor to im
Pavel Sanda wrote:
> When you typeset bilingual edition via (e)ledpar the structure is like this
>
> \begin{pages}
>
> \begin{Leftside}
> \beginnumbering
> \pstart paragraph1 \pend
> \pstart paragraph2 \pend
> \pstart paragraph3 \pend
> ...
> \endnumbering
> \end{Leftside}
This strikes me like a
On 01/02/2013 06:39 PM, Uwe Stöhr wrote:
Am 02.01.2013 15:45, schrieb Richard Heck:
Done. OK for branch too Richard?
Yes, OK.
Is branch frozen? If so, when will it be open again?
No, it is open and was never closed.
Btw. can you please commit the changes you made to the po-files
(remerg
Jürgen Spitzmüller wrote:
> Pavel Sanda wrote:
> > Layout experts, is there a way how to define environment so that
> > LaTeX output looks like:
> >
> > \awesomestart
> > paragraph text
> > \awesomeend
> >
> > (that is no "begin{" stuff, but my own "\strings" there) ?
>
> Don't think so. What is
Am Donnerstag, 3. Januar 2013 um 13:11:48, schrieb Kornel Benko
> Hi,
> if we compile with program suffix, the at least on cmake build
> tex2lyx2.1 is not able to find lyx2.1. Instead, it is searching for
> "lyx2.1.1"
>
The problem here is Package.cpp:348
abs_binary == "tex2lyx2.1" is a path whi
Pavel Sanda wrote:
> Layout experts, is there a way how to define environment so that
> LaTeX output looks like:
>
> \awesomestart
> paragraph text
> \awesomeend
>
> (that is no "begin{" stuff, but my own "\strings" there) ?
Don't think so. What is your usecase?
Jürgen
Julien Rioux wrote:
> On 03/01/2013 3:45 AM, Jürgen Spitzmüller wrote:
>> Julien Rioux wrote:
>>> In 2.0 if I define the simple layout
>>>
>>> InsetLayout "Flex:LatexParamTest"
>>> LatexType environment
>>> LatexName awesome
>>> LatexParam "[eh?]"
>>> LyXType custom
>>> End
Layout
Julien Rioux wrote:
> Patch for branch follows. OK?
I'm not the one to give green light, but the patch is good.
Jürgen
On 03/01/2013 3:45 AM, Jürgen Spitzmüller wrote:
Julien Rioux wrote:
In 2.0 if I define the simple layout
InsetLayout "Flex:LatexParamTest"
LatexType environment
LatexName awesome
LatexParam "[eh?]"
LyXType custom
End
The latex output from such an inset looks like:
\begin{awes
Julien Rioux wrote:
> ! LaTeX Error: Something's wrong--perhaps a missing \item.
>
> See the LaTeX manual or LaTeX Companion for explanation.
> Type H for immediate help.
You hit the beamer bug mentioned here:
http://tex.stackexchange.com/questions/38313/missing-item-in-article-mode-
using-aut
On 03/01/2013 8:37 AM, Jürgen Spitzmüller wrote:
Julien Rioux wrote:
No I don't. I did not realize that beamer.lyx was a child doc.
When compiling beamer-article.lyx the process finishes quickly, but I
get lots of "LaTeX Error:Something's wrong--perhaps a missing \item" and
no PDF.
[...]
LyX
Julien Rioux wrote:
> No I don't. I did not realize that beamer.lyx was a child doc.
> When compiling beamer-article.lyx the process finishes quickly, but I
> get lots of "LaTeX Error:Something's wrong--perhaps a missing \item" and
> no PDF.
[...]
> LyX eventually popped up a window with LaTeX
On 03/01/2013 4:48 AM, Jürgen Spitzmüller wrote:
Julien Rioux wrote:
I plan to add an optional Argument to the LilyPond flex inset. When I do
this, it does not get reverted to ERT for 2.0. Do I understand correctly
that I need to increase FORMAT and add lyx2lyx code each time we will do
such a l
On 03/01/2013 7:51 AM, Jürgen Spitzmüller wrote:
Julien Rioux wrote:
Thanks for the pointer to those discussions. I think the dialog is
great, but let me go back and explain better what I did and why I
think there is an issue here (and perhaps two). In trunk a.k.a git
master, I try to export the
Julien Rioux wrote:
> Thanks for the pointer to those discussions. I think the dialog is
> great, but let me go back and explain better what I did and why I
> think there is an issue here (and perhaps two). In trunk a.k.a git
> master, I try to export the examples/beamer.lyx file to PDF
> (pdflatex
On Thu, Jan 3, 2013 at 5:20 AM, Liviu Andronic wrote:
> On Thu, Jan 3, 2013 at 10:10 AM, Julien Rioux wrote:
>> I mean exactly this dialog: I click OK to stop the process, but the
>> View Button remains greyed out and the spinning wheel continues to
>> spin.
>>
> This dialogue is discussed in htt
Hi,
if we compile with program suffix, the at least on cmake build
tex2lyx2.1 is not able to find lyx2.1. Instead, it is searching for
"lyx2.1.1"
I could not find, where the relevant code is ...
#strace -o xx -f ...
...
#egrep xx
17932 stat("/usr/BUILD/Bui
Am Donnerstag, 3. Januar 2013 um 11:47:22, schrieb Kornel Benko
> BUT, as I see, you create "lyx2.1", but the "runtests.py" is using "lyx"
> (hardcoded).
> If you add a symbolic link lyx -> lyx2.1 in the bin-dir, it should work for
> now.
> Better would be to use the suffix of tex2lyx in runtest
Am Donnerstag, 3. Januar 2013 um 05:06:02, schrieb Scott Kostyshak
> On Thu, Jan 3, 2013 at 3:53 AM, Kornel Benko wrote:
> > Am Mittwoch, 2. Januar 2013 um 14:16:54, schrieb Scott Kostyshak
> >
> >
> > If you are using cmake, then you are not supposed to run run-tests.sh.
>
> Should "make" be
On Wed, Jan 2, 2013 at 4:25 PM, Richard Heck wrote:
>
> The source code for LyX 2.0.5.1 has been posted to ftp.lyx.org:
> ftp://ftp.lyx.org/pub/lyx/stable/2.0.x/
> Please let me have binaries as soon as you are able. I aim to announce
> within a few days.
>
Ubuntu binaries are available on the
On Thu, Jan 3, 2013 at 10:10 AM, Julien Rioux wrote:
> I mean exactly this dialog: I click OK to stop the process, but the
> View Button remains greyed out and the spinning wheel continues to
> spin.
>
This dialogue is discussed in http://www.lyx.org/trac/ticket/8032 .
Enrico fixed it and check sp
On Thu, Jan 3, 2013 at 3:53 AM, Kornel Benko wrote:
> Am Mittwoch, 2. Januar 2013 um 14:16:54, schrieb Scott Kostyshak
>
>
> If you are using cmake, then you are not supposed to run run-tests.sh.
Should "make" be disabled in the development/autotests directory then
when built with cmake?
All of
Julien Rioux wrote:
> I plan to add an optional Argument to the LilyPond flex inset. When I do
> this, it does not get reverted to ERT for 2.0. Do I understand correctly
> that I need to increase FORMAT and add lyx2lyx code each time we will do
> such a layout change?
Yes. However, there's lyx2
Julien Rioux wrote:
> I missed the commit that added this module.
http://www.lyx.org/trac/changeset/824b0313b/lyxgit
http://www.lyx.org/trac/changeset/fcb49729/lyxgit
> I think such module should
> be on the wiki only, while in our source tree we implement proper
> support.
How would "proper su
On 03/01/2013 3:36 AM, Jürgen Spitzmüller wrote:
Julien Rioux wrote:
In 2.1 if I define Arguments for my InsetLayout (great feature!) I note
that lyx2lyx backport from 2.1 to 2.0 converts
\begin_layout Argument 1
to
\begin_layout Argument
which isn't understood by 2.0 (maybe this conversion
Le 03/01/2013 01:07, Pavel Sanda a écrit :
I find this annoying too. Seems like some automated preference file should
have these new toolbars OFF by default, no? It would also be very nice to
be able to remove all IPA toolbars in one click instead of having to remove
half a dozen different ones o
On Sat, Dec 29, 2012 at 10:55 AM, Juergen Spitzmueller wrote:
> The branch, master, has been updated.
>
> - Log -
>
> commit d0b5728d2e4f6d33212639784b8ec3fa9d957ae4
> Author: Juergen Spitzmueller
> Date: Sat Dec 29 16:55:32 2012 +
On Thu, Jan 3, 2013 at 3:30 AM, Liviu Andronic wrote:
>
> On Thu, Jan 3, 2013 at 1:20 AM, Julien Rioux wrote:
> > Anyone else seeing this?
> >
> Yes. When some converter hangs LyX cannot know about this so becomes
> unresponsive compilation-wise. But I think that things are different
> in trunk,
Am Mittwoch, 2. Januar 2013 um 14:16:54, schrieb Scott Kostyshak
> I'm looking forward to making some tests for LyX but right now I can't
> run the tests.
>
> I'm on Ubuntu 12.04 64-bit using current master branch. I installed
> the following packages:
> wmctrl
> pcregrep
> xvkbd
This one will
Julien Rioux wrote:
> In 2.0 if I define the simple layout
>
> InsetLayout "Flex:LatexParamTest"
>LatexType environment
>LatexName awesome
>LatexParam "[eh?]"
>LyXType custom
> End
>
> The latex output from such an inset looks like:
>
> \begin{awesome}
> [eh?]content
> \end{aweso
On Thu, Jan 3, 2013 at 1:20 AM, Julien Rioux wrote:
> Anyone else seeing this?
>
Yes. When some converter hangs LyX cannot know about this so becomes
unresponsive compilation-wise. But I think that things are different
in trunk, where 3 minutes into the compilation a dialogue pops up
asking you to
Julien Rioux wrote:
> In 2.1 if I define Arguments for my InsetLayout (great feature!) I note
> that lyx2lyx backport from 2.1 to 2.0 converts
>
> \begin_layout Argument 1
>
> to
>
> \begin_layout Argument
>
> which isn't understood by 2.0 (maybe this conversion works for Style,
> which has s
On 03-Jan-13 1:45 AM, Uwe Stöhr wrote:
Am
02.01.2013 09:57, schrieb Zohar Levi:
The image itself is not a problem, but I
set the box mini page to be 207% column
width,
That is the reason why it is wi
38 matches
Mail list logo
