unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Trent W. Buck" <trentbuck@gmail.com>
To: emacs-pretest-bug@gnu.org
Cc: rfrancoise@debian.org
Subject: PEBCAK
Date: Sat, 26 Jan 2008 17:04:24 +1100	[thread overview]
Message-ID: <20080126060317.GA4026@Clio.twb.ath.cx> (raw)
In-Reply-To: <20080126055132.GA3751@Clio.twb.ath.cx>


[-- Attachment #1.1: Type: text/plain, Size: 866 bytes --]

On Sat, Jan 26, 2008 at 04:51:32PM +1100, Trent W. Buck wrote:
> emacsclient will create a new X frame, EVEN WITHOUT the -c switch.
> 
> I do not want this.  Within M-x shell, I want emacsclient to open a
> buffer in the current frame and window, as it does under Emacs 22.
> 
> ## Why?  Because I'm connecting remotely to a Screen session that was
> ## started under X.  New X frames will appear on the original X
> ## display -- which could be a five hour drive away from the keyboard
> ## and display I'm actually sitting in front of *now*.  Furthermore, X
> ## might not even be running anymore -- my Screen sessions persist
> ## across my X sessions.

Ignore that, PEBCAK.  This does indeed work:

> Invoking emacsclient as "env -u DISPLAY emacsclient foo" does not
> help.

...I had modified the wrong line of my emacsclient wrapper script.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[-- Attachment #2: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

  reply	other threads:[~2008-01-26  6:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-26  5:51 23.0.50; mtty emacsclient confused by dumb terminal & DISPLAY Trent W. Buck
2008-01-26  6:04 ` Trent W. Buck [this message]
2008-01-26 19:10 ` Stefan Monnier
2008-01-27  0:44 ` Richard Stallman
2008-01-27  1:43   ` Stefan Monnier

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=20080126060317.GA4026@Clio.twb.ath.cx \
    --to=trentbuck@gmail.com \
    --cc=emacs-pretest-bug@gnu.org \
    --cc=rfrancoise@debian.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).