Angus Leeming wrote:
> $ ls -l *.dvi
> -rw-rw-r-- 1 angus angus 496736 Feb 15 22:33 UserGuide_13x.dvi
> -rw-rw-r-- 1 angus angus 496940 Feb 15 22:33 UserGuide_13x_2.dvi
Repeating the loop (to get UserGuide_13x_3.dvi) I see these warnings:
Warning: Could not find graphics file 'mobius.eps not fo
As ever, this is pre-release software. Use at your own risk.
Get it here (760kB):
http://www.devel.lyx.org/~leeming/tex2lyx_win32_15Feb05.zip
It will unzip to a directory LyX containing
LyX/
bin/
reLyX
tex2lyx.exe
Resources/
lyx/
chkconfig.ltx
configure
credits
UserGuide_13x.lyx --exported to--> UserGuide_13x.tex
UserGuide_13x.tex --tex2lyx--> UserGuide_14x.lyx
UserGuide_14x.lyx --lyx2lyx--> UserGuide_13x_2.lyx
Open this file, UserGuide_13x_2.lyx, with lyx 1.3.x and *save it*.
This step gets rid of all the whitespace differences produced by
the round tri
André, I hope your cvs troubles are solved soon. I am not going to write
comments and changelogs for you forever ;-)
It would ease Andre's life and reduce the download/upload times
significantly, if somebody committed up-to-date ./po/*.po files. (But beware
of the problem that I have mentioned so
Georg Baum wrote:
> Am Dienstag, 15. Februar 2005 19:58 schrieb Angus Leeming:
>> These patches work around a bug in the gcc 2.95 STL implementation.
>
> 1.4 does not work with the gcc 2.95 STL at all. One needs to use STLport.
> Fortunately I don't have to use gcc 2.95 anymore, but I have this
>
In no particular order, these are the things that I think need to be
considered before either LyX 1.3.6 or 1.4.0 is released to the wider
world. Unless marked (14x), each entry refers equally to either release.
* Leave reLyX in its own directory and add a symlink/reLyX.cmd to the
bin directory?
*
Am Dienstag, 15. Februar 2005 11:31 schrieb Lars Gullik Bjønnes:
> Ok, then at least the --x; should have a comment on it.
See attached. Committing now.
André, I hope your cvs troubles are solved soon. I am not going to write
comments and changelogs for you forever ;-)
Georg
diff -p -r -U 3 -X
Am Dienstag, 15. Februar 2005 19:58 schrieb Angus Leeming:
> These patches work around a bug in the gcc 2.95 STL implementation.
1.4 does not work with the gcc 2.95 STL at all. One needs to use STLport.
Fortunately I don't have to use gcc 2.95 anymore, but I have this
compiler + STLport still in
Angus Leeming wrote:
> MSVC complains about line 797 of rowpainter.C:
> if (vi.p2 < text->paragraphs().size() - 1) {
>
> \lyx\lyx-devel\src\rowpainter.C(797) : warning C4018: '<' :
> signed/unsigned mismatch
>
> vi.p2 has type lyx::pit_type (ptrdiff_t).
> text->paragraphs().size() has type s
Bennett Helm wrote:
>> Bennett, could you post the patch of all changes to the list,
>> just to make sure that I don't forget anything.
>
> Here it is. I've left in all the diagnostic stuff. Also, note lines
> 68-69, which you'll probably want to delete.
>
> Bennett
Thanks.
--
Angus
These patches work around a bug in the gcc 2.95 STL implementation.
Committing now.
--
AngusIndex: src/support/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/support/ChangeLog,v
retrieving revision 1.149.2.36
diff -u -p
> I see. I'll commit your patch if you attach it again (with ChangeLog
please).
I invented a Changelog entry and committed this right now.
Georg
Index: src/ChangeLog
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/src/ChangeLog,v
re
Here's a summary of what needs to be done to fix the vcproj build:
development\win32\package.C:
Change GetEnv to getEnv and/or update from package.C.in
development\win32\lyx.vcproj
Add src\support\environment.C
Remove src\support\putenv.C
src\lyxserver.C (win32_kludge.diff)
Fix by updating broke
On Feb 15, 2005, at 11:42 AM, Angus Leeming wrote:
Bennett, could you post the patch of all changes to the list,
just to make sure that I don't forget anything.
Here it is. I've left in all the diagnostic stuff. Also, note lines
68-69, which you'll probably want to delete.
Bennett
bennett.diff
Asger Alstrup wrote:
Angus wrote:
> I wonder if the attached patch will make MSVC happy. Could you test it
> for me?
The result is below.
Regards,
Asger
Thanks, Asger. I guess that I'll just have to try harder.
Angus
Bennett Helm wrote:
Try changing the ss.tellp() bit to something comparing iterators:
That seems to do the trick! (See output below.) I'll do more testing
tomorrow.
Excellent! Thanks for your patience.
I can't find any other problems with this.
Bennett, could you post the patch of all changes to
Rob Bearman wrote:
Unfortunately, environment.C doesn't build under MSVC:
environment.C
\lyx\lyx-devel\src\support\environment.C(90) : error C2079: 'ss' uses
undefined class 'std::basic_ostringstream<_Elem,_Traits,_Alloc>'
Oops! Add #include
package.C
package.C(322) : error C3861: 'GetEnv': ident
> A fixed VS lyxserver.C is attached. When I find the time,
> I'll update the
> patch.
>
> Regards,
> Asger
>
Thank you. Also, I think the vcproj file will need to be updated to
remove putenv.C and add environment.C. Unfortunately, environment.C
doesn't build under MSVC:
Compiling...
environm
Juergen Spitzmueller <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>
>> I am very happy to see bugs fixed. but I am a bit wary of adding
>> functionality at this stage.
>
| It's a bug fix really. The unability to break paragraphs is a severe (and
| the biggest remaining AFAICS) limitat
A fixed VS lyxserver.C is attached. When I find the time, I'll update the
patch.
Regards,
Asger
/**
* \file lyxserver.C
* This file is part of LyX, the document processor.
* Licence details can be found in the file COPYING.
*
* \author Lars Gullik Bjønnes
* \author Jean-Marc Lasgouttes
* \
On Tue, 2005-02-15 at 14:29, Angus Leeming wrote:
> Edwin Leuven wrote:
> > i just don't really understand why selections are so complicated compared
> > to copy and cut's. why not send a signal (with a string) to the frontend
> > on selection. the frontend can then push it to the selection buffer
> CVSROOT: /usr/local/lyx/cvsroot
> Module name: lyx-devel
> Repository: lyx-devel/src/
> Changes by: [EMAIL PROTECTED] 05/02/15 12:04:40
>
> Modified files:
> lyx-devel/src/: ChangeLog lyxserver.C
>
> Log message:
> Squash MSVC warning "local variable 'fd' used witho
On Tue, Feb 15, 2005 at 03:21:22PM +0100, Juergen Spitzmueller wrote:
> > I am very happy to see bugs fixed. but I am a bit wary of adding
> > functionality at this stage.
>
> It's a bug fix really. The unability to break paragraphs is a severe (and
> the biggest remaining AFAICS) limitation of
On Feb 14, 2005, at 5:01 PM, Angus Leeming wrote:
Bennett Helm wrote:
Try changing the ss.tellp() bit to something comparing iterators:
That seems to do the trick! (See output below.) I'll do more testing
tomorrow.
Excellent! Thanks for your patience.
I can't find any other problems with this.
Benn
Angus wrote:
> I wonder if the attached patch will make MSVC happy. Could you test it
> for me?
The result is below.
Regards,
Asger
Compiling...
ExternalTransforms.C
\lyx\lyx-devel\src\insets\ExternalTransforms.C(345) : warning C4239:
nonstandard extension used : 'argument' : conversion from
'boo
On MacOSX, the lyx directory for both lyx-136 and lyx-140 is currently
~/Library/Application Support/lyx, which of course has a space in it.
Although it's possible to open .lyx files here (such as those found in
the doc, examples, and templates directories), LyX prevents running
LaTeX on these
Lars Gullik Bjønnes wrote:
> I am very happy to see bugs fixed. but I am a bit wary of adding
> functionality at this stage.
It's a bug fix really. The unability to break paragraphs is a severe (and
the biggest remaining AFAICS) limitation of the change tracker (see bug
880).
> Are you able to
Angus Leeming wrote:
I read that as saying that the code in the mail at the start of this thread
is perfectly safe, don't you?
Well, we also have:
template
class _Tree
{
const_iterator find(const key_type& _Keyval) const
{ // find an element in nonmutable seque
Lars Gullik Bjønnes wrote:
> | Ok, here's the entire patch in all its glory. The putenv merge replaces
> | the code of filetools.C's putEnv function (HAVE_PUTENV block) with that
> | in environment.C's setEnv function.
>
> This looks ok to me.
Then it it goes... Done.
--
Angus
Asger Alstrup wrote:
> Angus Leeming wrote:
>> That will require an MSVC user (Asger) to check his
>> std::map::const_iterator implementation.
>
> I'm not sure this is what you are looking for, but here is some of the
> code for the map::const_iterator in MSVC 7.1:
>
> class const_iterator
> : p
Angus Leeming wrote:
That will require an MSVC user (Asger) to check his
std::map::const_iterator implementation.
I'm not sure this is what you are looking for, but here is some of the code
for the map::const_iterator in MSVC 7.1:
class const_iterator
: public _Bidit
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>> | Lars Gullik Bjønnes wrote:
| It seems like an intelligent change to make to me, but I see that
| Lars' has said that we should be thinking in terms of a freeze. Can I
| ask formally, therefore, for permissio
Gentlemen,
I wonder if the attached patch will make MSVC happy. Could you test it
for me?
I'm hoping that it will silence warnings like:
ExternalTransforms.C
\lyx\lyx-devel\src\insets\ExternalTransforms.C(345) : warning C4239:
nonstandard extension used : 'argument' : conversion from
'boost::
Edwin Leuven wrote:
> i just don't really understand why selections are so complicated compared
> to copy and cut's. why not send a signal (with a string) to the frontend
> on selection. the frontend can then push it to the selection buffer (if
> it exists). and if a copy or cut follows put the str
Lars Gullik Bjønnes wrote:
> | Lars Gullik Bjønnes wrote:
>>> | It seems like an intelligent change to make to me, but I see that
>>> | Lars' has said that we should be thinking in terms of a freeze. Can I
>>> | ask formally, therefore, for permission to commit this patch.
>>>
>>> Patch ok.
>>
> |
Hi,
I have this in my tree, I think that we have discussed this some time ago
as it fixes a bug reported at that time.
If I don't have any objections I will apply it soon. :-)
--
José Abílio
Index: LyX.py
===
RCS file: /usr/loca
Angus Leeming wrote:
I agree that LyX's interaction with klipper is a PITA. Can you explain the
implications of the changes below? What changes, other than klipper being
happy?
hi angus,
it's really all trial and error (little kid groping in the dark).
as you've noticed i even missed the other wa_p
Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
> | class Mover {...};
> | class SpecialisedMover : public Mover {...};
>>
> | class Movers {
> | public:
> | /// @c returns the Mover registered for format @c fmt.
> | Mover const & operator()(std::string const & f
Lars Gullik Bjønnes wrote:
> | The patch is exactly equivalent to this test code. c==c2 and uc==uc2,
> | as expected.
>
> :-)
>
> When I said tested, meant "compiled"
> but your test was nice as well.
Sheesh! You think I trust myself to second guess what a compiler thinks
about all these implici
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>
>> Angus Leeming <[EMAIL PROTECTED]> writes:
>>
>> | Angus Leeming wrote:
>>>
Lars Gullik Bjønnes wrote:
> Hmm... it should be easy to avoid the extra local var.
>
>'\x5f' could have been used.
Lars Gullik Bjønnes wrote:
> Angus Leeming <[EMAIL PROTECTED]> writes:
>
> | Angus Leeming wrote:
>>
>>> Lars Gullik Bjønnes wrote:
Hmm... it should be easy to avoid the extra local var.
'\x5f' could have been used.
but keep the local var, but IMHO it would be ni
Angus Leeming <[EMAIL PROTECTED]> writes:
| class Mover {...};
| class SpecialisedMover : public Mover {...};
>
| class Movers {
| public:
| /// @c returns the Mover registered for format @c fmt.
| Mover const & operator()(std::string const & fmt) const
| {
| SpecialsMap::cons
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>> | It seems like an intelligent change to make to me, but I see that Lars'
>> | has said that we should be thinking in terms of a freeze. Can I ask
>> | formally, therefore, for permission to commit this patch.
>>
>> Patch o
Angus Leeming <[EMAIL PROTECTED]> writes:
| Angus Leeming wrote:
>
>> Lars Gullik Bjønnes wrote:
>>> Hmm... it should be easy to avoid the extra local var.
>>>
>>>'\x5f' could have been used.
>>>
>>> but keep the local var, but IMHO it would be nice with:
>>>
>>> char const underbar
Lars Gullik Bjønnes wrote:
> | It seems like an intelligent change to make to me, but I see that Lars'
> | has said that we should be thinking in terms of a freeze. Can I ask
> | formally, therefore, for permission to commit this patch.
>
> Patch ok.
Thanks. Shall I commit it as is, or are you al
Angus Leeming <[EMAIL PROTECTED]> writes:
| João Assirati contributed a 'less horrible, less leaky' putenv function in
| src/support/putenv.C. It's currently used only by src/lyxsocket.C.
>
| We also have putEnv in src/support/filetools.C. It has the same signature
| as João's function but uses ei
Angus Leeming <[EMAIL PROTECTED]> writes:
| Tracking down the reasons for Bennett's problems with LyX compiled
| with gcc 2.95 on MacOSX, I got pissed off and changed the names of the
| setter and getter functions. This patch
>
| * renames GetEnv as getEnv
| * renames putEnv as setEnv. It also cha
class Mover {...};
class SpecialisedMover : public Mover {...};
class Movers {
public:
/// @c returns the Mover registered for format @c fmt.
Mover const & operator()(std::string const & fmt) const
{
SpecialsMap::const_iterator const it = specials_.find(fmt);
return (i
"Michael Schmitt" <[EMAIL PROTECTED]> writes:
>> The new teTeX 3.0 has a way (or two) to handle spaces. Something like
>>\include{"My Files"}
>>
>> So probably we should drop all safety checks concerning this and just
>> include the quotes whenever LyX creates such a TeX command.
>
| That is n
Angus Leeming wrote:
> Lars Gullik Bjønnes wrote:
>> Hmm... it should be easy to avoid the extra local var.
>>
>>'\x5f' could have been used.
>>
>> but keep the local var, but IMHO it would be nice with:
>>
>> char const underbar = '\x5f';
>>
>> then you don't get any conversions a
Angus Leeming <[EMAIL PROTECTED]> writes:
| Andreas Vox wrote:
>
>> Angus Leeming <[EMAIL PROTECTED]> writes:
>>
>>> Well that seems pretty conclusive then. setEnvPath loops over the
>>> elements but doesn't do anything with them.
>>>
>>> Try changing the ss.tellp() bit to something comparing it
Lars Gullik Bjønnes wrote:
> Hmm... it should be easy to avoid the extra local var.
>
>'\x5f' could have been used.
>
> but keep the local var, but IMHO it would be nice with:
>
> char const underbar = '\x5f';
>
> then you don't get any conversions at all, implicit nor explicit.
Ok
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Mon, Feb 14, 2005 at 01:21:24PM +0100, Lars Gullik Bjønnes wrote:
>> | - return Point(x,y);
>> | + --x;
>>
>> Why this extra line and not just:
>>
>> x += dit.bottom().text()->cursorX(dit.bottom()) - 1;
>
| No specific reason other than that corre
Johnathan Burchill <[EMAIL PROTECTED]> writes:
| Hi folks,
>
| Please find attached three files: a change-tracking patch, and a new inset
| declaration and implementation.
>
| Use -p0 from the top-level source dir for applying the patch.
| insetnewparagraph.{C,h} need to be placed in src/insets/
MSVC complains about line 797 of rowpainter.C:
if (vi.p2 < text->paragraphs().size() - 1) {
\lyx\lyx-devel\src\rowpainter.C(797) : warning C4018: '<' : signed/unsigned
mismatch
vi.p2 has type lyx::pit_type (ptrdiff_t).
text->paragraphs().size() has type std::size_t
Given that (text->paragrap
Angus Leeming <[EMAIL PROTECTED]> writes:
| Here's another obvious fix. Ok to commit?
>
| \lyx\lyx-devel\src\insets\insetlatexaccent.C(431) : warning C4309:
| 'argument' : truncation of constant value
>
| Index: src/insets/insetlatexaccent.C
| =
This patch is trivial and squashes the MSVC warning below. Committing now.
\lyx\lyx-devel\src\graphics\GraphicsLoader.C(29) : warning C4099:
'lyx::graphics::Loader::Impl' : type name first seen using 'class' now
seen using 'struct' c:\lyx\lyx-devel\src\graphics\GraphicsLoader.h(103) :
see declarat
Asger Alstrup <[EMAIL PROTECTED]> writes:
| Andre Poenitz wrote:
>> On Mon, Feb 14, 2005 at 05:17:49PM +0100, Jean-Marc Lasgouttes wrote:
>>>If there is interest and if things evolve positively, I may be able to
>>> propose Paris
>> Both sound nice. [And in case it matters: I am a bit biased towar
Edwin Leuven wrote:
> PS i was finally too annoyed by lyx's clipboard behavior (klipper in kde
> was hanging etc...) so i removed the line above, made the changes below,
> and life has been better since...
I agree that LyX's interaction with klipper is a PITA. Can you explain the
implications of t
Angus Leeming wrote:
> Here's another obvious fix. Ok to commit?
I committed it.
--
Angus
João Assirati contributed a 'less horrible, less leaky' putenv function in
src/support/putenv.C. It's currently used only by src/lyxsocket.C.
We also have putEnv in src/support/filetools.C. It has the same signature
as João's function but uses either ::setenv or ::putenv internally with a
preferen
Tracking down the reasons for Bennett's problems with LyX compiled
with gcc 2.95 on MacOSX, I got pissed off and changed the names of the
setter and getter functions. This patch
* renames GetEnv as getEnv
* renames putEnv as setEnv. It also changes the function signature from a
single coded argume
On Monday 14 February 2005 16:17, Jean-Marc Lasgouttes wrote:
> Interested?
Certainly. :-)
> JMarc
--
José Abílio
Andre Poenitz wrote:
On Mon, Feb 14, 2005 at 05:17:49PM +0100, Jean-Marc Lasgouttes wrote:
If there is interest and if things evolve positively, I may be able to
propose Paris
Both sound nice. [And in case it matters: I am a bit biased towards
France outside Paris...]
Paris sounds great!
Regards,
64 matches
Mail list logo
