emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Fwd: Mail delivery failed: returning message to sender]


From: Lennart Borgman (gmail)
Subject: [Fwd: Mail delivery failed: returning message to sender]
Date: Mon, 07 Jan 2008 21:27:59 +0100
User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666

I got this in return, see below for the actual message

-------- Original Message --------
Subject: Mail delivery failed: returning message to sender
Date: Mon, 07 Jan 2008 15:23:02 -0500
From: Mail Delivery System <address@hidden>
To: address@hidden

This message was created automatically by mail delivery software.

A message that you sent could not be delivered to one or more of its
recipients. This is a permanent error. The following address(es) failed:

  address@hidden
SMTP error from remote mail server after RCPT TO:<address@hidden>:
    host fencepost.gnu.org [140.186.70.10]: 550 unknown user

------ This is a copy of the message, including all the headers. ------

Return-path: <address@hidden>
Received: from Debian-exim by monty-python.gnu.org with spam-scanned (Exim 4.60)
        (envelope-from <address@hidden>)
        id 1JByUt-0007yN-98
        for address@hidden; Mon, 07 Jan 2008 15:23:02 -0500
Received: from ch-smtp01.sth.basefarm.net ([80.76.149.212])
        by monty-python.gnu.org with esmtps 
(TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32)
        (Exim 4.60)
        (envelope-from <address@hidden>)
        id 1JByUs-0007yB-Qw
        for address@hidden; Mon, 07 Jan 2008 15:22:59 -0500
Received: from c83-254-148-228.bredband.comhem.se ([83.254.148.228]:62003 helo=[127.0.0.1])
        by ch-smtp01.sth.basefarm.net with esmtp (Exim 4.68)
        (envelope-from <address@hidden>)
        id 1JByUq-0007fK-5e; Mon, 07 Jan 2008 21:22:57 +0100
Message-ID: <address@hidden>
Date: Mon, 07 Jan 2008 21:22:44 +0100
From: "Lennart Borgman (gmail)" <address@hidden>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.9) Gecko/20071031 Thunderbird/2.0.0.9 Mnenhy/0.7.5.666
MIME-Version: 1.0
To: address@hidden, Stefan Monnier <address@hidden>
Subject: Re: 23.0.50; DISPLAY env var bug on w32?
References: <address@hidden>
In-Reply-To: <address@hidden>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 080107-0, 2008-01-07), Outbound message
X-Antivirus-Status: Clean
X-Originating-IP: 83.254.148.228
X-Scan-Result: No virus found in message 1JByUq-0007fK-5e.
X-Scan-Signature: ch-smtp01.sth.basefarm.net 1JByUq-0007fK-5e ccbfddb287e6cf8ea97cbe46f403cd00
X-detected-kernel: by monty-python.gnu.org: Linux 2.6? (barebone, rare!)

Lennart Borgman (gmail) wrote:
I can not use emacsclient to open files unless I delete the environmental variable DISPLAY.

To reproduce the problem do

  emacs -Q
  M-x server-mode

Then from the command line try to open a file, for example

  emacsclient.exe COPYING

This fails with the message

  C:\emacs\u\080104\emacs\bin>emacsclient.exe COPYING
  Waiting for Emacs...
  *ERROR*: Don't know how to create a frame on window system x

It looks like several possible bugs to me. A call from emacsclient leads to

   server-process-filter

and since tty-name is nil this calls

   server-select-display

In this function there is a check

    (equal (frame-parameter (selected-frame) 'display) display))

This fails since (frame-parameter (selected-frame) 'display) returns "".
  I would expect it to return "localhost:0.0" in my case. The reason for
this is explained further below.

Now this leads to a call to

   make-frame-on-display

which finishes with a line at the bottom saying

   (make-frame `((window-system . x) (display . ,display) .
     ,parameters)))

The correct window-system seems to be 'w32 in my case, since that is
what works inf make-frame. The variable frame-creation-function-alist
used there is

   ((w32 . x-create-frame-with-faces)
    (nil . tty-create-frame-with-faces))

If I use this then the frame actually get the display property
"localhost:0.0" and that is why I believe that this is what it should
have from the beginning. So this is bug 1 here I believe.

But 2 is the hard coded value in the last line of make-frame-on-display.
It looks like window-system should be something different there.

When I try to find out what I see in server-process-filter some lines saying

                 ;; -window-system:  Open a new X frame.
                 ((equal "-window-system" arg)
                   (setq dontkill t)
                   (setq tty-name 'window-system))

Those are a bit surprising to me since I expect an analogous use of
something called "window-system" throughout the code. Obviously that is
not the case here.

And here I stop speculating because there might be some mistake in the
structure here. Someone who understands this code better than I do can
perhaps see more clearly what is needed.





reply via email to

[Prev in Thread] Current Thread [Next in Thread]