From: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: [jidanni@jidanni.org: Re: emacsclient additional arguments buried]
Date: Tue, 04 Jul 2006 10:14:21 -0400 [thread overview]
Message-ID: <877j2te9tu.fsf@stupidchicken.com> (raw)
In-Reply-To: <E1Fvw6m-0007mK-Cx@fencepost.gnu.org> (Richard Stallman's message of "Thu, 29 Jun 2006 08:59:00 -0400")
Richard Stallman <rms@gnu.org> writes:
> Would someone please fix this, then ack?
>
> From: Dan Jacobson <jidanni@jidanni.org>
> Subject: Re: emacsclient additional arguments buried
> To: bug-gnu-emacs@gnu.org
> Cc: bortzmeyer@debian.org
>
>> 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
next prev parent reply other threads:[~2006-07-04 14:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 12:59 [jidanni@jidanni.org: Re: emacsclient additional arguments buried] Richard Stallman
2006-07-04 14:14 ` Chong Yidong [this message]
2006-07-04 16:35 ` Stefan Monnier
2006-07-04 20:52 ` Richard Stallman
2006-07-04 23:24 ` Chong Yidong
2006-07-09 14:12 ` Richard Stallman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877j2te9tu.fsf@stupidchicken.com \
--to=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).