unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Sascha Wilde <wilde@sha-bang.de>
To: "David De La Harpe Golden" <david.delaharpe.golden@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: emacsclient bug
Date: Mon, 04 Feb 2008 12:46:10 +0100	[thread overview]
Message-ID: <m2y7a1q70d.fsf@kenny.sha-bang.de> (raw)
In-Reply-To: <8e24944a0802021610v7f9e22ebv22c9403556f37b40@mail.gmail.com> (David De La Harpe Golden's message of "Sun, 3 Feb 2008 00:10:25 +0000")

"David De La Harpe Golden" <david.delaharpe.golden@gmail.com> wrote:

> On 31/01/2008, Sascha Wilde <wilde@sha-bang.de> wrote:
>> This stopped working with the new emacsclient version and `-d $DISPLAY
>> -c $f' doesn't help, because there is no shell involved which could
>> expand $DISPLAY.
>>
>
> But does it it still exist in the process' environment?

Sure it is.  The problem is that the latest changes caused emacsclient
to open a tty frame even with `-c' and a valid DISPLAY in the
environment.

> Maybe  emacsclient now just needs a -D option for "use X11 display
> found in DISPLAY env var" ? So you can do "emacsclient -D -c", say.

emacsclient -D -c
emacsclient: invalid option -- D

emacsclient only knows about -d, which _requires_ an argument of the
form HOST:SERVER or HOST:SERVER.SCREEN.

> or is firefox cleaning the env of its children?

No it doesn't and my setup used to work before the behavior of
emacsclient was changes...

cheers
sascha
-- 
Sascha Wilde
Well, *my* brain likes to think it's vastly more powerful than any
finite Turing machine but it hasn't proven that to me...
  -- Christopher Koppler in comp.lang.lisp




  reply	other threads:[~2008-02-04 11:46 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-17  0:07 emacsclient bug Len Trigg
2008-01-17 15:42 ` Stefan Monnier
2008-01-17 17:48   ` Len Trigg
2008-01-17 17:56   ` Len Trigg
2008-01-17 18:42     ` Stefan Monnier
2008-01-17 19:00       ` Len Trigg
2008-01-20 20:41         ` Stefan Monnier
2008-01-20 21:56           ` Len Trigg
2008-01-21  1:45             ` Stefan Monnier
2008-01-21  3:16               ` Len Trigg
2008-01-21  9:54                 ` Andreas Schwab
2008-01-21 15:52                 ` Stefan Monnier
2008-01-22 11:30                   ` Richard Stallman
2008-01-26 21:58                     ` Stefan Monnier
2008-01-27  2:06                       ` Dan Nicolaescu
     [not found]                       ` <ur9odb89g39.fsf@totally-fudged-out-message-id>
2008-01-27 15:41                         ` Dan Nicolaescu
2008-01-28  7:57                           ` KOBAYASHI Yasuhiro
2008-01-31 17:15                           ` Sascha Wilde
2008-02-03  0:10                             ` David De La Harpe Golden
2008-02-04 11:46                               ` Sascha Wilde [this message]
2008-02-04 14:56                                 ` David De La Harpe Golden
2008-02-04 15:04                                   ` David De La Harpe Golden
2008-02-04 17:33                                     ` Sascha Wilde
2008-02-06 17:29                             ` Stefan Monnier
2008-02-06 17:40                               ` Dan Nicolaescu
2008-02-06 19:31                                 ` Stefan Monnier
2008-02-07  0:44                                 ` Richard Stallman
2008-02-07  0:50                                   ` Leo
2008-02-07  1:00                                   ` Dan Nicolaescu
2008-02-07  9:03                                   ` Sascha Wilde
2008-02-08  4:16                                     ` Richard Stallman
2008-02-07  9:05                                 ` Sascha Wilde
2008-02-08 15:27                                 ` Stefan Monnier
2008-02-09 14:50                                   ` Sascha Wilde
2008-02-07  8:56                               ` Sascha Wilde
2008-02-04  4:57                           ` Leo
2008-01-27 16:03                       ` Richard Stallman
2008-01-20 21:56           ` Len Trigg

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=m2y7a1q70d.fsf@kenny.sha-bang.de \
    --to=wilde@sha-bang.de \
    --cc=david.delaharpe.golden@gmail.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).