LADI
/
ladish
1
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Switched LASH_START_SERVER for LASH_NO_START_SERVER (with opposite semantics), 

for consistency with Jack and to lower learning curve.


git-svn-id: svn://svn.savannah.nongnu.org/lash/trunk@48 1de19dc7-4e3f-0410-a61d-eddf686bf0b7
This commit is contained in:
Dave Robillard 2006-10-17 08:01:23 +00:00
parent 4aee0eb9de
commit 3dcf4ba517
4 changed files with 35 additions and 25 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
NEWS
View File

@ -1,3 +1,6 @@
0.5.3:
* switch LASH_START_SERVER for LASH_NO_START_SERVER with opposite semantics
0.5.2:
* support for building without ALSA
* server auto-launching bug fixes

26
docs/lash-manual.info
View File

@ -280,24 +280,28 @@ listening for connections from clients. It doesn't do much else.
`lash_panel' program (though this is not necessary, and it can be
started later at any time).
The environment variable `LASH_START_SERVER' can be set to have any
LASH client automatically start the server if one isn't already running.
Doing this you can simply put `lash_panel' (or any other LASH client)
in your applications menu and have LASH automatically work without
having to remember to start the server manually.
Unless the environment variable `LASH_NO_START_SERVER' is set any
LASH client will automatically start the server if one isn't already running.
Doing this you can simply run applications normally (e.g. from a terminal or
your Applications menu) and have LASH automatically work without having to
remember to start the server manually.
Starting the server can be disabled by specifying the
Starting the server can also be disabled by specifying the
`--lash-no-start-server' option on the client's command line.
If you're using a Bourne compatible shell like `bash' (if you don't
know, you probably are) you can enable auto-start with the following
know, you probably are) you can disable auto-start with the following
command:
`export LASH_START_SERVER=1'
`export LASH_NO_START_SERVER=1'
Some applications may also choose themselves whether to start the
server (or have a configurable option).
Disabling the automatic start is not recommended to gain the abilities LASH
intends to provide. With auto launching enabled you don't need to worry about
LASH until you actually want to save a session.
If you would like to always have the server started, put that
command in the file ~/.bashrc (or in /etc/profile if you are root and
want it set system wide) to have it run whenever a new shell is started.
6.1.1.2 A client connection
...........................

29
docs/lash-manual.texi.in
View File

@ -306,23 +306,26 @@ To keep track of what is happening with LASH, the user can run the
@command{lash_panel} program (though this is not necessary, and it can
be started later at any time).
The environment variable @code{LASH_START_SERVER} can be set to have any
LASH client automatically start the server if one isn't already running.
Doing this you can simply put @command{lash_panel} (or any other LASH
client) in your applications menu and have LASH automatically work without
having to remember to start the server manually.
Unless the environment variable @code{LASH_NO_START_SERVER} is set any
LASH client will automatically start the server if one isn't already running.
Doing this you can simply run applications normally (e.g. from a terminal or
your Applications menu) and have LASH automatically work without having to
remember to start the server manually.
Starting the server can be disabled by specifying the
@option{--lash-no-start-server} option on the client's command line.
Starting the server can also be disabled by specifying the
@command{--lash-no-start-server} option on the client's command line.
If you're using a Bourne compatible shell like @command{bash} (if you don't
know, you probably are) you can enable auto-start with the following command:
If you're using a Bourne compatible shell like @code{bash} (if you don't
know, you probably are) you can disable auto-start with the following
command:
@command{export LASH_START_SERVER=1}
@command{export LASH_NO_START_SERVER=1}
If you would like to always have the server started, put that command in the
file ~/.bashrc (or in /etc/profile if you are root and want it set system
wide) to have it run whenever a new shell is started.
Some applications may also choose themselves whether to start the
server (or have a configurable option), however risabling the automatic
start (by any method) is not recommended if you want to gain the benefits of
LASH. With auto launching enabled you don't need to worry about
LASH until you actually want to save a session.
@subsubsection A client connection

2
liblash/lash.c
View File

@ -186,7 +186,7 @@ lash_init(const lash_args_t * args,
case something must be broken if we can't connect */
if ( !(client_flags & LASH_No_Start_Server) ) {
lash_args_get_id(args, id);
if (err && getenv("LASH_START_SERVER") != NULL && uuid_is_null(id)) {
if (err && getenv("LASH_NO_START_SERVER") == NULL && uuid_is_null(id)) {
LASH_DEBUGARGS("%s: trying to start new LASH server\n",
__FUNCTION__);