Re: confused about emacs 23 in daemon mode

[Bruno Barbier <bruno.barbier.cs@begin_dom.orange.fr.end_dom>]

On 2009-09-13, Daniel Pittman <daniel@rimspace.net> wrote:
> Tim X <timx@nospam.dev.null> writes:
>> Rodrigo Amestica <ramestica@gmail.com> writes:
>>
>>> it is so nice to have emacs starting so blazingly fast when using the
>>> daemon and emacsclient combination. However it seems that every other
>>> emacsclient I open is not an independent version of emacs and things get
>>> intermixed. I think that in emacs parlance the terminology is 'frame', all
>>> emacsclient instances are emacs frames.

Thanks to emacsclient, you only have one emacs. The fact that you get
a new frame or not is just a configuration setting.

   (describe-variable 'server-window)

I mean, the fact that things get intermixed is one goal of emacsclient
(the other one being fast start up).

>>> The main problems I have noticed under these circumstances is that 'C- h-i'
>>> seems to be shared by all frames such that browsing in one frame will make
>>> the others to move away from their own current info page.  

Type M-n to open a new independent info buffer.
And most jumping commands have a 'C-u' that jump into a new buffer.
      
    (info "(info)Create Info buffer")

>>> And the mayor
>>> show stopper is ECB. It seems that I cannot have 2 emacsclients running
>>> their own ECB session.

I would use one emacs by ECB and an other one for planning, taking
notes, etc.  You can then make emacsclient use the one you want or
setup only the third emacs as a server depending on your needs.

    From the emacs info manual:

    |    If there is more than one Emacs server running, you can specify a
    | server name with the `-s NAME' or `--socket-name=NAME' option to
    | `emacsclient'.  (This option is not supported on MS-Windows.)

    (info "(emacs)Invoking emacsclient")