Hello!
Sorry for the long delay, real life took recently quite all my free
time.
On Wed, 30 Aug 2006 00:13:47 +0200, Faré wrote:
> On 29/08/06, Luca Capello <[EMAIL PROTECTED]> wrote:
>>> check_lisp_variable () {
>>> test -r /etc/cl-launchrc && . /etc/cl-launchrc
>>> test -r "$HOME/.cl-
Hello!
On Wed, 30 Aug 2006 01:38:30 +0200, Faré wrote:
> Due to popular request, I am working on an optional /etc/cl-launchrc
> feature for cl-launch.
[...]
> Also, the preferrence happens at script-creation time. At runtime,
> the variable $LISP is still all that matters -- should it not?
I test
I put on my site a cl-launch 1.87 deb that I believe fixes 384697.
Testers: Please test.
Uploaders: please upload.
[ François-René ÐVB Rideau | Reflection&Cybernethics | http://fare.tunes.org ]
If Java had true garbage collection, most programs would delete themselves
upon execution. -- Robert Se
Due to popular request, I am working on an optional /etc/cl-launchrc
feature for cl-launch.
Because I allow a --no-rc option (that is enabled by default for me,
you can use --rc by default), the contents of these file will be read
*after* the option processing.
A cl-launchrc file may contain stat
On 29/08/06, Luca Capello <[EMAIL PROTECTED]> wrote:
check_lisp_variable () {
test -r /etc/cl-launchrc && . /etc/cl-launchrc
test -r "$HOME/.cl-launchrc" && . "$HOME/.cl-launchrc"
test -n ${SOFTWARE_SYSTEM} && LISP=${SOFTWARE_SYSTEM}
}
I have several issues with such a patch:
(1
Hello!
On Sat, 26 Aug 2006 18:50:40 +0200, Luca Capello wrote:
> ATM the patch is quite dirty, because it uses grep and the BASH
> parameter substitution to assign the value, while the same function
> should be very simple as:
>
> check_lisp_variable () {
> test -r /etc/cl-launchrc && . /etc
I'm not sure we either need or want a /etc/cl-launchrc or a
~/.cl-launchrc. After all, the user (or root) may already export the
variable $LISP to override things at runtime (or at dump time),
whatever the --lisp or $LISPS variable be, unless explicitly prevented
with a --wrap argume
tags 384697 + patch
thanks
Hello Faré!
On Sat, 26 Aug 2006 06:08:39 +0200, Faré wrote:
> I'm not sure we either need or want a /etc/cl-launchrc or a
> ~/.cl-launchrc.
I still think that's the way to go, but obviously we need more
feedbacks from the other CL-Debian developers/users (especially Pe
On 25/08/06, Luca Capello <[EMAIL PROTECTED]> wrote:
Package: cl-launch
Version: 1.85-1
Severity: wishlist
I'm not sure we either need or want a /etc/cl-launchrc or a
~/.cl-launchrc. After all, the user (or root) may already export the
variable $LISP to override things at runtime (or at dump ti
Package: cl-launch
Version: 1.85-1
Severity: wishlist
Hello,
the background of this wishlist can be found on bug #384071 [1], I
created a new bug because I think the discussion was becoming
specific to CL-Launch and no more to StumpWM.
BTW, Xavier, I Cc:ed you because you were deeply involved in
10 matches
Mail list logo
