Re: address@hidden: Re: emacsclient additional arguments buried]

[Chong Yidong]

Richard Stallman <address@hidden> writes:

> Would someone please fix this, then ack?
>
> From: Dan Jacobson <address@hidden>
> Subject: Re: emacsclient additional arguments buried
> To: address@hidden
> Cc: address@hidden
>
>>     Hurmf, emacsclient -n a b c causes the additional arguments to be
>>     buried. The second argument should be right there at the
>>     switch-to-buffer prompt. Additional arguments not far behind too on
>>     the buffer list.
>
> rms> I don't understand.
>
> emacsclient works fine, except when you try it with more than one
> argument. When you do that, the additional arguments after the first
> end up bury-buffer'ed, whereas one might expect them near the top of
> the buffer list. OK, no big deal...there is a Debian emacsclient man
> page. Maybe what should happen when one gives more than one file
> argument to emacsclient should be documented.

What exactly needs to be done here?  If we don't want the additional
files to be buried, that is easy enough to do (one-liner patch below).
But I'm not sure that is the correct thing to do---it could be
construed as interfering with the server's buffer setup.  Note that
C-x # brings up the next client file correctly, even though they are
buried.

*** emacs/lisp/server.el.~1.112.~       2006-06-11 14:50:32.000000000 -0400
--- emacs/lisp/server.el        2006-07-04 10:10:57.000000000 -0400
***************
*** 426,432 ****
                           (write-file filen))))
                (setq server-existing-buffer t)
                (server-goto-line-column file))
!           (set-buffer (find-file-noselect filen))
            (server-goto-line-column file)
            (run-hooks 'server-visit-hook)))
        (unless nowait
--- 426,432 ----
                           (write-file filen))))
                (setq server-existing-buffer t)
                (server-goto-line-column file))
!           (find-file filen)
            (server-goto-line-column file)
            (run-hooks 'server-visit-hook)))
        (unless nowait