From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Juanma Barranquero Newsgroups: gmane.emacs.bugs Subject: bug#6468: A couple of problem related to frame raising (partly w32) Date: Sun, 20 Jun 2010 01:58:54 +0200 Message-ID: References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: dough.gmane.org 1276993743 12246 80.91.229.12 (20 Jun 2010 00:29:03 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Sun, 20 Jun 2010 00:29:03 +0000 (UTC) Cc: 6468@debbugs.gnu.org To: Lennart Borgman Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Sun Jun 20 02:28:59 2010 connect(): No such file or directory Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1OQ8PB-0001fv-Go for geb-bug-gnu-emacs@m.gmane.org; Sun, 20 Jun 2010 02:28:57 +0200 Original-Received: from localhost ([127.0.0.1]:43791 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OQ8PA-0002Nu-Pi for geb-bug-gnu-emacs@m.gmane.org; Sat, 19 Jun 2010 20:28:56 -0400 Original-Received: from [140.186.70.92] (port=39204 helo=eggs.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1OQ8P3-0002Nj-Ox for bug-gnu-emacs@gnu.org; Sat, 19 Jun 2010 20:28:51 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.69) (envelope-from ) id 1OQ8P2-0006St-H3 for bug-gnu-emacs@gnu.org; Sat, 19 Jun 2010 20:28:49 -0400 Original-Received: from debbugs.gnu.org ([140.186.70.43]:50194) by eggs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OQ8P2-0006So-EU for bug-gnu-emacs@gnu.org; Sat, 19 Jun 2010 20:28:48 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.69) (envelope-from ) id 1OQ7xD-0003fr-CR; Sat, 19 Jun 2010 20:00:03 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Juanma Barranquero Original-Sender: debbugs-submit-bounces@debbugs.gnu.org Resent-To: owner@debbugs.gnu.org Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 20 Jun 2010 00:00:03 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 6468 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 6468-submit@debbugs.gnu.org id=B6468.127699196114100 (code B ref 6468); Sun, 20 Jun 2010 00:00:03 +0000 Original-Received: (at 6468) by debbugs.gnu.org; 19 Jun 2010 23:59:21 +0000 Original-Received: from localhost ([127.0.0.1] helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OQ7wW-0003fN-MO for submit@debbugs.gnu.org; Sat, 19 Jun 2010 19:59:20 -0400 Original-Received: from mail-fx0-f44.google.com ([209.85.161.44]) by debbugs.gnu.org with esmtp (Exim 4.69) (envelope-from ) id 1OQ7wU-0003fI-Lx for 6468@debbugs.gnu.org; Sat, 19 Jun 2010 19:59:19 -0400 Original-Received: by fxm19 with SMTP id 19so1355052fxm.3 for <6468@debbugs.gnu.org>; Sat, 19 Jun 2010 16:59:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:cc:content-type; bh=qoYD7uLH4WJrG4/v2kzhMRFfRwW+rqfhXOAmVvHHiEE=; b=kl+kHXt7gAu2BbbIFjvzt9IQq8IPDP7JCskCVNQmU/ho7cpeYPf8fVyPrx7BNdf/r/ Q1ivD+9eb0EBM77m/5jISlyHtuCQkJEhYF4puNSAyhFs8LgDTgZZpkloCLVx2bYJKioh hsGfhqMyGUogmfEXDEHHvgC/PQ6MIywxsgGxk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=CVh02iBeuYqJLO8tCccUXF6otszp5STa9l9ACUowjEhFzMCvI8xg75keAKZ20yVlK/ mNF10EBmWgCBxBXnA9GM8Ci5xkML5pzsh9GJcbOdAuABeazeOOweS0Me6wsIGGOwjpYq h9eHFJqegEic3j6N5XNCXiNblg8BERZ++4c4E= Original-Received: by 10.102.15.22 with SMTP id 22mr986550muo.7.1276991954154; Sat, 19 Jun 2010 16:59:14 -0700 (PDT) Original-Received: by 10.204.24.129 with HTTP; Sat, 19 Jun 2010 16:58:54 -0700 (PDT) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.11 Precedence: list Resent-Date: Sat, 19 Jun 2010 20:00:03 -0400 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:37893 Archived-At: On Sun, Jun 20, 2010 at 01:36, Lennart Borgman wrote: > I am never surprised by that. When I am telling about a complicated > problem I am merely asking for a starting point in the discussion. > Have others seen similar problems? Do they have any guesses? Have they > tried to investigate some part of the problem? IMHO, sometimes you fail to explain the problem to such a point that it is difficult for other people to know whether they have also experienced it. > This is not about the internals of redisplay. It is about the logic > between narrow_to_region etc and redisplay. I don't think Eli's knowledge is limited to the "internals of redisplay". > I think both of us has tried the best we can but we have got stuck at > this moment. That, I can understand. What I do not understand is that then you switch to accusing people of wasting your time, or not wanting your patches, or not wanting to take the trouble to understand, etc. etc. > But it does not help if you say that Eli understands the > problem better. I am sure Eli understands the display engine better > now, but it is only partly involved. Oh, it can be of help if it makes you think that perhaps (not necessarily, but perhaps) he's on the right track and you are not. I've seen him ask you, twice, to try something after reverting one of your patches, and I don't think you obliged. > (What happens below is expected. Either you have seen those kind of > problems or not. It looks like you have not. No. But I don't try to do the things you do with frames, mainly because I very rarely use more than one. > For me this is just a > normal progress of the discussion. Is it not that for you?) Seems like a non sequitur. What is a normal progress of the discussion? > I have been trying to get a frame to become the foreground window in a > certain situation but so far failed. There are many things involved so > I am not sure of why it fails. And it does not always fail. I even > believed I found out how to get it to work but after that it has > always failed. > > I have tried the normal things like raise-frame, > set-frame-select-input-focus, make-frame-visible, redisplay. And I > have tried to do it in a timer. (I think when it worked I had a rather > large timeout in the timer.) > > When doing some logging I have seen that the frame setup does not seem > to be finished. The frame is created, the buffer I want to display is > somehow tied to the frame, but it does not yet have a window. I have > no idea whether this is a part of the problem I have or not. All of this seems like a recipe that you *could* send to this thread. "Look, I tried with this code here, run in such-and-such circumstances, and sometimes it works, sometimes it doesn't". It would be clearer than trying to extract meaning from descriptions and paraphrases. > I try to open a new frame to edit a text area in Firefox using It's > All Text. This calls emacsclient without wait (since otherwise it > hangs Firefox). > > I have set server-raise-frame to nil since I want to create a special > frame for editing and just raise that. If server-raise-frame is > non-nil this will raise the current frame in Emacs instead. > > So now in server-window I just create a frame and try to raise that. > And I can't get it to work. > > I have a variable pointing to the frame and it looks ok so I know it is there. Are you sure this isn't just Windows trying to keep Emacs from stealing the focus? You know, AllowSetForegroundWindow and that stuff. I've sometimes seen emacsclient call Emacs from a console (4NT) and Emacs not getting the focus because 4NT (and so emacsclient) just happened to lose the focus before calling AllowSetForegroundWindow. > Ah, shit. Thanks. (I am too unused to reading C code.) Glad to help. Juanma