Pavel Sanda wrote:
> > Both commits are for branch too Juergen.
>
> Juergen?
OK.
Jürgen
rgheck wrote:
This is correct. The old cell is still there, and I think it may even
still have its old contents.
nope, it is cleared
Uwe Stöhr wrote:
I made progress with the multirow support, but there is one thing I
cannot figure out:
Where in the code are the cells merged when I e.g. select 2 cells and
press the multicolumn button? I a 2x2 table I have after this action
only 1 cell in the first row and 2 in the second o
Jean-Marc Lasgouttes schreef:
"Vincent van Ravesteijn - TNW" writes:
I tried to compare the Intro from trunk and branch
and got the following. Vincent?
Can you reproduce it ? I don't see it.
It comes from gcc vector-index checks, so you may not see it. What
happens is
On 01/15/2010 06:19 PM, Vincent van Ravesteijn wrote:
Uwe Stöhr schreef:
I made progress with the multirow support, but there is one thing I
cannot figure out:
Where in the code are the cells merged when I e.g. select 2 cells and
press the multicolumn button? I a 2x2 table I have after this a
Uwe Stöhr schreef:
I made progress with the multirow support, but there is one thing I
cannot figure out:
Where in the code are the cells merged when I e.g. select 2 cells and
press the multicolumn button? I a 2x2 table I have after this action
only 1 cell in the first row and 2 in the second
Pavel Sanda schreef:
Pavel Sanda wrote:
- Are there other missing features that you are working on and that you
want to have in LyX 1.7 before a beta release?
revision info under VCS is still in plan (fileformat change). but not
necessarily before beta, shouldn't be big change...
Jan Sykora wrote:
> What kind of debugging shall I do (debug option + some filtering)? It is
> very annoying - I've been using lyx since for many years (>10) (mostly on
> linux) and my recent jump on mac version is a bit frustrating
this just reflect the fact that we miss developers on mac.
Richard Heck wrote:
> We're about ready for this.
congratz! just tried with file i'm currently editing and except TBA title
output seems to be already nicer than latex2html. cool stuff.
pavel
I made progress with the multirow support, but there is one thing I
cannot figure out:
Where in the code are the cells merged when I e.g. select 2 cells and
press the multicolumn button? I a 2x2 table I have after this action
only 1 cell in the first row and 2 in the second one. I'm looking fo
Pavel Sanda wrote:
> > - Are there other missing features that you are working on and that you
> > want to have in LyX 1.7 before a beta release?
>
> revision info under VCS is still in plan (fileformat change). but not
> necessarily before beta, shouldn't be big change...
oops i forgot - instan
On Friday 15 January 2010 16:54:15 Jean-Marc Lasgouttes wrote:
> José Matos writes:
> > Any other opinions suggestions?
>
> I guess the question is what we need before alpha 1. One thing I would
> like to see (at least before real release) is a ui2ui/bind2bind/rc2rc
> infrastructure. If some
José Matos wrote:
> Any other opinions suggestions?
- please do some definitive decision about version number now.
i have asked about the opinions few days ago, whoever has something
to say got his chance. the result was 2:1 for 1.7 so you have the
royal choice :)
- i miss some gener
Rob Oakes wrote:
> need to change the current position in the text. After looking at the
> TocModel classes, I realized that it is going to require the addition of
i can just repeat - make small steps, otherwise the work will stall. starting
with having "only" drag&drop in outliner would be big s
sa...@lyx.org wrote:
> Author: sanda
> Date: Thu Jan 14 02:06:21 2010
> New Revision: 33023
> URL: http://www.lyx.org/trac/changeset/33023
>
> Log:
> It seems that svn changes its implicit behaviour across versions.
>
> Both commits are for branch too Juergen.
Juergen?
>
> Modified:
>lyx-
Tommaso Cucinotta wrote:
> - how does the release process work ? are you going to create a new branch
> on the repo, etc... ?
you may be interested to read http://www.lyx.org/VersioningSystem where we have
tried
to sum up our view of prerelases. basically - you will work in trunk until
final 1.
It seems that I've found the solution - the "backup original document
when saving" option must be switched off. Then it is OK even with NFS
mounted home. There must be a bug in the procedure of renaming the orig.
file when this is on NFS+being deep into the directory hierarchy.
prof. Jan Syk
.. additional observation: everything is OK (including editing, latex
compilation...) _until_ the first "save lyx-file" command. Then the
problem of kbd stealing appears.
prof. Jan Sykora
Jan Sykora wrote:
.. another observation:
the behavior depends on the (probably) full path name length,
.. another observation:
the behavior depends on the (probably) full path name length, or
dir-names used on the NFS home (case sensitive/linux server).
when the lyx file is deeply nested into the nfs directory hierarchy -
the lyx fails (steals the kbd)
when I move the lyx file almost on the
José Matos writes:
> Any other opinions suggestions?
I guess the question is what we need before alpha 1. One thing I would
like to see (at least before real release) is a ui2ui/bind2bind/rc2rc
infrastructure. If some nice python hacker (hint!) were to provide the
functionality, we could do
"Vincent van Ravesteijn - TNW" writes:
>
>>I tried to compare the Intro from trunk and branch
>>and got the following. Vincent?
>
> Can you reproduce it ? I don't see it.
It comes from gcc vector-index checks, so you may not see it. What
happens is that forwardPos can put you at the end of a
>I tried to compare the Intro from trunk and branch
>and got the following. Vincent?
Can you reproduce it ? I don't see it.
Are these by accident the same docs ? (The assertion is already there
before the algorithm is even started).
Maybe I should change "to.backwardPos()" to "step(to, Backwa
Hi all,
trying to synthesize the different threads we had this week it seems
that
there is a consensus that we are ready (^H late) to release the first alpha.
As it is usual with the alpha stage this means that lyx builds (and
hopefully works) on our support platforms. Those pla
Yes, it makes problems even when kbd maps are completely switched off.
But only some documents cause the problem (long, complicated). I have
one document which deterministically causes the problem (lyx steals the
keyboard focus) when on NFS mounted home. When it is on local volume, it
is OK.
Guenter Milde wrote:
> But definitely here with LMRoman10-Regular.
Not here.
> What fonts do you use?
I tested with default (LMRoman-10), MinionPro, Garamond and Times New Roman.
Jürgen
On 2010-01-15, Jürgen Spitzmüller wrote:
> Guenter Milde wrote:
>> Another, more relevant example is XeTeX: If (like in the default LyX-svn
>> setup) system fonts are used, --- is rendered as three hyphens.
> Not here.
But definitely here with LMRoman10-Regular.
What fonts do you use?
> Jürgen
Jean-Marc Lasgouttes writes:
> I tried to compare the Intro from trunk and branch and got the
> following. Vincent?
> #4 0x083323a2 in lyx::Paragraph::getChar (this=0x9765780, pos=19)
> at ../../lyx-devel/src/Paragraph.cpp:3003
> #5 0x080bd00e in traverseSnake (p...@0xb6181f04, range=,
>
I tried to compare the Intro from trunk and branch and got the
following. Vincent?
JMarc
/usr/lib/gcc/i586-mandriva-linux-gnu/4.1.2/../../../../include/c++/4.1.2/bits/basic_string.h:709:
typename _Alloc::rebind<_CharT>::other::reference std::basic_string::operator[](typename _Alloc::rebind<_Cha
Jean-Marc Lasgouttes wrote:
> I think we should continue to pass --- unchanged.
+1
Jürgen
rgheck writes:
>> a) What to use in the tutorial, --- or em-dash?
>>
> ---, on the ground that em-dash as currently handled breaks lines
> wrong. One could change the handling of em-dash, but I see no
> generally acceptable way to do it, though see below.
+1
>> b) How to export the em-dash Unico
On 01/15/2010 05:24 AM, Guenter Milde wrote:
In my view, the issues are:
So, just to be clear what my views are:
a) What to use in the tutorial, --- or em-dash?
---, on the ground that em-dash as currently handled breaks lines wrong.
One could change the handling of em-dash, but I
On 01/15/2010 08:02 AM, Steve Litt wrote:
On Friday 15 January 2010 07:34:02 Philiрp Rеichmuth wrote:
Am Fri, 15 Jan 2010 10:28:10 + (UTC) schrieb Guenter Milde:
If ever we want to switch to a XML like math format, it should use
Unicode where available. For an incremental transiti
On Friday 15 January 2010 07:34:02 Philiрp Rеichmuth wrote:
> Am Fri, 15 Jan 2010 10:28:10 + (UTC) schrieb Guenter Milde:
> > If ever we want to switch to a XML like math format, it should use
> > Unicode where available. For an incremental transition, we could use
> > Unicode chars in LaTeX fo
Am Fri, 15 Jan 2010 10:28:10 + (UTC) schrieb Guenter Milde:
> If ever we want to switch to a XML like math format, it should use
> Unicode where available. For an incremental transition, we could use
> Unicode chars in LaTeX format right now.
I think this is a fundamentally bad idea. I use LyX
> - will Advanced F&R be in for this new release ? (I hope so)
Without a doubt. That's why we were slightly urging you to round up the loose
ends.
>- how does the release process work ? are you going to create
>a new branch on the repo, etc... ?
No trunk = new release.
Afterwards a new branch
Guenter Milde wrote:
> Another, more relevant example is XeTeX: If (like in the default LyX-svn
> setup) system fonts are used, --- is rendered as three hyphens.
Not here.
Jürgen
On 2010-01-14, Pavel Sanda wrote:
> Guenter Milde wrote:
>> On 2010-01-13, Pavel Sanda wrote:
>> > Vincent van Ravesteijn - TNW wrote:
>> >> >doesn't work because of different preambles and different
>> >> >needs of manuals.
>> >> >
>> >> Which I still don't understand.
>> > http://www.lyx.org/t
On 2010-01-14, rgheck wrote:
> On 01/14/2010 05:28 PM, Guenter Milde wrote:
>> On 2010-01-14, rgheck wrote:
>>> On 01/14/2010 03:05 AM, Guenter Milde wrote:
>> I propose to use Unicode chars in the LyX file (so that if your write
>> \hbar, the math editor would not only show ℏ in the GUI but also
On 2010-01-15, rgheck wrote:
> Before we have any more of this discussion, let me just emphasize that
> my original concern was with the use of the Unicode emdash in the User's
> Guide and Tutorial, where it gives bad results, according to the
> standards of English typography. That is what I
Uwe Stöhr wrote:
- Are there other missing features that you are working on and that
you want to have in LyX 1.7 before a beta release?
Two questions:
- will Advanced F&R be in for this new release ? (I hope so)
- how does the release process work ? are you going to create a new
branch on the r
Jürgen Spitzmüller wrote:
> I don't know how to get it sorted alphabetically in the list, though.
Erm, it's rather my own sorting algorithm that needs fixing :-/
Jürgen
rgheck wrote:
> Can someone add an XHTML "component" to the trac bug thingy and make me
> owner? We're about ready for this.
Done. I don't know how to get it sorted alphabetically in the list, though.
Jürgen
42 matches
Mail list logo