Bo Peng wrote:
> On 6/26/07, José Matos <[EMAIL PROTECTED]> wrote:
>> Hi all,
>> as discussed in this list I would like to release rc2 today.
>>
>> The only thing that needs to be done now is to commit
>> configure.ac. I have
>> all other the changes committed.
>>
>
> OK. I have
On Tuesday 26 June 2007 19:08:56 Edwin Leuven wrote:
> i thought you established the consensus by your coin toss?
So that just means that I will toss the coin again, what is the problem? ;-)
--
José Abílio
José Matos wrote:
On Tuesday 26 June 2007 19:08:56 Edwin Leuven wrote:
i thought you established the consensus by your coin toss?
So that just means that I will toss the coin again, what is the problem? ;-)
none really, i just thought i noticed some inconsistency between this
mail and a
Asger Ottar Alstrup wrote:
instead? If you don't like the word Built-in, then please make it
Default Alignment for Current Paragraph (Justified)
to make it *extra* clear what default we are talking about. There is
room enough, according to the screen shot.
or even more verbose:
"Use
José Matos wrote:
> Hi all,
> as discussed in this list I would like to release rc2 today.
>
> The only thing that needs to be done now is to commit configure.ac. I
> have
> all other the changes committed.
>
> In normal conditions I will release rc2 in less than 3 hours I am
On Tue, Jun 26, 2007 at 04:46:39PM +0100, José Matos wrote:
> AFAIR one proposed solution implied the use of boost support for threads.
> This would hide the platform specific details.
Do boost threads work nowadays on Windows?
I was under the impression that they use pthreads there, which
Peter Kümmel wrote:
> Bo Peng wrote:
>> On 6/26/07, José Matos <[EMAIL PROTECTED]> wrote:
>>> Hi all,
>>> as discussed in this list I would like to release rc2 today.
>>>
>>> The only thing that needs to be done now is to commit
>>> configure.ac. I have
>>> all other the changes
On 6/26/07, Peter Kümmel <[EMAIL PROTECTED]> wrote:
Peter Kümmel wrote:
> Bo Peng wrote:
>> On 6/26/07, José Matos <[EMAIL PROTECTED]> wrote:
>>> Hi all,
>>> as discussed in this list I would like to release rc2 today.
>>>
>>> The only thing that needs to be done now is to commit
Andre Poenitz wrote:
> On Tue, Jun 26, 2007 at 04:46:39PM +0100, José Matos wrote:
>> AFAIR one proposed solution implied the use of boost support for threads.
>> This would hide the platform specific details.
>
> Do boost threads work nowadays on Windows?
Yes, also on Windows CE ;)
>
> I
On Tue, Jun 26, 2007 at 08:38:01PM +0200, Edwin Leuven wrote:
> José Matos wrote:
> >On Tuesday 26 June 2007 19:08:56 Edwin Leuven wrote:
> >>i thought you established the consensus by your coin toss?
> >
> >So that just means that I will toss the coin again, what is the problem?
> >;-)
>
> none
According to http://www.netbsd.org/about/roadmap.html, this is also
true for NetBSD, so I would also add "&& !defined(__NetBSD__)" there.
Are you sure about the name here? Not __NETBSD__?
Bo
Bo Peng wrote:
>> According to http://www.netbsd.org/about/roadmap.html, this is also
>> true for NetBSD, so I would also add "&& !defined(__NetBSD__)" there.
>
> Are you sure about the name here? Not __NETBSD__?
>
> Bo
>
Seems he is right:
http://predef.sourceforge.net/preos.html#sec23
And
Peter Kümmel wrote:
> Bo Peng wrote:
>>> According to http://www.netbsd.org/about/roadmap.html, this is also
>>> true for NetBSD, so I would also add "&& !defined(__NetBSD__)" there.
>> Are you sure about the name here? Not __NETBSD__?
>>
>> Bo
>>
>
> Seems he is right:
>
> Are you sure about the name here? Not __NETBSD__?
>
When I google, I see a lot of
defined (__FreeBSD__) || defined (__OpenBSD__) || defined(__OpenBSD__)
so I guess we should use these forms. Also, has anyone checked open bsd?
Bo
On 6/26/07, Bo Peng <[EMAIL PROTECTED]> wrote:
> > Are you sure about the name here? Not __NETBSD__?
> >
When I google, I see a lot of
defined (__FreeBSD__) || defined (__OpenBSD__) || defined(__OpenBSD__)
Of course I meant FreeBSD, OpenBSD and NetBSD.
Bo
Stefan Schimanski wrote:
+// If the last logical character is a separator, skip it, unless
+// it's in the last row of a paragraph
+if (end > 0 && end < par.size() && par.isSeparator(end - 1))
+skipped_sep_vpos = bidi.log2vis(end - 1);
I thought it's about the visually last
Martin Vermeer wrote:
On Mon, Jun 25, 2007 at 11:17:15PM +0300, Dov Feldstern wrote:
Dov Feldstern wrote:
Hi!
Here's another RTL regression --- I think this should be really easy to
solve for anyone familiar with the painting code. I'd be happy to try
and help out if necessary.
Enrico Forestieri schrieb:
On Wed, Jun 20, 2007 at 09:44:12AM +0100, José Matos wrote:
On Wednesday 20 June 2007 00:00:06 Enrico Forestieri wrote:
The attached patch fixes it. José, OK to commit?
The patch seems right. If you someone to test this and guarantee that it
works
[EMAIL PROTECTED] schrieb:
Author: spitz
Date: Mon Jun 25 15:49:51 2007
New Revision: 18885
URL: http://www.lyx.org/trac/changeset/18885
Log:
Fix bug 1749. CAUTION: lyx2lyx not fully working yet (see FIXMEs).
José, isn't lyx2lyx your hobby-horse :-)
Michael
Le 26 juin 07 à 17:55, Abdelrazak Younes a écrit :
José Matos wrote:
On Tuesday 26 June 2007 16:15:32 Richard Heck wrote:
May I file an enhancement at bugzilla? (I didn't find any
dealing with
this)
Of course.
This subject has been discussed here before I would be surprised
if this is
José,
(when) should we update all LyX files to the latest file format?
Michael
Uwe Stöhr wrote:
Dov Feldstern schrieb:
Thanks for taking care of the lyx2lyx stuff! I added the requisite
comment to the FORMAT file --- could you just check your name (I'm not
sure my accents are correct) and email?
The name is fine there.
Btw. Why do you have a [EMAIL PROTECTED] email
> "Peter" == Peter Kümmel <[EMAIL PROTECTED]> writes:
Peter> Here a updated patch with the scons changes. Should I apply? Or
Peter> comes JMarc back before RC2?
I was waiting for a confirmation that the patch works for FreeBSD...
Now I guess LyX will not configure itself correctly with
> "Peter" == Peter Kümmel <[EMAIL PROTECTED]> writes:
Peter> Is it correct that this line remains untouched?
Peter> #if SIZEOF_WCHAR_T != 4 && defined(__GNUC__) &&
Peter> defined(__GNUC_MINOR__) && __GNUC__ == 3 && __GNUC_MINOR__ < 4
No, and I do not know how I missed it. I think it should
Am 26.06.2007 um 21:25 schrieb Dov Feldstern:
Stefan Schimanski wrote:
+// If the last logical character is a separator, skip it,
unless
+// it's in the last row of a paragraph
+if (end > 0 && end < par.size() && par.isSeparator(end - 1))
+skipped_sep_vpos =
> "Jürgen" == Jürgen Spitzmüller <[EMAIL PROTECTED]> writes:
Jürgen> José Matos wrote:
>> Yes.
Jürgen> Thanks. I'm done with my patches now (I wait witth the one for
Jürgen> bug 3915 unless Jean-Marc and I have come to a conclusion).
I think the latest patch is better than what we had
Stefan Schimanski wrote:
Ok, after rereading your previous mail I got it. Would be good to put a
better documentation there like:
// Spaces at line breaks in bidi text can appear visually in the middle
// of a row and must be skipped during painting:
// * logically "abc_[HEBREW_\nHEBREW]"
//
Edwin Leuven wrote:
Asger Ottar Alstrup wrote:
instead? If you don't like the word Built-in, then please make it
Default Alignment for Current Paragraph (Justified)
to make it *extra* clear what default we are talking about. There is
room enough, according to the screen shot.
or even
An update to the previous patch, incorporating a check for a
multi-paragraph selection. I'll commit after rc2, if there is no
objection. I go away Thursday morning on vacation, though, so if rc2 is
not out by then, someone else will have to do it for me
Richard
The attached patch
An update to the previous patch, incorporating a check for a
multi-paragraph selection. I'll commit after rc2, if there is no
objection. I go away Thursday morning on vacation, though, so if rc2 is
not out by then, someone else will have to do it for me
Richard
The attached patch
On Tue, Jun 26, 2007 at 02:19:47PM -0500, Bo Peng wrote:
> On 6/26/07, Bo Peng <[EMAIL PROTECTED]> wrote:
> > > > Are you sure about the name here? Not __NETBSD__?
> > > >
> >
> > When I google, I see a lot of
> >
> > defined (__FreeBSD__) || defined (__OpenBSD__) || defined(__OpenBSD__)
>
> Of
On Tue, Jun 26, 2007 at 09:38:44PM +0200, Michael Gerz wrote:
> Enrico Forestieri schrieb:
> > On Wed, Jun 20, 2007 at 09:44:12AM +0100, José Matos wrote:
> >
> >> On Wednesday 20 June 2007 00:00:06 Enrico Forestieri wrote:
> >>
> >>> The attached patch fixes it. José, OK to commit?
>
On Tue, 2007-06-26 at 17:01 +0200, Mael Hilléreau wrote:
> I have a feature request: Would it be possible to perform output
> generation in a different thread so that LyX wouldn't freeze while
> compiling? This would be particularly appreciated with big documents
> which take a long time to
Hi all,
I just imported a Word document and am now cleaning it up.
I found a curiosity for you: after a subsection heading, there was a
blank line before the next paragraph. I only noticed it because of the
wrong indenting of the next paragraph.
I can't create such a blank line so it's
Hi all,
I just added a fresh BibTeX database to a document and found the file
selection dialogue to be utterly baffling.
Is it meant to be like that??
Have fun,
Darren
Richard Heck wrote:
> > "Use this paragraph's default alignment (Justified)"
>
> That's fine with me, though I'd suggest "the" instead of "this", as that
> is OK for the multi-paragraph case, too.
Oh no, please don't. Use tooltips for verbose hints (you can't imagine how
long this label will be
User guide section 5.7.2 Math Text Mode.
Footnote reads: "Moreover, math text mode outputs its contents inside a
\textrm{}, whereas and \mbox (or AMS-LaTeX's \text) might have been a
better choice"
This is wrong because LyX now uses \mbox{}.
Have fun,
Darren
On Mon, 2007-05-21 at 17:21 +0200, Jean-Marc Lasgouttes wrote:
> > "Darren" == Darren Freeman <[EMAIL PROTECTED]> writes:
>
> Darren> On Mon, 2007-05-21 at 16:16 +0200, Herbert Voss wrote:
> >> {Ge}^3 is different to
> >>
> >> Ge^3 and G^3 and e^3, which have all the same vertical height.
>
201 - 238 of 238 matches
Mail list logo
