Configuration
Host type: i686-pc-linux-gnu
Special build flags:warnings assertions xforms-image-loader compression
C Compiler: gcc
C Compiler flags: -g -O2
C++ Compiler: g++ (2.96)
C++ Compiler flags:
This is the end of the "make install" in making the lyx-1.3.x RPM:
/usr/bin/install -c -m 644 xfonts/fonts.dir /var/tmp/lyx-1.3.4cvs-root/usr/share
/lyx/xfonts/fonts.dir ; \
/usr/bin/install -c -m 644 xfonts/fonts.scale /var/tmp/lyx-1.3.4cvs-root/usr/sha
re/lyx/xfonts/fonts.scale
mkdir /var/tmp/ly
My kids are all big time mac users, so the sooner the better.
Garst
Jean-Marc Lasgouttes wrote:
>
> > "John" == John Levon <[EMAIL PROTECTED]> writes:
>
> John> Has somebody taken care of announcing to the usual places ?
>
> John> LWN, LinuxToday, apps.kde.com etc.
>
> The announcement was
In src/support/Makefile.am
--
Kayvan A. Sylvan | Proud husband of | Father to my kids:
Sylvan Associates, Inc. | Laura Isabella Sylvan | Katherine Yelena (8/8/89)
http://sylvan.com/~kayvan | "crown of her husband" | Robin Gregory (2/28/92)
Index: src/support/Makefile.am
===
On Fri, Sep 26, 2003 at 01:51:07PM -0700, Mike Ressler wrote:
> them to CVS. Also, if there are any glaring deficiencies in the docs,
> let me know - I can try to fix them, just not with the speed I used to.
There are glaring deficiencies, but they're mostly missing stuff. The
docs should be pre
The RPM auto-build has been changed.
At this point, whether or not the build succeeds, there are logs in
ftp://ftp.sylvan.com/pub/lyx/devel/log
These logs can be looked at by anyone and I encourage developers and users
to look for them (especially when a daily build appears to be missing
On Mon, 2003-09-22 at 03:56, Angus Leeming wrote:
> Just a thought, but is there any sense in the commit privileges to lyxdoc
> vis-à-vis lyx-devel?
>
> avail|larsbj,mressler,lasgouttes,karger,rae,levon|lyxdoc
> avail|larsbj,lasgouttes,jug,rae,jamatos,alstrup,poenitz,dekel,leeming,levon,abra
> un
Christian Ridderström wrote:
> however, then I get other errors because getLanguages() is unknown...
getLanguages() is a member function in ControlListing. I'll send you a patch
privately.
Jürgen.
Christian Ridderström wrote:
> vector const languages = frnt::getLanguages();
> Any ideas on how it should be today? (The file is also attached).
frnt::getLanguageData() ?
--
Angus
Hi
I'm still trying to port Herbert's listing stuff (now for Qt), and the
compiler chokes on this:
vector const languages = frnt::getLanguages();
with the error:
qt2/QListing.C:71: `frnt' undeclared (first use this function)
qt2/QListing.C:71: (Each undeclared identifier is reported on
> "John" == John Levon <[EMAIL PROTECTED]> writes:
John> Has somebody taken care of announcing to the usual places ?
John> LWN, LinuxToday, apps.kde.com etc.
The announcement was Bcc'd to [EMAIL PROTECTED] I did not try the others.
BTW it already transpires that I forgot to add a few macosx
This patch adds a missing file.
? debug-1.diff
? debug-2.diff
Index: boost/boost/test/detail/nullstream.hpp
===
RCS file: boost/boost/test/detail/nullstream.hpp
diff -N boost/boost/test/detail/nullstream.hpp
--- /dev/null 1 Jan 1970
Has somebody taken care of announcing to the usual places ?
LWN, LinuxToday, apps.kde.com etc.
regards
john
--
Khendon's Law:
If the same point is made twice by the same person, the thread is over.
Andre Poenitz <[EMAIL PROTECTED]> writes:
| On Fri, Sep 26, 2003 at 02:41:04PM +0200, Lars Gullik Bjønnes wrote:
>>
>> This is the reworked debug stream.
>
| Fine with me if it works.
>
| Incidently, would it be possible to remove a few ./configure checks
| afterwards?
You mean the testing for m
On Fri, Sep 26, 2003 at 02:41:04PM +0200, Lars Gullik Bjønnes wrote:
>
> This is the reworked debug stream.
Fine with me if it works.
Incidently, would it be possible to remove a few ./configure checks
afterwards?
Andre'
This is the reworked debug stream.
Unless I get objections, this will go into CVS rather soon.
? debug-1.diff
Index: po/POTFILES.in
===
RCS file: /usr/local/lyx/cvsroot/lyx-devel/po/POTFILES.in,v
retrieving revision 1.354
diff -u -p
Am Freitag, 26. September 2003 13:04 schrieb Helge Hafting:
> j.heidemeier wrote:
> > 3. The main exposure of the Floats is misleading from the authors
> > perspective. Floats are TeX's typesetting perspective. For the author
> > tabular and longtable are similar - not floating figures or floating
Jean-Marc Lasgouttes wrote:
> Angus> A bit slow (about an hour ;-) but looks successful. 472 files
> Angus> changed in the 1.4 tree.
>
> Great!
>
> If it turns out that this solves the problems and did not break
> anything, this would be nice to have in 1.3.4cvs.
I guess you should get Hartmut t
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> Jean-Marc Lasgouttes wrote:
>> It would be nice to change our xpms so that this works
>> consistently. I am not sure though what is the best tool to do
>> that...
Angus> A bit slow (about an hour ;-) but looks successful. 472 files
Christian Ridderström <[EMAIL PROTECTED]> writes:
| Hi
>
| Is there a description of what the different targets in the Makefile(s) do
| anywhere? For instance, what's the difference between the different
| 'clean'-targets, i.e. when should you use what?
>
| /Christian
>
| Here are the targets I
j.heidemeier wrote:
3. The main exposure of the Floats is misleading from the authors perspective.
Floats are TeX's typesetting perspective. For the author tabular and
longtable are similar - not floating figures or floating tables. The ability
to float in the final layout should be handled as
Hi
Is there a description of what the different targets in the Makefile(s) do
anywhere? For instance, what's the difference between the different
'clean'-targets, i.e. when should you use what?
/Christian
Here are the targets I found in src/Makefile by using grep:
all: all-recursive
Makefile:
Angus Leeming <[EMAIL PROTECTED]> writes:
| Lars Gullik Bjønnes wrote:
>> | I thnk that adding a couple of ? should do that.
>> | // A valid environment variable is defined as
>> | // $\{?[A-Za-z_][A-Za-z_0-9]*\}?
>> | Do you agree?
>>
>> $\{?[[:alpha:]][[:word:]]*\}?
>>
>> bett
On Friday 26 September 2003 10:03 am, Jean-Marc Lasgouttes wrote:
> > "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
>
> Angus> I thnk that adding a couple of ? should do that. // A valid
> Angus> environment variable is defined as //
> Angus> $\{?[A-Za-z_][A-Za-z_0-9]*\}? Do you agree?
>
Public release of LyX version 1.3.3
===
We are pleased to announce the release of LyX 1.3.3.
This is a maintenance release which improves upon 1.3.2 in
four main areas:
* import of old LyX files and export to DocBook have been improved;
* many small bugs in th
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> I thnk that adding a couple of ? should do that. // A valid
Angus> environment variable is defined as //
Angus> $\{?[A-Za-z_][A-Za-z_0-9]*\}? Do you agree?
Does this really make sure that the {} match? It is probably good
enough, t
Lars Gullik Bjønnes wrote:
> | I thnk that adding a couple of ? should do that.
> | // A valid environment variable is defined as
> | // $\{?[A-Za-z_][A-Za-z_0-9]*\}?
> | Do you agree?
>
> $\{?[[:alpha:]][[:word:]]*\}?
>
> better?
I have to admit that I am not familiar with thes
[EMAIL PROTECTED] (Lars Gullik Bjønnes) writes:
| Angus Leeming <[EMAIL PROTECTED]> writes:
>
| | I thnk that adding a couple of ? should do that.
| | // A valid environment variable is defined as
| | // $\{?[A-Za-z_][A-Za-z_0-9]*\}?
| | Do you agree?
>
| $\{?[[:alpha:]][[:word:]]
Angus Leeming <[EMAIL PROTECTED]> writes:
| I thnk that adding a couple of ? should do that.
| // A valid environment variable is defined as
| // $\{?[A-Za-z_][A-Za-z_0-9]*\}?
| Do you agree?
$\{?[[:alpha:]][[:word:]]*\}?
better?
http://www.boost.org/libs/regex/syntax.htm#synta
Jean-Marc Lasgouttes wrote:
> This is very nice. The only possible improvement would be to allow the
> omission of curly brackets in cases where there is no ambiguity.
>
> That would mean that, beside this case:
> + // A valid environment variable is defined as
> + // $\{[A-Za-z_][A-Za-z_0
Lars Gullik Bjønnes wrote:
> | Why does it do that? Surely that does not conform to the principle of
> | least surprise.
>
> because it is not intended for real regexps but for globs.
> In he shell "*" == regex ".*" etc.
> I am fine with requiring to use real regex all the time, but I must
> admi
> "Angus" == Angus Leeming <[EMAIL PROTECTED]> writes:
Angus> I've rewritten ReplaceEnvironmentPath in a sane manner and got
Angus> rid of lstrings.[Ch] regexMatch because nothing was using it.
This is very nice. The only possible improvement would be to allow the
omission of curly brackets i
Angus Leeming <[EMAIL PROTECTED]> writes:
| This started off as a simple question about this code in
| support/lstrings.[Ch]:
>
| /** Compares a string and a (simple) regular expression
| * The only element allowed is "*" for any string of characters
| */
| bool regexMatch(string const & a, st
33 matches
Mail list logo
