emacs.bash?

emacs.bash?

[Chong Yidong]

Does anyone know what's the purpose of etc/emacs.bash, as opposed to
running `emacsclient -a emacs'?

Re: emacs.bash?

[Glenn Morris]

Chong Yidong wrote:

> Does anyone know what's the purpose of etc/emacs.bash, as opposed to
> running `emacsclient -a emacs'?

There is some discussion of this in bug#890 (perhaps this is what
prompted your question though).

Re: emacs.bash?

[Chong Yidong]

Glenn Morris <rgm@gnu.org> writes:

> Chong Yidong wrote:
>
>> Does anyone know what's the purpose of etc/emacs.bash, as opposed to
>> running `emacsclient -a emacs'?
>
> There is some discussion of this in bug#890 (perhaps this is what
> prompted your question though).

Thanks, now I remember that discussion.  I've removed the mention of
emacs.bash from the Emacs manual.

I've also rewritten the documentation of the Emacs server substantially.
If anyone is familiar with the Emacs server/client functionality, I
encourage you to take a look, and check if I screwed up anywhere.

Re: emacs.bash?

[Dan Nicolaescu]

Chong Yidong <cyd@stupidchicken.com> writes:

  > Glenn Morris <rgm@gnu.org> writes:
  > 
  > > Chong Yidong wrote:
  > >
  > >> Does anyone know what's the purpose of etc/emacs.bash, as opposed to
  > >> running `emacsclient -a emacs'?
  > >
  > > There is some discussion of this in bug#890 (perhaps this is what
  > > prompted your question though).
  > 
  > Thanks, now I remember that discussion.  I've removed the mention of
  > emacs.bash from the Emacs manual.

There's still a mention of it (and emacs.csh) in cmdargs.texi

  > I've also rewritten the documentation of the Emacs server substantially.
  > If anyone is familiar with the Emacs server/client functionality, I
  > encourage you to take a look, and check if I screwed up anywhere.

Looks good to me.
Maybe adding some info about `server-use-tcp' and `server-host' would be
useful too, it's hard to find out about those without reading the code.

Re: emacs.bash?

[Glenn Morris]

Chong Yidong wrote:

> I've removed the mention of emacs.bash from the Emacs manual.

I think this means lisp/resume.el should be moved to obsolete.

Re: emacs.bash?

[Chong Yidong]

Glenn Morris <rgm@gnu.org> writes:

>> I've removed the mention of emacs.bash from the Emacs manual.
>
> I think this means lisp/resume.el should be moved to obsolete.

Yes, it should.

Re: emacs.bash?

[Chong Yidong]

>   > I've also rewritten the documentation of the Emacs server substantially.
>   > If anyone is familiar with the Emacs server/client functionality, I
>   > encourage you to take a look, and check if I screwed up anywhere.
>
> Looks good to me.
> Maybe adding some info about `server-use-tcp' and `server-host' would be
> useful too, it's hard to find out about those without reading the code.

Is it generally useful to connect to the server via TCP?  Or is it
useful only on systems without local sockets?

Re: emacs.bash?

[Juanma Barranquero]

On Wed, Oct 29, 2008 at 16:36, Chong Yidong <cyd@stupidchicken.com> wrote:

> Is it generally useful to connect to the server via TCP?  Or is it
> useful only on systems without local sockets?

TCP allows connecting from remote machines (though you still need
access to the server file), and supports a very trivial scheme for
authentication. Other than that, there is no benefit in using it on
systems with local sockets.

             Juanma

Re: emacs.bash?

[Dan Nicolaescu]

Chong Yidong <cyd@stupidchicken.com> writes:

  > >   > I've also rewritten the documentation of the Emacs server substantially.
  > >   > If anyone is familiar with the Emacs server/client functionality, I
  > >   > encourage you to take a look, and check if I screwed up anywhere.
  > >
  > > Looks good to me.
  > > Maybe adding some info about `server-use-tcp' and `server-host' would be
  > > useful too, it's hard to find out about those without reading the code.
  > 
  > Is it generally useful to connect to the server via TCP? 

It is quite useful.  If $HOME is on NFS, then `server-use-tcp' = t puts the
server file in $HOME/.emacs.d/server/server.  
If on top of that you set `server-host' to $HOSTNAME, then you can
use emacsclient from all the hosts that NFS mount $HOME.

Re: emacs.bash?

[Chong Yidong]

"Juanma Barranquero" <lekktu@gmail.com> writes:

> On Wed, Oct 29, 2008 at 16:36, Chong Yidong <cyd@stupidchicken.com> wrote:
>
>> Is it generally useful to connect to the server via TCP?  Or is it
>> useful only on systems without local sockets?
>
> TCP allows connecting from remote machines (though you still need
> access to the server file), and supports a very trivial scheme for
> authentication. Other than that, there is no benefit in using it on
> systems with local sockets.

I see.  OK, I added documentation for server-use-tcp and server-host.