On 13 Sep 2000 09:00:50 +0200, Lars Gullik Bjønnes wrote:
| --- po/Makefile.in.in.orig Tue Sep 12 18:57:02 2000
| +++ po/Makefile.in.inTue Sep 12 18:51:04 2000
| @@ -24,6 +24,8 @@ gnulocaledir = $(prefix)/share/locale
| gettextsrcdir = $(prefix)/share/gettext/po
| subdir = po
|
|
On Wed, 13 Sep 2000 10:55:11 + (GMT), Carlos A M dos Santos wrote:
Have you patched LyX or any other software to use native catgets? In my
system (FreeBSD 4.1-RELEASE) I have gettext-0.10.35 installed because it
is required by GNU make and wget, but LyX is statically linked to the
included
On 13 Sep 2000 12:42:49 +0200, Jean-Marc Lasgouttes wrote:
I thought it was only a problem for suid programs... I would not give
LyX such special rights, anyway...
What, if a talented and qualified intrusor would be able to connect the
functions to a suid program? This only means that one leak
On Wed, 13 Sep 2000 14:43:43 + (GMT), Carlos A M dos Santos wrote:
On Wed, 13 Sep 2000, Juergen Vigna wrote:
Well wouldn't it be easier to specify in the /usr/local/share/lyx/lyxrc
file that you want your files in ~/tmp and create a ~/tmp for every user?
It's undocumented, at least in
On Wed, 13 Sep 2000 13:08:24 -0700, Carl Ollivier-Gooch wrote:
And security/privacy means always security/privacy to be enforced by
default, unless somebody who knows what he is doing decides against
them. (Most commercial Linux distributions entirely would disagree; but
they are biased,
On 13 Sep 2000 09:00:50 +0200, Lars Gullik Bjønnes wrote:
>| --- po/Makefile.in.in.orig Tue Sep 12 18:57:02 2000
>| +++ po/Makefile.in.inTue Sep 12 18:51:04 2000
>| @@ -24,6 +24,8 @@ gnulocaledir = $(prefix)/share/locale
>| gettextsrcdir = $(prefix)/share/gettext/po
>| subdir = po
>|
On Wed, 13 Sep 2000 10:55:11 + (GMT), Carlos A M dos Santos wrote:
>Have you patched LyX or any other software to use native catgets? In my
>system (FreeBSD 4.1-RELEASE) I have gettext-0.10.35 installed because it
>is required by GNU make and wget, but LyX is statically linked to the
On 13 Sep 2000 12:42:49 +0200, Jean-Marc Lasgouttes wrote:
>
>I thought it was only a problem for suid programs... I would not give
>LyX such special rights, anyway...
What, if a talented and qualified intrusor would be able to connect the
functions to a suid program? This only means that one
On Wed, 13 Sep 2000 14:43:43 + (GMT), Carlos A M dos Santos wrote:
>On Wed, 13 Sep 2000, Juergen Vigna wrote:
>
>> Well wouldn't it be easier to specify in the /usr/local/share/lyx/lyxrc
>> file that you want your files in ~/tmp and create a ~/tmp for every user?
>
>It's undocumented, at
On Wed, 13 Sep 2000 13:08:24 -0700, Carl Ollivier-Gooch wrote:
>> > And security/privacy means always security/privacy to be enforced by
>> > default, unless somebody who knows what he is doing decides against
>> > them. (Most commercial Linux distributions entirely would disagree; but
>> > they
Hi,
Lars or Jean-Marc: Could you just cut cut and paste the following recipe by
Shigeru to the beginning of the OS/2-cookbook:
INSTALL.OS2
and put the patch as OS2_tmpFix.dif.gz somewhere? (Please do not apply.) As it
seems, we have quite a lot of people who are accustomed to always
Hi,
Lars or Jean-Marc: Could you just cut cut and paste the following recipe by
Shigeru to the beginning of the OS/2-cookbook:
INSTALL.OS2
and put the patch as OS2_tmpFix.dif.gz somewhere? (Please do not apply.) As it
seems, we have quite a lot of people who are accustomed to always
On Tue, 11 Apr 2000 14:26:17 -0700 (PDT), [EMAIL PROTECTED]
wrote:
On 11 Apr 2000, Jean-Marc Lasgouttes wrote:
Mike It's merely to give people a quick way to search for things when
Mike it isn't obvious which doc to look at (e.g. how do I set up a
Mike printer?). When cross-document searching
On Tue, 11 Apr 2000 14:26:17 -0700 (PDT), [EMAIL PROTECTED]
wrote:
>On 11 Apr 2000, Jean-Marc Lasgouttes wrote:
>> Mike> It's merely to give people a quick way to search for things when
>> Mike> it isn't obvious which doc to look at (e.g. how do I set up a
>> Mike> printer?). When cross-document
On 30 Mar 2000 15:45:45 +0200, Jean-Marc Lasgouttes wrote:
I did not find
anything in the standard about putenv(), though.
putenv() is proprietary to 4.2 BSD and derived systems (like SunOS),
saw all kinds of funny prototypes.
Others have setenv(). Others neither. GNU software often uses bad
On 30 Mar 2000 15:45:45 +0200, Jean-Marc Lasgouttes wrote:
> I did not find
>anything in the standard about putenv(), though.
putenv() is proprietary to 4.2 BSD and derived systems (like SunOS),
saw all kinds of funny prototypes.
Others have setenv(). Others neither. GNU software often uses
On Sun, 30 Jan 2000 23:06:39 -0800, Karl Nelson wrote:
One last suggestion is to rename sigc++config.h sigc++/config.h
in all the headers so that you don't need to include sigc++
in your include paths. (and of course make the corresponding
rename in the configure.in.)
Hi,
once again I'd
On Sun, 30 Jan 2000 23:06:39 -0800, Karl Nelson wrote:
>One last suggestion is to rename sigc++config.h sigc++/config.h
>in all the headers so that you don't need to include sigc++
>in your include paths. (and of course make the corresponding
>rename in the configure.in.)
Hi,
once again
On Thu, 27 Jan 2000 11:47:55 +1000 (GMT+1000), Allan Rae wrote:
The first draft of libsigc++ integration uses a slightly modified version
of the libsigc++ configure.in in the sigc++ directory. Hmmm, does NT let
you have a directory called "sigc++"? What about OS/2?
OS/2-HPFS (the standard):
On Thu, 27 Jan 2000 12:49:03 -0800, Karl Nelson wrote:
On Thu, 27 Jan 2000 11:47:55 +1000 (GMT+1000), Allan Rae wrote:
The first draft of libsigc++ integration uses a slightly modified version
of the libsigc++ configure.in in the sigc++ directory. Hmmm, does NT let
you have a directory
On Thu, 27 Jan 2000 11:47:55 +1000 (GMT+1000), Allan Rae wrote:
>The first draft of libsigc++ integration uses a slightly modified version
>of the libsigc++ configure.in in the sigc++ directory. Hmmm, does NT let
>you have a directory called "sigc++"? What about OS/2?
OS/2-HPFS (the
On Thu, 27 Jan 2000 12:49:03 -0800, Karl Nelson wrote:
>> On Thu, 27 Jan 2000 11:47:55 +1000 (GMT+1000), Allan Rae wrote:
>>
>> >The first draft of libsigc++ integration uses a slightly modified version
>> >of the libsigc++ configure.in in the sigc++ directory. Hmmm, does NT let
>> >you have a
On Thu, 13 Jan 2000 12:33:40 +1000 (GMT+1000), Allan Rae wrote:
[ here's my slightly modified version of Martin's PR]
[Don't want to much otherwise we won't have anything new to say for the
1.2.0 release PR]
LyX is an advanced open-source document processor running on many Unix
platforms and
On 13 Jan 2000 16:33:24 +0100, Jean-Marc Lasgouttes wrote:
"Lars" == Lars Gullik Bj°nnes [EMAIL PROTECTED] writes:
Lars | Maybe the right solution is to see which of these header files
Lars are needed | to make FD_ZERO work: sys/time.h, stdlib.h,
Lars strings.h. (After all, it is | FD_ZERO we
On 13 Jan 2000 17:43:29 +0100, Lars Gullik Bj°nnes wrote:
Jean-Marc Lasgouttes [EMAIL PROTECTED] writes:
| "Lars" == Lars Gullik Bj°nnes [EMAIL PROTECTED] writes:
|
| Lars The problem is not C library functions, but "UNIX" functions
| Lars declared in C headers. (IMHO a mistake, but now we
On Thu, 13 Jan 2000 12:33:40 +1000 (GMT+1000), Allan Rae wrote:
>
>[ here's my slightly modified version of Martin's PR]
>[Don't want to much otherwise we won't have anything new to say for the
> 1.2.0 release PR]
>
>LyX is an advanced open-source document processor running on many Unix
On 13 Jan 2000 16:33:24 +0100, Jean-Marc Lasgouttes wrote:
>> "Lars" == Lars Gullik Bj°nnes <[EMAIL PROTECTED]> writes:
>
>Lars> | Maybe the right solution is to see which of these header files
>Lars> are needed | to make FD_ZERO work: sys/time.h, stdlib.h,
>Lars> strings.h. (After all, it
On 13 Jan 2000 17:43:29 +0100, Lars Gullik Bj°nnes wrote:
>Jean-Marc Lasgouttes <[EMAIL PROTECTED]> writes:
>
>| > "Lars" == Lars Gullik Bj°nnes <[EMAIL PROTECTED]> writes:
>|
>| Lars> The problem is not C library functions, but "UNIX" functions
>| Lars> declared in C headers. (IMHO a
On Wed, 12 Jan 2000 13:58:53 -0500, R. Lindsay Todd wrote:
At 12:38 PM 1/12/00 +0100, Jean-Marc Lasgouttes wrote:
"Lindsay" == R Lindsay Todd [EMAIL PROTECTED] writes:
Until yesterday, I would have said that _all_ systems except solaris7
use const char* ;) I have added some code in configure
On Wed, 12 Jan 2000 13:58:53 -0500, R. Lindsay Todd wrote:
>At 12:38 PM 1/12/00 +0100, Jean-Marc Lasgouttes wrote:
>> > "Lindsay" == R Lindsay Todd <[EMAIL PROTECTED]> writes:
>>
>>Until yesterday, I would have said that _all_ systems except solaris7
>>use const char* ;) I have added some
On 23 Dec 1999 20:22:39 +0100, Lars Gullik Bj°nnes wrote:
|
| Some time ago I suggested to use 'static inline' to break fn's up. I
| think this should work without of introducing fn call overhead.
inlining is one of the fings that really slows a compilation...
I see... Re-inlining fn's
On 23 Dec 1999 20:22:39 +0100, Lars Gullik Bj°nnes wrote:
>|
>| Some time ago I suggested to use 'static inline' to break fn's up. I
>| think this should work without of introducing fn call overhead.
>
>inlining is one of the fings that really slows a compilation...
I see... Re-inlining fn's
On 22 Dec 1999 14:33:03 +0100, Lars Gullik Bj°nnes wrote:
"Andre' Poenitz" [EMAIL PROTECTED] writes:
| of virtual memory. The gcc/egcs faq has very 'helpful' recommendations:
|
|
| Optimize less (or dont't optimize at all), use only small
| functions.
|
| Well. The second part *is*
On 22 Dec 1999 14:33:03 +0100, Lars Gullik Bj°nnes wrote:
>"Andre' Poenitz" <[EMAIL PROTECTED]> writes:
>
>| > of virtual memory. The gcc/egcs faq has very 'helpful' recommendations:
>| >
>| >
>| >Optimize less (or dont't optimize at all), use only small
>| > functions.
>|
>| Well. The
On Wed, 22 Dec 1999 12:59:28 +1000 (GMT+1000), Allan Rae wrote:
ven with 128MB of RAM and dual 400MHz processors it takes twice as long
to compile with SGI's string and _no_ exceptions as it does to compile lyx
with the lyx supplied string _and_ exceptions! (12minutes vs 6minutes)
The only
On Wed, 22 Dec 1999 12:59:28 +1000 (GMT+1000), Allan Rae wrote:
>ven with 128MB of RAM and dual 400MHz processors it takes twice as long
>to compile with SGI's string and _no_ exceptions as it does to compile lyx
>with the lyx supplied string _and_ exceptions! (12minutes vs 6minutes)
>The only
On 17 Dec 1999 10:26:31 +0100, Jean-Marc Lasgouttes wrote:
"Asger" == Asger K Alstrup Nielsen [EMAIL PROTECTED] writes:
Asger But then, even that is hard to find these days. So many other
Asger things come first. For instance, I'll going to drik a few
Asger beers tomorrow.
Do you mean
On 17 Dec 1999 10:26:31 +0100, Jean-Marc Lasgouttes wrote:
>> "Asger" == Asger K Alstrup Nielsen <[EMAIL PROTECTED]> writes:
>
>Asger> But then, even that is hard to find these days. So many other
>Asger> things come first. For instance, I'll going to drik a few
>Asger> beers tomorrow.
>
On Tue, 14 Dec 1999 13:38:02 +0100 (MET), Asger K. Alstrup Nielsen
wrote:
So my idea was something similar to this:
Setup each source file with a comment form just at the beginning,
something like the following and ask developers to fill them by and by
(I think this will work better than
On Tue, 14 Dec 1999 13:38:02 +0100 (MET), Asger K. Alstrup Nielsen
wrote:
>> So my idea was something similar to this:
>>
>> Setup each source file with a comment form just at the beginning,
>> something like the following and ask developers to fill them by and by
>> (I think this will work
On 13 Dec 1999 18:28:14 +0100, Lars Gullik Bj°nnes wrote:
| 1) In open source with a large number of rapidly changing contributors
| comments are crucial to attract new collaborators and to assure project
| survival when core contributors change. I think everybody knows
| examples of failures.
On 13 Dec 1999 18:28:14 +0100, Lars Gullik Bj°nnes wrote:
>
>| 1) In open source with a large number of rapidly changing contributors
>| comments are crucial to attract new collaborators and to assure project
>| survival when core contributors change. I think everybody knows
>| examples of
On Sun, 05 Dec 1999 21:01:48 +, Duncan Simpson wrote:
cc'ed to LyX-list, because it's about LyX design:
lots snipped
Depending on the blocking or shared memory properties of vfork() is guaranteed
to burn you on at least one of the unicies out there.
? You mean older bsd clones
On Sun, 05 Dec 1999 21:01:48 +, Duncan Simpson wrote:
cc'ed to LyX-list, because it's about LyX design:
>
>
>> >Depending on the blocking or shared memory properties of vfork() is guaranteed
>> >to burn you on at least one of the unicies out there.
>>
>> ? You mean older bsd clones
On 03 Dec 1999 15:00:47 +0100, Jean-Marc Lasgouttes wrote:
There were however a few places where spaceless was actually used to
avoid spaces. I replaced it by a new function QuoteName() which adds
single quotes around the argument:
aa - 'aa'
JMarc's file - 'JMarc\'s file'
(now
On 4 Dec 1999 14:35:21 +0900, [EMAIL PROTECTED] wrote:
- fonts.dir/fonts.scale files in xfonts.tar.gz explicitely prohibits
X clients from accessing non ISO8859-1 characters in the fonts.
Try
xfd -fn -bluesky-lasy-medium-r-normal--0-0-0-0-m-0-iso8859-1
to see what I mean. I
On Sat, 4 Dec 1999 14:22:34 +0100 (MET), Asger K. Alstrup Nielsen
wrote:
It's easier (IMO) to use the exec calls.
It is easy to change in the new LyX code:
The system() call is done in the SystemCalls framework.
This framework (originally introduced by Bernhard a long time ago,
and enhanced
On 25 Nov 1999 02:48:49 +0100, Lars Gullik Bj°nnes wrote:
| Well, in the old dll version I had to export some uninitialized
| globals, what I did not like.
Do you have a list of them? We should not have uninitialized globals.
Unfortunately I did not keep a list. I think 1.0.4 finally got rid
On 03 Dec 1999 15:00:47 +0100, Jean-Marc Lasgouttes wrote:
>There were however a few places where spaceless was actually used to
>avoid spaces. I replaced it by a new function QuoteName() which adds
>single quotes around the argument:
>aa -> 'aa'
>JMarc's file -> 'JMarc\'s file'
On 4 Dec 1999 14:35:21 +0900, [EMAIL PROTECTED] wrote:
> - fonts.dir/fonts.scale files in xfonts.tar.gz explicitely prohibits
> X clients from accessing non ISO8859-1 characters in the fonts.
> Try
>xfd -fn -bluesky-lasy-medium-r-normal--0-0-0-0-m-0-iso8859-1
> to see what I mean.
On Sat, 4 Dec 1999 14:22:34 +0100 (MET), Asger K. Alstrup Nielsen
wrote:
>> It's easier (IMO) to use the exec calls.
>
>It is easy to change in the new LyX code:
>
>The system() call is done in the SystemCalls framework.
>
>This framework (originally introduced by Bernhard a long time ago,
>and
On 25 Nov 1999 02:48:49 +0100, Lars Gullik Bj°nnes wrote:
>| Well, in the old dll version I had to export some uninitialized
>| globals, what I did not like.
>
>Do you have a list of them? We should not have uninitialized globals.
Unfortunately I did not keep a list. I think 1.0.4 finally got
On 23 Nov 1999 15:45:47 +0100, Lars Gullik Bj°nnes wrote:
The "experimental" use of libtool works for linux, and I have not seen
any failure reports from other archs yet.
I suspect that when libtool is used in "static" mode as it is now, we
should not have large problems on any system. However
On 24 Nov 1999 20:35:05 +0100, Lars Gullik Bj°nnes wrote:
| You can use the EMXEXP tool to export all global functions and all
| initialized global variables.
| (And even the uninitialized, but this is often problematic: Please
| initialize ALL global variables to a completely defined state and
On 23 Nov 1999 15:45:47 +0100, Lars Gullik Bj°nnes wrote:
>
>The "experimental" use of libtool works for linux, and I have not seen
>any failure reports from other archs yet.
>
>I suspect that when libtool is used in "static" mode as it is now, we
>should not have large problems on any system.
On 24 Nov 1999 20:35:05 +0100, Lars Gullik Bj°nnes wrote:
>| You can use the EMXEXP tool to export all global functions and all
>| initialized global variables.
>| (And even the uninitialized, but this is often problematic: Please
>| initialize ALL global variables to a completely defined state
On Mon, 15 Nov 1999 12:11:49 MET, Andre' Poenitz wrote:
Depends. It makes the executable slimmer if only one frontend is linked
in at a time and it does not create dependencies on libraries you do not
need/want/have. Personally I am in favour of having a 'kernel library'
that contains all real
On Mon, 15 Nov 1999 12:11:49 MET, Andre' Poenitz wrote:
>Depends. It makes the executable slimmer if only one frontend is linked
>in at a time and it does not create dependencies on libraries you do not
>need/want/have. Personally I am in favour of having a 'kernel library'
>that contains all
On Wed, 13 Oct 1999 17:20:24 +0100, Arnd Hanses wrote:
On 13 Oct 1999 11:19:07 +0200, Jean-Marc Lasgouttes wrote:
"Arnd" == Arnd Hanses [EMAIL PROTECTED] writes:
Arnd Hi, some spurious error messages with LyX 1.04 and lang=de
Arnd (de_menus.bind). In de_menus.bind the Buffer-Expor
On Wed, 13 Oct 1999 17:20:24 +0100, Arnd Hanses wrote:
>On 13 Oct 1999 11:19:07 +0200, Jean-Marc Lasgouttes wrote:
>
>>>>>>> "Arnd" == Arnd Hanses <[EMAIL PROTECTED]> writes:
>>
>>Arnd> Hi, some spurious error messages with LyX
On Fri, 12 Nov 1999 12:59:03 MET, Andre' Poenitz wrote:
The commandline interface does exactly the same, of course the painter
is much simpler in this case, it just produces some text describing the
current state. But this is a way to achieve GUI
independence: Everything up to and including the
On Fri, 12 Nov 1999 10:55:08 +0100 (MET), Asger K. Alstrup Nielsen
wrote:
Now, where do we go from here?
Can we handle this very extremely hyper-super-difficult problem that
is completely and utterly impossible to solve?
Of course we can not, so let's just keep arguing that ; should be
On Fri, 12 Nov 1999 12:59:03 MET, Andre' Poenitz wrote:
>The commandline interface does exactly the same, of course the painter
>is much simpler in this case, it just produces some text describing the
>current state. But this is a way to achieve GUI
>independence: Everything up to and including
On Fri, 12 Nov 1999 10:55:08 +0100 (MET), Asger K. Alstrup Nielsen
wrote:
>Now, where do we go from here?
>
>Can we handle this very extremely hyper-super-difficult problem that
>is completely and utterly impossible to solve?
>
>Of course we can not, so let's just keep arguing that ; should be
On 12 Nov 1999 01:28:01 +0100, Lars Gullik Bj°nnes wrote:
"Arnd Hanses" [EMAIL PROTECTED] writes:
| How can you be sure without ' 0x7f' for all the numerous different
| Double Byte encodings, commonly used for PC file systems in asian
| countries? Perhaps some of the asian langua
On 12 Nov 1999 01:28:01 +0100, Lars Gullik Bj°nnes wrote:
>"Arnd Hanses" <[EMAIL PROTECTED]> writes:
>
>| How can you be sure without '& 0x7f' for all the numerous different
>| Double Byte encodings, commonly used for PC file systems in asian
>| countries?
On 10 Nov 1999 04:03:47 +0100, Lars Gullik Bj°nnes wrote:
>One other thing we ofcourse can to is to just use _ for all chars that
>is not in the keep list already, and drop the 0x7f completely. That
>actually has some merits...
>
>| The reason for isalnum() in 1.0.4 and 1.1.1 was precisely to
On 02 Nov 1999 11:08:54 +0100, Jean-Marc Lasgouttes wrote:
"Lars" == Lars Gullik Bj°nnes [EMAIL PROTECTED] writes:
Lars First of all I wonder what we want to achieve with this
Lars functions. I understand that we want to avoid characters that
Lars can give us problems with filenames on
On 02 Nov 1999 11:08:54 +0100, Jean-Marc Lasgouttes wrote:
>> "Lars" == Lars Gullik Bj°nnes <[EMAIL PROTECTED]> writes:
>
>Lars> First of all I wonder what we want to achieve with this
>Lars> functions. I understand that we want to avoid characters that
>Lars> can give us problems with
On 19 Oct 1999 23:09:24 +0900, [EMAIL PROTECTED] wrote:
In an ideal world where you have plenty of time and diligence to maintain
any macro set (Imake, autoconf, tmake, ... whatever) actively for wide
portability, it might be desirable. In the real world, although you may
see quite noticeable
On 19 Oct 1999 17:40:35 +0200, Lars Gullik Bj°nnes wrote:
NO!! You have to check the standard before doing _ANY_ changes to
lyxstring.
|
| I'll fix this now and if you don't like it then you (you is general not JMarc;)
| can refix this and also all instances in the code where we allocate a
On 19 Oct 1999 23:09:24 +0900, [EMAIL PROTECTED] wrote:
>In an ideal world where you have plenty of time and diligence to maintain
>any macro set (Imake, autoconf, tmake, ... whatever) actively for wide
>portability, it might be desirable. In the real world, although you may
>see quite
On 19 Oct 1999 17:40:35 +0200, Lars Gullik Bj°nnes wrote:
>NO!! You have to check the standard before doing _ANY_ changes to
>lyxstring.
>
>|
>| I'll fix this now and if you don't like it then you (you is general not JMarc;)
>| can refix this and also all instances in the code where we allocate
On Sun, 17 Oct 1999 16:30:07 -0700, Kayvan A. Sylvan wrote:
On Sun, Oct 17, 1999 at 11:40:59PM +0200, Nils Jeppe wrote:
I just updated my base apckages to Redhat 6.1 packages. And now, my lyx is
hopelessly broken. It looks like the new tetex-* Packages moved around the
templates/styles etc.
On Sun, 17 Oct 1999 16:30:07 -0700, Kayvan A. Sylvan wrote:
>On Sun, Oct 17, 1999 at 11:40:59PM +0200, Nils Jeppe wrote:
>>
>> I just updated my base apckages to Redhat 6.1 packages. And now, my lyx is
>> hopelessly broken. It looks like the new tetex-* Packages moved around the
>>
On 16 Oct 1999 12:15:11 +0200, Lars Gullik Bj°nnes wrote:
"Arnd Hanses" [EMAIL PROTECTED] writes:
| On 15 Oct 1999 15:03:31 +0200, Lars Gullik Bj nnes wrote:
|
| It is often this wrapper that cannot have C++ linkage...the problem
| arises when passing pointer to functioncs th
On 16 Oct 1999 12:15:11 +0200, Lars Gullik Bj°nnes wrote:
>"Arnd Hanses" <[EMAIL PROTECTED]> writes:
>
>| On 15 Oct 1999 15:03:31 +0200, Lars Gullik Bj nnes wrote:
>|
>| >It is often this wrapper that cannot have C++ linkage...the problem
>| >arises when
Hi,
as follow up to my recent complaints about Rexx complexity, now some
links, so that I don't dissuade someone from Rexx.
Don't you ever dare to believe me, investigate yourself :-)
"Daniel Hellerstein. [EMAIL PROTECTED] wrote:
LINUX, DOS and WIN95 and NT versions of the free
Hi,
as follow up to my recent complaints about Rexx complexity, now some
links, so that I don't dissuade someone from Rexx.
Don't you ever dare to believe me, investigate yourself :-)
"Daniel Hellerstein. <[EMAIL PROTECTED]> wrote:
LINUX, DOS and WIN95 and NT versions of the free
For the record (OS/2 compilers):
==BEGIN FORWARDED MESSAGE==
Return-Path: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Message-Id: [EMAIL PROTECTED]
Received: from trancentral ([212.74.44.49]) by mail.primeline.ch
(Post.Office MTA v3.5.1 release 219
For the record (OS/2 compilers):
==BEGIN FORWARDED MESSAGE==
Return-Path: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Message-Id: [EMAIL PROTECTED]
Received: from trancentral ([212.74.44.49]) by mail.primeline.ch
(Post.Office MTA v3.5.1 release 219
On Thu, 14 Oct 1999 11:51:07 -0700 (PDT), [EMAIL PROTECTED]
wrote:
If you can come up with a better name, I think we'd all be happy to hear
it. "Extended" was just the best we could come up with at the time.
"Special F."
AH
For the record (OS/2 compilers):
==BEGIN FORWARDED MESSAGE==
>Return-Path: <[EMAIL PROTECTED]>
>Delivered-To: [EMAIL PROTECTED]
>Message-Id: <[EMAIL PROTECTED]>
>Received: from trancentral ([212.74.44.49]) by mail.primeline.ch
> (Post.Office MTA v3.5.1
For the record (OS/2 compilers):
==BEGIN FORWARDED MESSAGE==
>Return-Path: <[EMAIL PROTECTED]>
>Delivered-To: [EMAIL PROTECTED]
>Message-Id: <[EMAIL PROTECTED]>
>Received: from trancentral ([212.74.44.49]) by mail.primeline.ch
> (Post.Office MTA v3.5.1
On Thu, 14 Oct 1999 11:51:07 -0700 (PDT), [EMAIL PROTECTED]
wrote:
>If you can come up with a better name, I think we'd all be happy to hear
>it. "Extended" was just the best we could come up with at the time.
"Special F."
AH
On 14 Oct 1999 15:30:18 +0900, [EMAIL PROTECTED] wrote:
"Arnd Hanses" [EMAIL PROTECTED] wrote:
Those paths are absolutely fixed and must not be changed. (If you
fiddle with them, X might even refuse to start up).
This statement is simply untrue. The only thing fixed in X is th
On 14 Oct 1999 11:35:06 +0200, Jean-Marc Lasgouttes wrote:
"miyata" == miyata [EMAIL PROTECTED] writes:
miyata Jean-Marc Lasgouttes [EMAIL PROTECTED] wrote:
Maybe I missed something. What is used instead? Is the
autoconf/OS/2 good enough right now?
miyata Yes, at this moment. The problem
On 14 Oct 1999 15:56:04 +0200, Jean-Marc Lasgouttes wrote:
If I don't mix C into too much, maybe this is a bit helpful:
- static functions: I cannot declare them extern "C" too.
In the context of functions, 'extern' is the mutually exclusive
opposite of 'static', when the fn is internal to
On 14 Oct 1999 15:30:18 +0900, [EMAIL PROTECTED] wrote:
>"Arnd Hanses" <[EMAIL PROTECTED]> wrote:
>
>> Those paths are absolutely fixed and must not be changed. (If you
>> fiddle with them, X might even refuse to start up).
>
>This statement is s
On 14 Oct 1999 11:35:06 +0200, Jean-Marc Lasgouttes wrote:
>> "miyata" == miyata <[EMAIL PROTECTED]> writes:
>
>miyata> Jean-Marc Lasgouttes <[EMAIL PROTECTED]> wrote:
>>> Maybe I missed something. What is used instead? Is the
>>> autoconf/OS/2 good enough right now?
>
>miyata> Yes, at this
On 14 Oct 1999 15:56:04 +0200, Jean-Marc Lasgouttes wrote:
If I don't mix C into too much, maybe this is a bit helpful:
>- static functions: I cannot declare them extern "C" too.
In the context of functions, 'extern' is the mutually exclusive
opposite of 'static', when the fn is internal to
On 13 Oct 1999 05:41:35 +0900, [EMAIL PROTECTED] wrote:
The debug code
say size;'cmd/c dir chkconfig.sed';
checks if the arguments to stream() is all right, and it seems OK.
The stream() line is setting the pointer to the end of the file
Ahh... This might be my idiosyncrasy, but with Rexx I've
On Tue, 12 Oct 1999 17:20:51 -0400, Amir Karger wrote:
On Tue, Oct 12, 1999 at 04:39:22PM +0100, Arnd Hanses wrote:
What about simply pasting such non-obvious things turning up on the
list by and by into a short lyx-magics.faq?
Don't forget the faq jose created a year ago. I'm sure a lot
On 13 Oct 1999 11:19:07 +0200, Jean-Marc Lasgouttes wrote:
"Arnd" == Arnd Hanses [EMAIL PROTECTED] writes:
Arnd Hi, some spurious error messages with LyX 1.04 and lang=de
Arnd (de_menus.bind). In de_menus.bind the Buffer-Export bindings
Arnd override mysterious old bindings.
This o
On 13 Oct 1999 05:41:35 +0900, [EMAIL PROTECTED] wrote:
>The debug code
>say size;'cmd/c dir chkconfig.sed';
>checks if the arguments to stream() is all right, and it seems OK.
>The stream() line is setting the pointer to the end of the file
Ahh... This might be my idiosyncrasy, but with Rexx
On Tue, 12 Oct 1999 17:20:51 -0400, Amir Karger wrote:
>On Tue, Oct 12, 1999 at 04:39:22PM +0100, Arnd Hanses wrote:
>> What about simply pasting such non-obvious things turning up on the
>> list by and by into a short lyx-magics.faq?
>>
>
>Don't forget the faq j
On 13 Oct 1999 11:19:07 +0200, Jean-Marc Lasgouttes wrote:
>>>>>> "Arnd" == Arnd Hanses <[EMAIL PROTECTED]> writes:
>
>Arnd> Hi, some spurious error messages with LyX 1.04 and lang=de
>Arnd> (de_menus.bind). In de_menus.bind the Buffer->Exp
On 12 Oct 1999 15:23:04 +0200, Jean-Marc Lasgouttes wrote:
Keith macro-expanding the commands
Do you know that the math editor already supports user-defined macros?
Having complete macro support would of course be good, but it is not
easy.
Keith some other things that would be nice are
Hi,
some spurious error messages with LyX 1.04 and lang=de (de_menus.bind).
In de_menus.bind the Buffer-Export bindings override mysterious old
bindings.
# Key bindings for menus, both invisible and visible.
# Adapted to the german internationalisation 98-1-31 [EMAIL PROTECTED]
\bind "M-d e
On 12 Oct 1999 15:23:04 +0200, Jean-Marc Lasgouttes wrote:
>Keith> macro-expanding the commands
>
>Do you know that the math editor already supports user-defined macros?
>Having complete macro support would of course be good, but it is not
>easy.
>
>Keith> some other things that would be nice
1 - 100 of 488 matches
Mail list logo
