Angus Leeming wrote:
2. Change the meaning of the (1.4.x) $$s placeholder from its current
meaning of support dir/scripts to simply support dir.
The drawback of this approach is that it breaks compatibility with old user
configuration files.
Why not place all scripts (including lyx2lyx, reLyX
On Tuesday 18 January 2005 10:54, Georg Baum wrote:
Why not place all scripts (including lyx2lyx, reLyX and noweb2lyx) in
support dir/scripts? I don't see why they need own directories.
Have you seen the code necessary for reLyX to work?
Basically you need to go through all the problems that
Jose' == Jose' Matos [EMAIL PROTECTED] writes:
Jose' On Tuesday 18 January 2005 10:54, Georg Baum wrote:
Why not place all scripts (including lyx2lyx, reLyX and noweb2lyx)
in support dir/scripts? I don't see why they need own
directories.
Jose' Have you seen the code necessary for reLyX to
Jean-Marc Lasgouttes wrote:
Jose' Basically you need to go through all the problems that Angus
Jose' had to consider for it to work in all the possible
Jose' configurations.
I am not sure it would be much more difficult than what we have now.
The only drawback I see with having reLyX and
Angus Leeming wrote:
If we really want to install these two scripts (reLyX, noweb2lyx) then
would it be possible to use symbolic links from /usr/local/bin to the
actual files?
I would prefer that. And the same applies for lyx2lyx. Installing them
in /usr/local/bin makes sense for expert users
Jose' Matos wrote:
Have you seen the code necessary for reLyX to work?
No.
If we start to create a library of python functions and/or modules we can
place that code in a single place but to replicate this to several
languages/projects is not fun. :-(
Indeed. If it is too complicated,
Angus Leeming wrote:
> 2. Change the meaning of the (1.4.x) "$$s" placeholder from its current
> meaning of "/scripts" to simply "".
The drawback of this approach is that it breaks compatibility with old user
configuration files.
Why not place all scripts (including lyx2lyx, reLyX and noweb2lyx)
On Tuesday 18 January 2005 10:54, Georg Baum wrote:
> Why not place all scripts (including lyx2lyx, reLyX and noweb2lyx) in
> /scripts? I don't see why they need own directories.
Have you seen the code necessary for reLyX to work?
Basically you need to go through all the problems that Angus had
> "Jose'" == Jose' Matos <[EMAIL PROTECTED]> writes:
Jose'> On Tuesday 18 January 2005 10:54, Georg Baum wrote:
>> Why not place all scripts (including lyx2lyx, reLyX and noweb2lyx)
>> in /scripts? I don't see why they need own
>> directories.
Jose'> Have you seen the code necessary for
Jean-Marc Lasgouttes wrote:
> Jose'> Basically you need to go through all the problems that Angus
> Jose'> had to consider for it to work in all the possible
> Jose'> configurations.
>
> I am not sure it would be much more difficult than what we have now.
> The only drawback I see with having
Angus Leeming wrote:
> If we really want to install these two scripts (reLyX, noweb2lyx) then
> would it be possible to use symbolic links from /usr/local/bin to the
> actual files?
I would prefer that. And the same applies for lyx2lyx. Installing them
in /usr/local/bin makes sense for expert
Jose' Matos wrote:
> Have you seen the code necessary for reLyX to work?
No.
> If we start to create a library of python functions and/or modules we can
> place that code in a single place but to replicate this to several
> languages/projects is not fun. :-(
Indeed. If it is too complicated,
On Monday 17 January 2005 19:37, Angus Leeming wrote:
...
Not only will this mean that things will work under Windows, but it will
also mean that they'll work on *nix when we're using an uninstalled
version of LyX.
Thoughts?
(I don't think that it matters that reLyX is slated to be retired.
On Monday 17 January 2005 19:37, Angus Leeming wrote:
...
> Not only will this mean that things will work under Windows, but it will
> also mean that they'll work on *nix when we're using an uninstalled
> version of LyX.
>
> Thoughts?
>
> (I don't think that it matters that reLyX is slated to be
14 matches
Mail list logo
