all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Eli Zaretskii <eliz@gnu.org>
Cc: rudalics@gmx.at, emacs-devel@gnu.org
Subject: Re: Uhm...  weird frame behaviour
Date: Mon, 12 Sep 2011 19:16:29 +0200	[thread overview]
Message-ID: <87d3f5r89e.fsf@wanadoo.es> (raw)
In-Reply-To: <83zki9wx4u.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 12 Sep 2011 19:20:17 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> > (#<frame emacs@qcore 0xf43590> #<frame F1 0xb6e7d0>)
>> > 
>> > I have no idea what frame F1 is. The only displayed frame is
>> > `emacs@qcore', which is what `emacsclient -c -n' creates.
>> 
>> Frames whose names are F1, F2, etc. are terminal frames.  Is it
>> possible that the demonic Emacs doesn't delete the initial terminal
>> frame, like an otherwise "normal" interactive session would?
>
> Answering my own question: yes, that's what happens.
>
> So Martin, I think other_visible_frames should be augmented for the
> fact that when IS_DAEMON is non-zero, there's one frame that is always
> there and does not constitute "other frames".

It seems more correct to fix the FRAME_VISIBLE_P test for that F1 frame.

OTOH:

emacs -Q

M-x server-start

(from a terminal): emacsclient -c -nw

(on the emacs' X frame): M-x delete-windows-on (select the currently
displayed buffer)

The graphical frame goes away. This is not correct, IMO.

Another example: running emacs as a server as above, connect from a
remote X server and create an emacs frame there. On one of the two
machines, M-x delete-windows-on (choose the currently displayed buffer.)
The frame on the other machine is deleted.

So this feature about smartly deleting frames is broken for some use
cases.



  reply	other threads:[~2011-09-12 17:16 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-10 19:14 Uhm... weird frame behaviour Lars Magne Ingebrigtsen
2011-09-10 22:13 ` Lars Magne Ingebrigtsen
2011-09-11  9:34   ` martin rudalics
2011-09-11 15:27     ` Lars Magne Ingebrigtsen
2011-09-11 15:44       ` Lars Magne Ingebrigtsen
2011-09-12  9:04         ` martin rudalics
2011-09-12  9:04       ` martin rudalics
2011-09-12 12:22         ` Óscar Fuentes
2011-09-12 12:47           ` martin rudalics
2011-09-12 13:32             ` Óscar Fuentes
2011-09-12 14:55               ` martin rudalics
2011-09-12 15:34                 ` Óscar Fuentes
2011-09-12 16:01                   ` Eli Zaretskii
2011-09-12 16:20                     ` Eli Zaretskii
2011-09-12 17:16                       ` Óscar Fuentes [this message]
2011-09-12 17:33                         ` Eli Zaretskii
2011-09-12 17:37                         ` Eli Zaretskii
2011-09-12 18:26                       ` martin rudalics
2011-09-12 19:12                         ` Eli Zaretskii
2011-09-13 11:59                           ` martin rudalics
2011-09-12 19:17                         ` Chong Yidong
2011-09-13 12:00                           ` martin rudalics
2011-09-13 12:45                             ` Óscar Fuentes
2011-09-13 18:28                               ` martin rudalics
2011-09-14  1:34                                 ` Óscar Fuentes
2011-09-13 15:41                             ` Chong Yidong
2011-09-13 18:27                               ` martin rudalics
2011-09-13 19:09                                 ` Chong Yidong
2011-09-12 12:31         ` Óscar Fuentes
2011-09-12 12:47           ` martin rudalics
2011-09-12 13:32         ` Andy Moreton
2011-09-12 13:39           ` Eli Zaretskii
2011-09-12 16:52             ` Lars Magne Ingebrigtsen
2011-09-13 18:28       ` martin rudalics
2011-09-13 20:26         ` Lars Magne Ingebrigtsen
2011-09-10 23:40 ` Rasmus
2011-09-10 23:42   ` Lars Magne Ingebrigtsen
2011-09-10 23:46   ` Rasmus
2011-09-10 23:53     ` Lars Magne Ingebrigtsen
2011-09-11  0:05 ` Óscar Fuentes

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87d3f5r89e.fsf@wanadoo.es \
    --to=ofv@wanadoo.es \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=rudalics@gmx.at \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.