Am Montag, 24. April 2017 um 17:13:23, schrieb Pavel Sanda
> Kornel Benko wrote:
> > Am Samstag, 15. April 2017 um 22:21:04, schrieb Richard Heck
> >
> > > On 04/15/2017 02:06 PM, Uwe Stöhr wrote:
> > > > Hi Richard,
> > > >
> > > > the attached patch fixes 2 lyx2lyx issues in the box reversion
Kornel Benko wrote:
> Am Samstag, 15. April 2017 um 22:21:04, schrieb Richard Heck
> > On 04/15/2017 02:06 PM, Uwe Stöhr wrote:
> > > Hi Richard,
> > >
> > > the attached patch fixes 2 lyx2lyx issues in the box reversion
> > > routines. Could this please go in for LyX 2.2.3?
> >
> > OK.
> >
> >
El 24.04.2017 a las 17:31, Richard Heck escribió:
OK.
It is in.
regards Uwe
t;
> this patch fixed some issues but Math.lyx uncovered an issue that I
> introduced with this patch.
> Attached is the patch for LyX 2.2.3 that allows to revert Math.lyx again.
>
> sorry and regards
> Uwe
patch.
Attached is the patch for LyX 2.2.3 that allows to revert Math.lyx again.
sorry and regards
Uwe
diff --git
"a/C:\\Users\\Usti\\AppData\\Local\\Temp\\TortoiseGit\\lyx_2_2-cac7b00.001.py"
"b/D:\\LyXGit\\2.2.x\\lib\\lyx2lyx\\lyx_2_2.py"
index c30477de17..a65f8ca67d 1006
El 17.04.2017 a las 21:57, Richard Heck escribió:
I will look these over and commit them if they're acceptable.
Attached are the obvious "\\" fixes that should be backported.
regards
Uwe
diff --git
"a/C:\\Users\\Usti\\AppData\\Local\\Temp\\TortoiseGit\\lyx_2_0-0271602.002.py"
"b/D:\\LyXGit\
On Mon, Apr 17, 2017 at 05:30:19AM +0200, Uwe Stöhr wrote:
> Hi Richard,
>
> the attached patch fixes several box reversion issues in lyx2lyx. Scott
> could verify that the conversion to LyX 2.1.x works now as expected.
Just to be clear: when I report results of ctests, it is important to
underst
El 17.04.2017 a las 21:57, Richard Heck escribió:
OK.
it is in.
I will look these over and commit them if they're acceptable.
thanks.
regards Uwe
On 04/17/2017 03:30 PM, Uwe Stöhr wrote:
> El 17.04.2017 a las 17:22, Richard Heck escribió:
>
>> OK.
>
> It is in.
>
> Attached is another fix fixing the box reversion from 2.0 to 1.6.
> Kornel verified that it works for him too OK to go in?
OK.
>> You can use git blame to identify where the cha
El 17.04.2017 a las 17:22, Richard Heck escribió:
OK.
It is in.
Attached is another fix fixing the box reversion from 2.0 to 1.6. Kornel
verified that it works for him too OK to go in?
You can use git blame to identify where the changes come from. Then we
can look at the individual commit
On 04/16/2017 11:30 PM, Uwe Stöhr wrote:
> Hi Richard,
>
> the attached patch fixes several box reversion issues in lyx2lyx.
> Scott could verify that the conversion to LyX 2.1.x works now as
> expected. Could this therefore also go in for LyX 2.2.3?
OK.
> Another issue: when I compare lyx-2_2.py
Hi Richard,
the attached patch fixes several box reversion issues in lyx2lyx. Scott
could verify that the conversion to LyX 2.1.x works now as expected.
Could this therefore also go in for LyX 2.2.3?
--
Another issue: when I compare lyx-2_2.py in master with branch I see a
lot of ch
El 16.04.2017 a las 04:21, Richard Heck escribió:
OK.
Thanks, it is in.
regards Uwe
Am Samstag, 15. April 2017 um 22:21:04, schrieb Richard Heck
> On 04/15/2017 02:06 PM, Uwe Stöhr wrote:
> > Hi Richard,
> >
> > the attached patch fixes 2 lyx2lyx issues in the box reversion
> > routines. Could this please go in for LyX 2.2.3?
>
> OK.
>
> rh
-1
Unless the export of examples/PDF
On 04/15/2017 02:06 PM, Uwe Stöhr wrote:
> Hi Richard,
>
> the attached patch fixes 2 lyx2lyx issues in the box reversion
> routines. Could this please go in for LyX 2.2.3?
OK.
rh
Hi Richard,
the attached patch fixes 2 lyx2lyx issues in the box reversion routines.
Could this please go in for LyX 2.2.3?
(In master they are already fixed but I winder why the issue with
"\usepackage" instead of "\\usepackage" was fixed in master long ago but
never backported.)
thanks a
On Sun, Feb 16, 2014 at 8:22 AM, Dustin J. Mitchell wrote:
> I hereby grant permission to license my contributions to LyX under the
> Gnu General Public Licence, version 2 or later.
>
> Dustin J. Mitchell
Thanks, Dustin. You're now added to the CREDITS (in Help > About).
Best,
Scott
I hereby grant permission to license my contributions to LyX under the
Gnu General Public Licence, version 2 or later.
Dustin J. Mitchell
-- Forwarded message --
From: Scott Kostyshak
Date: Sat, Feb 15, 2014 at 9:08 PM
Subject: Your patch for LyX
To: dus...@v.igoro.us
Hi
On 12/30/2013 01:13 PM, Stephan Witt wrote:
Am 30.12.2013 um 17:59 schrieb Richard Heck :
On 12/30/2013 06:06 AM, Stephan Witt wrote:
Hi Richard,
I had to use the current trunk version of the LyX build script to package
lyx-2.0.7 So, I want to back port this version. Is it ok?
The attached
Am 30.12.2013 um 17:59 schrieb Richard Heck :
> On 12/30/2013 06:06 AM, Stephan Witt wrote:
>> Hi Richard,
>>
>> I had to use the current trunk version of the LyX build script to package
>> lyx-2.0.7 So, I want to back port this version. Is it ok?
>>
>> The attached patch contains the mentioned
My second message was only about master... We still need gettext for 2.0.x.
JMarc
Richard Heck a écrit :
>On 12/30/2013 06:06 AM, Stephan Witt wrote:
>> Hi Richard,
>>
>> I had to use the current trunk version of the LyX build script to
>package lyx-2.0.7 So, I want to back port this version. I
On 12/30/2013 06:06 AM, Stephan Witt wrote:
Hi Richard,
I had to use the current trunk version of the LyX build script to package
lyx-2.0.7 So, I want to back port this version. Is it ok?
The attached patch contains the mentioned change. Plus it contains the changes
needed to build the packag
Le 30/12/13 13:04, Jean-Marc Lasgouttes a écrit :
Le 30/12/13 12:06, Stephan Witt a écrit :
Hi Richard,
I had to use the current trunk version of the LyX build script to
package lyx-2.0.7
So, I want to back port this version. Is it ok?
The attached patch contains the mentioned change. Plus it
Le 30/12/13 12:06, Stephan Witt a écrit :
Hi Richard,
I had to use the current trunk version of the LyX build script to package
lyx-2.0.7
So, I want to back port this version. Is it ok?
The attached patch contains the mentioned change. Plus it contains the changes
needed to build the package o
Hi Richard,
I had to use the current trunk version of the LyX build script to package
lyx-2.0.7
So, I want to back port this version. Is it ok?
The attached patch contains the mentioned change. Plus it contains the changes
needed to build the package on my current Mac OS X 10.8.5 with Xcode 5.0.
"Vincent van Ravesteijn - TNW" writes:
> So, now I can start complaining about Windows :)
Yes please :)
JMarc
>>> I hoped there would be a solution that would avoid changing LyXFunc
>>> at all and just ignore() early when the key event are unknown.
>>
>> Ah, probably because you want to isolate all Qt-related code within
>> frontends/qt4/. Here's yet another approach, at the keyPressEvent()
>> level:
"Ben M." writes:
>> I hoped there would be a solution that would avoid changing LyXFunc at all
>> and just ignore() early when the key event are unknown.
>
> Ah, probably because you want to isolate all Qt-related code within
> frontends/qt4/. Here's yet another approach, at the keyPressEvent()
>
On 05/07/2009 16:06, Jean-Marc Lasgouttes wrote:
Le 2 juil. 09 à 04:00, Ben M. a écrit :
I hoped there would be a solution that would avoid changing LyXFunc
at all
and just ignore() early when the key event are unknown.
Ah, probably because you want to isolate all Qt-related code within
front
On Sun, Jul 05, 2009 at 04:34:45PM +0200, Jean-Marc Lasgouttes wrote:
> Le 5 juil. 09 � 16:06, Jean-Marc Lasgouttes a �crit :
> > Unfortunately this does not tell me that it is working. I am currently
> > compiling on OS X, but the problem is to know what to test.
>
> Everything I tested on OS X
Le 5 juil. 09 à 16:06, Jean-Marc Lasgouttes a écrit :
Unfortunately this does not tell me that it is working. I am currently
compiling on OS X, but the problem is to know what to test.
Everything I tested on OS X seems correct.
Abdel, could you have a look please?
The plan could be to apply
Le 2 juil. 09 à 04:00, Ben M. a écrit :
I hoped there would be a solution that would avoid changing LyXFunc
at all
and just ignore() early when the key event are unknown.
Ah, probably because you want to isolate all Qt-related code within
frontends/qt4/. Here's yet another approach, at the k
> I hoped there would be a solution that would avoid changing LyXFunc at all
> and just ignore() early when the key event are unknown.
Ah, probably because you want to isolate all Qt-related code within
frontends/qt4/. Here's yet another approach, at the keyPressEvent()
level:
http://www.lyx.or
Le 1 juil. 09 à 22:02, Ben M. a écrit :
Thank you. I don't yet know proper C++ syntax, so I will do these
silly things while I learn.
No problem, I am here just for that. You are a very efficient student :)
What I would like is to drop the "Unknown function part" and only
test
on isKnown.
On Wed, Jul 1, 2009 at 6:40 AM, Jean-Marc Lasgouttes wrote:
> First incident remark: use
> known = !qkey_to_string(key_).empty();
> instead.
Thank you. I don't yet know proper C++ syntax, so I will do these
silly things while I learn.
> What I would like is to drop the "Unknown function par
"Ben M." writes:
> On Tue, Jun 30, 2009 at 5:12 AM, Jean-Marc Lasgouttes
> wrote:
>> What I would like (but I have not understood yet where to do that) is to
>> use reject() only when we have an unknown keysym. We should not reject
>> events because M-C-j is not bound currently, but because a giv
> Sure, how's this?
> http://www.lyx.org/trac/attachment/ticket/6043/multimediakeys3.diff
I verified that this patch also works on trunk.
Multimedia keys do work in Document - Settings, and Tools -
Preferences, but don't work in File - Open. I wonder if I missed a
QKeyEvent somewhere. However,
On Tue, Jun 30, 2009 at 5:12 AM, Jean-Marc Lasgouttes wrote:
> What I would like (but I have not understood yet where to do that) is to
> use reject() only when we have an unknown keysym. We should not reject
> events because M-C-j is not bound currently, but because a given
> multimedia key is not
Jean-Marc Lasgouttes writes:
> What I would like (but I have not understood yet where to do that) is to
> use reject() only when we have an unknown keysym. We should not reject
ignore()
> events because M-C-j is not bound currently, but because a given
> multimedia key is not handled by
"Ben M." writes:
> According to
> http://doc.trolltech.com/3.3/qkeyevent.html#details
> "Key events for multi media keys are ignored by default. You should
> call QKeyEvent::accept() if your widget handles those events."
Very good detective work (although you should point to the 4.2
documentati
According to
http://doc.trolltech.com/3.3/qkeyevent.html#details
"Key events for multi media keys are ignored by default. You should
call QKeyEvent::accept() if your widget handles those events."
Currently, LyX calls accept() for everything, so multimedia keys are
undesirably blocked:
http://w
>> The phantom feature is a math feature
>
> No, \phantom, \vphantom and \hphantom are general (plain TeX) commands, which
> also work outside mathed (I use them from time to time).
I know and use them often e.g. also in the EmbeddedObjects manual. But the suport for these comands
is at the mome
On Tue, Nov 06, 2007 at 08:40:19AM +0100, Jürgen Spitzmüller wrote:
> Uwe Stöhr wrote:
> > > I like this phantom feature a lot myself, but I think it qualifies as
> > > expert feature. I am not sure it belongs to the toolbar, but I do not
> > > oppose it.
> >
> > The phantom feature is a math featu
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
> Jean-Marc Lasgouttes wrote:
>> This is not good. The text should be any possible Text Inset (even a
>> font change would make the metrics bad).
>
> Then we need Tommaso's input widget (or a collapsable).
A collapsable separate from the space inset
Jean-Marc Lasgouttes wrote:
> This is not good. The text should be any possible Text Inset (even a
> font change would make the metrics bad).
Then we need Tommaso's input widget (or a collapsable).
Jürgen
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
> Jean-Marc Lasgouttes wrote:
>> Where would you put the text?
>
> Like Helge outlined. The dialog would include a combo with all the predefined
> spaces (enspace etc.), then custom for a length (\hspace) and a widget for
> text ("Space in the lengt
Jean-Marc Lasgouttes wrote:
> Where would you put the text?
Like Helge outlined. The dialog would include a combo with all the predefined
spaces (enspace etc.), then custom for a length (\hspace) and a widget for
text ("Space in the length of the following string").
Jürgen
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
> Jean-Marc Lasgouttes wrote:
>> I never thought about that... But of course you are right.
>
> I think ui-wise, phantoms should be implemented in a forthcoming InsetSpace
> dialog (in Texted).
Where would you put the text?
JMarc
Jürgen Spitzmüller wrote:
Jean-Marc Lasgouttes wrote:
I never thought about that... But of course you are right.
I think ui-wise, phantoms should be implemented in a forthcoming InsetSpace
dialog (in Texted).
Good idea. A dialog like:
_ short space
_ interword space
_ enskip
_ ems
Jean-Marc Lasgouttes wrote:
> I never thought about that... But of course you are right.
I think ui-wise, phantoms should be implemented in a forthcoming InsetSpace
dialog (in Texted).
Jürgen
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
>> The phantom feature is a math feature
>
> No, \phantom, \vphantom and \hphantom are general (plain TeX) commands, which
> also work outside mathed (I use them from time to time).
I never thought about that... But of course you are right.
JMarc
Uwe Stöhr <[EMAIL PROTECTED]> writes:
>> I like this phantom feature a lot myself, but I think it qualifies as
>> expert feature. I am not sure it belongs to the toolbar, but I do not
>> oppose it.
>
> The phantom feature is a math feature so it should be accessible via the
> math toolbar. The mat
Uwe Stöhr wrote:
> > I like this phantom feature a lot myself, but I think it qualifies as
> > expert feature. I am not sure it belongs to the toolbar, but I do not
> > oppose it.
>
> The phantom feature is a math feature
No, \phantom, \vphantom and \hphantom are general (plain TeX) commands, whic
I like this phantom feature a lot myself, but I think it qualifies as
expert feature. I am not sure it belongs to the toolbar, but I do not
oppose it.
The phantom feature is a math feature so it should be accessible via the
math toolbar. The math toolbar contains much more expert stuff than
plac
[EMAIL PROTECTED] (Jürgen Spitzmüller) writes:
> Uwe Stöhr wrote:
>> What about the other changes (fraction, placeholders)?
>
> The fraction changes are OK. For the placeholders, I'd like to have some
> input
> from math users first.
I like this phantom feature a lot myself, but I think it qual
Uwe Stöhr wrote:
> What about the other changes (fraction, placeholders)?
The fraction changes are OK. For the placeholders, I'd like to have some input
from math users first.
Jürgen
>> OK I'll postpone this change to LyX 1.6.0.
>
> Yes, please.
What about the other changes (fraction, placeholders)?
Uwe
Uwe Stöhr wrote:
> OK I'll postpone this change to LyX 1.6.0.
Yes, please.
Jürgen
> was the change from "math-insert
> \choose" to "math-insert \binom" intentional? And if so, why?
This is intended because LyX 1.6.0 will have \tbinom and \dbinom. So it will be confusing that the
standard binom command is \choose. \choose is identic to \binom.
OK I'll postpone this change to
Uwe Stöhr wrote:
> The attached patch registeres placeholders to the math toolbar and clarify
> some entries. OK for branch?
As I'm no math user, I do not have strong opinions. I guess \phantom is
useful. Is it also often used? What do others say?
The Fractions changes look good. However, was th
On Sun, Nov 04, 2007 at 08:33:59PM +0100, Uwe Stöhr wrote:
> The attached patch registeres placeholders to the math toolbar and clarify
> some entries.
> OK for branch?
>
> regards Uwe
>
> p.s. lyx.org is currently dead
In deep coma. But I did get a commit through...
- Martin
The attached patch registeres placeholders to the math toolbar and clarify some
entries.
OK for branch?
regards Uwe
p.s. lyx.org is currently dead
Index: stdtoolbars.inc
===
--- stdtoolbars.inc (revision 21421)
+++ stdtoolbars.inc
Uwe Stöhr wrote:
> Since I got no response from the marvosym package maintainer, g-brief won't
> be usable for MiKTeX and TeXLive 2007 users. I therefore added a warning to
> the templates to switch to g-brief2.
>
> What do you think?
Fine with me.
Jürgen
Since I got no response from the marvosym package maintainer, g-brief won't be usable for MiKTeX and
TeXLive 2007 users. I therefore added a warning to the templates to switch to g-brief2.
What do you think?
regards Uwe
Index: g-brief-de.lyx
=
> "Ronald" == Ronald Florence <[EMAIL PROTECTED]> writes:
Ronald> This patch adapts Jean-Marc's proposed localdir patch so it
Ronald> works only for LyX/Mac. It allows LyX/Mac to find its
Ronald> localedir in the relocatable Application bundle. Should have
Ronald> no effect on other architectu
This patch adapts Jean-Marc's proposed localdir patch so it works only
for LyX/Mac. It allows LyX/Mac to find its localedir in the
relocatable Application bundle. Should have no effect on other
architectures. (For 1.3.4)
--
Ronald
lyx-localedir.patch
Description: Binary data
> "Ronald" == Ronald Florence <[EMAIL PROTECTED]> writes:
Ronald> The attached patch is adapted from the corresponding patch to
Ronald> 1.3.4cvs, and allows LyX/Mac to find the LyX fonts inside its
Ronald> own relocatable application bundle. --
This is applied now.
JMarc
The attached patch is adapted from the corresponding patch to 1.3.4cvs,
and allows LyX/Mac to find the LyX fonts inside its own relocatable
application bundle.
--
Ronald
1.4.0-fonts.patch
Description: Binary data
On Wed, Jan 07, 2004 at 12:15:13PM -0500, Ronald Florence wrote:
> No more than maxBufLen bytes are written to buffer. If url requires
> more than maxBufLen bytes to represent itself, including the
> terminating null byte. this function returns false. To avoid this
IN which case we should real
On Jan 7, 2004, at 11:59 AM, John Levon wrote:
All of the code changes are inside QT_WS_MAC defines.
Looks fine
+ UInt8 buf[255];
+ CFURLGetFileSystemRepresentation(FontsURL, true, buf,
255);
But is this definitely correct ? (i.e. is the function API including
null
On Wed, Jan 07, 2004 at 11:10:49AM -0500, Ronald Florence wrote:
>
> All of the code changes are inside QT_WS_MAC defines.
Looks fine
+ UInt8 buf[255];
+ CFURLGetFileSystemRepresentation(FontsURL, true, buf, 255);
But is this definitely correct ? (i.e. is the funct
> "Ronald" == Ronald Florence <[EMAIL PROTECTED]> writes:
Ronald> Here is a revised patch for 1.4.0 to enable compilation on
Ronald> MacOS with Qt/Mac, and to include various LyX/Mac features
Ronald> (double-clicking from the finder, relocatable application, and
Ronald> setting the PATH for th
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> On Wed, Jan 07, 2004 at 04:53:22PM +0100, Jean-Marc Lasgouttes
John> wrote:
>> > "Ronald" == Ronald Florence <[EMAIL PROTECTED]> writes:
>>
Ronald> The attached patch to 1.3.4cvs -- suggested by Jean-Marc --
Ronald> lets LyX/Mac fin
On Jan 7, 2004, at 11:05 AM, John Levon wrote:
Ronald> The attached patch to 1.3.4cvs -- suggested by Jean-Marc --
Ronald> lets LyX/Mac find additional fonts in its own application
Ronald> bundle. The addFontPath code works, but does not get called by
Ronald> qfont_loader::available. Instead, Qt f
On Wed, Jan 07, 2004 at 04:53:22PM +0100, Jean-Marc Lasgouttes wrote:
> > "Ronald" == Ronald Florence <[EMAIL PROTECTED]> writes:
>
> Ronald> The attached patch to 1.3.4cvs -- suggested by Jean-Marc --
> Ronald> lets LyX/Mac find additional fonts in its own application
> Ronald> bundle. The a
Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>> "Ronald" == Ronald Florence <[EMAIL PROTECTED]> writes:
>
| Ronald> Here is a revised patch for 1.4.0 to enable compilation on
| Ronald> MacOS with Qt/Mac, and to include various LyX/Mac features
| Ronald> (double-clicking from the finder, re
> "Ronald" == Ronald Florence <[EMAIL PROTECTED]> writes:
Ronald> The attached patch to 1.3.4cvs -- suggested by Jean-Marc --
Ronald> lets LyX/Mac find additional fonts in its own application
Ronald> bundle. The addFontPath code works, but does not get called by
Ronald> qfont_loader::available
> "Ronald" == Ronald Florence <[EMAIL PROTECTED]> writes:
Ronald> Here is a revised patch for 1.4.0 to enable compilation on
Ronald> MacOS with Qt/Mac, and to include various LyX/Mac features
Ronald> (double-clicking from the finder, relocatable application, and
Ronald> setting the PATH for th
The attached patch to 1.3.4cvs -- suggested by Jean-Marc -- lets
LyX/Mac find additional fonts in its own application bundle. The
addFontPath code works, but does not get called by
qfont_loader::available. Instead, Qt finds fonts in the teTeX
hierarchy which do the math symbols wrong. The o
> "Ronald" == Ronald Florence <[EMAIL PROTECTED]> writes:
Ronald> Here is a revised patch for 1.4.0 to enable compilation on
Ronald> MacOS with Qt/Mac, and to include various LyX/Mac features
Ronald> (double-clicking from the finder, relocatable application, and
Ronald> setting the PATH for th
Here is a revised patch for 1.4.0 to enable compilation on MacOS with
Qt/Mac, and to include various LyX/Mac features (double-clicking from
the finder, relocatable application, and setting the PATH for the
application and auxiliary programs). I've incorporated Jean-Marc's
suggestion of a condi
My apologies for all those mistakes. Now, I've read the entire README and the
files in the development/Code_rules directory ;-)
I've send that patch mostly for the idea of inserting the X selection into a
table, because it could be useful for inserting columns of numbers for
example. But I think
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Mon, Jan 06, 2003 at 03:00:35PM +0100, Jean-Marc Lasgouttes wrote:
>> Andre> I am not sure this should go in 1.3.0 though and I am not sure
>> Andre> I am happy about the amount of code needed to implement this
>> Andre> feature, though...
>>
>> I do
On Mon, Jan 06, 2003 at 03:00:35PM +0100, Jean-Marc Lasgouttes wrote:
> Andre> I am not sure this should go in 1.3.0 though and I am not sure
> Andre> I am happy about the amount of code needed to implement this
> Andre> feature, though...
>
> I do not want yet another feature to do what we can al
> "Andre" == Andre Poenitz <[EMAIL PROTECTED]> writes:
Andre> On Mon, Jan 06, 2003 at 02:41:31PM +0100, Jean-Marc Lasgouttes
Andre> wrote:
>> If you want to insert a tab-spearated file in a table, here is how
>> you can do: create a new table, place the cursor in the first cell
>> (not in the
On Mon, Jan 06, 2003 at 02:41:31PM +0100, Jean-Marc Lasgouttes wrote:
> If you want to insert a tab-spearated file in a table, here is how you
> can do: create a new table, place the cursor in the first cell (not
> in the cell (red frame) but in the extra position on the left, and
> then do Paste E
> "Bruno" == Bruno Mathieu <[EMAIL PROTECTED]> writes:
Bruno> Oups, sorry ! Here is the dirty patch.
If you want to insert a tab-spearated file in a table, here is how you
can do: create a new table, place the cursor in the first cell (not
in the cell (red frame) but in the extra position on
Oups, sorry !
Here is the dirty patch.
--
Bruno
-- Message transmis --
Subject: Re: Patch for Lyx
Date: 05 Jan 2003 20:36:44 +0100
From: [EMAIL PROTECTED] (Lars Gullik Bjønnes)
To: Bruno Mathieu <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED]
Bruno Mathieu <[EMAIL
Bruno Mathieu <[EMAIL PROTECTED]> writes:
| Happy new Year, LyX Team !!!
|
| Here is a dirty (cut & paste ) patch for inserting the X selection as a table.
| My brother needed that, maybe somone else too ?
Perhaps. Thanks.
But we really need the patch as well :-)
And please send it to [EMAIL
On Wed, Jan 30, 2002 at 01:25:59PM +0100, Jean-Marc Lasgouttes wrote:
> So how come LyX oly uses ios and never ios_base? I'll stick to ios for
> simplicity.
g++ 2.95.2's standard library has no ios_base.
Andre'
--
André Pönitz .. [EMAIL PROTECTED]
> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
Lars> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>>> "Lars" == Lars Gullik Bjønnes <[EMAIL PROTECTED]> writes:
>>
Lars> | Lars> Use of ios::binary should be ok. (but I guess it really
Lars> should | Lars> be ios_base::binar
On Tue, Jan 22, 2002 at 07:10:16PM +0100, Jean-Marc Lasgouttes wrote:
> > "Kayvan" == Kayvan A Sylvan <[EMAIL PROTECTED]> writes:
>
> Kayvan> Huh.
>
> Kayvan> I never had to do any of this to get it to compile and run on
> Kayvan> Cygwin 1.3.6.
>
> Kayvan> I wonder what the difference is?
>
> "Kayvan" == Kayvan A Sylvan <[EMAIL PROTECTED]> writes:
Kayvan> Huh.
Kayvan> I never had to do any of this to get it to compile and run on
Kayvan> Cygwin 1.3.6.
Kayvan> I wonder what the difference is?
Most of these patches are included in 1.2.0cvs. My intent is to have
all necessary stu
Huh.
I never had to do any of this to get it to compile and run on
Cygwin 1.3.6.
I wonder what the difference is?
---Kayvan
On Tue, Jan 22, 2002 at 12:15:52PM +0100, Claus Hentschel wrote:
> Attached is my patch against the sources to make Lyx running on Win32 using
>
Attached is my patch against the sources to make Lyx running on Win32 using
the Cygwin environment (release 1.3.6). Maybe someone is interested and this
patch will be included in future releases.
Some remarks to that patch:
1) lib/configure.m4 wasn't part of the sources tarball. I've picked that
> > "Bruce" == Bruce Foster <[EMAIL PROTECTED]> writes:
>
>Bruce> After applying the patch and rerunning the configuration, the
>Bruce> compile still fails in fmt.C:
>
>Have you run autoconf?
>
>JMarc
At that time, I was working with an incomplete patch and also had not
run autoconf. With Al
> "Bruce" == Bruce Foster <[EMAIL PROTECTED]> writes:
Bruce> After applying the patch and rerunning the configuration, the
Bruce> compile still fails in fmt.C:
Have you run autoconf?
JMarc
> "Bruce" == Bruce Foster <[EMAIL PROTECTED]> writes:
Bruce> After applying the patch and rerunning the configuration, the
Bruce> compile still fails in fmt.C:
Could somebody try to compile on HP-UX from the latest cvs?
JMarc
After applying the patch and rerunning the configuration, the compile
still fails in fmt.C:
/bin/sh ../../libtool --mode=compile g++ -DHAVE_CONFIG_H -I. -I.
-I../../src -I./../ -I../../boost -I/opt/local/include
-D_HPUX_SOURCE -fno-rtti -fno-exceptions -c fmt.C
g++ -DHAVE_CONFIG_H -I. -I. -I.
On Tue, Feb 06, 2001 at 05:21:38PM +0100, Jean-Marc Lasgouttes wrote:
> > "lyx-devel" == lyx-devel <[EMAIL PROTECTED]> writes:
>
> lyx-devel> After building and installing, executing lyx gives:
> lyx-devel> /usr/lib/dld.sl: Call to mmap() failed - TEXT
> lyx-devel> /opt/TWWfsw/libxforms/lib/
1 - 100 of 117 matches
Mail list logo
