unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Subject: [jidanni@jidanni.org: Re: emacsclient additional arguments buried]
Date: Thu, 29 Jun 2006 08:59:00 -0400	[thread overview]
Message-ID: <E1Fvw6m-0007mK-Cx@fencepost.gnu.org> (raw)

Would someone please fix this, then ack?

------- Start of forwarded message -------
From: Dan Jacobson <jidanni@jidanni.org>
To: bug-gnu-emacs@gnu.org
Date: Wed, 28 Jun 2006 06:21:54 +0800
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: bortzmeyer@debian.org
Subject: Re: emacsclient additional arguments buried
X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=failed 
	version=3.0.4

>     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.


_______________________________________________
bug-gnu-emacs mailing list
bug-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnu-emacs
------- End of forwarded message -------

             reply	other threads:[~2006-06-29 12:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-29 12:59 Richard Stallman [this message]
2006-07-04 14:14 ` [jidanni@jidanni.org: Re: emacsclient additional arguments buried] Chong Yidong
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=E1Fvw6m-0007mK-Cx@fencepost.gnu.org \
    --to=rms@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).