From: Dan Nicolaescu <dann@ics.uci.edu>
To: rms@gnu.org
Cc: emacs-devel@gnu.org
Subject: Re: [raman@users.sf.net: 23.0.50; Unable to launch emacsclient from shell buffers:]
Date: Wed, 19 Sep 2007 18:57:56 -0700 [thread overview]
Message-ID: <200709200157.l8K1vu40011335@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <E1IWSdT-0003Us-0i@fencepost.gnu.org> (Richard Stallman's message of "Sat\, 15 Sep 2007 04\:04\:15 -0400")
Richard Stallman <rms@gnu.org> writes:
> Would someone please DTRT, then ack?
This is not a problem. Invoking "emacsclient -c" in that situation
works. After the multi-tty merge emacsclient defaults to creating a
new frame. Stefan is working on changing the default to what it was
before the merge.
prev parent reply other threads:[~2007-09-20 1:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-15 8:04 [raman@users.sf.net: 23.0.50; Unable to launch emacsclient from shell buffers:] Richard Stallman
2007-09-20 1:57 ` Dan Nicolaescu [this message]
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=200709200157.l8K1vu40011335@oogie-boogie.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=emacs-devel@gnu.org \
--cc=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).