From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: Terminology in multi-tty primitives Date: Mon, 29 Dec 2008 00:31:09 -0500 Message-ID: <87prjbh7j6.fsf@cyd.mit.edu> References: <87zlihi05s.fsf@cyd.mit.edu> <878wq0j52s.fsf@cyd.mit.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1230528702 7208 80.91.229.12 (29 Dec 2008 05:31:42 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 29 Dec 2008 05:31:42 +0000 (UTC) Cc: emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 29 06:32:50 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1LHAkC-0005So-Ol for ged-emacs-devel@m.gmane.org; Mon, 29 Dec 2008 06:32:49 +0100 Original-Received: from localhost ([127.0.0.1]:47743 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LHAiz-0004TD-6P for ged-emacs-devel@m.gmane.org; Mon, 29 Dec 2008 00:31:33 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1LHAiZ-0004Lg-Hc for emacs-devel@gnu.org; Mon, 29 Dec 2008 00:31:07 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1LHAiX-0004Kw-V9 for emacs-devel@gnu.org; Mon, 29 Dec 2008 00:31:07 -0500 Original-Received: from [199.232.76.173] (port=58754 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1LHAiX-0004Kr-RQ for emacs-devel@gnu.org; Mon, 29 Dec 2008 00:31:05 -0500 Original-Received: from cyd.mit.edu ([18.115.2.24]:40812) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1LHAiT-0002Sg-Ed; Mon, 29 Dec 2008 00:31:01 -0500 Original-Received: by cyd.mit.edu (Postfix, from userid 1000) id EB0EA57E175; Mon, 29 Dec 2008 00:31:09 -0500 (EST) In-Reply-To: (Eli Zaretskii's message of "Sun, 28 Dec 2008 21:18:19 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.0.60 (gnu/linux) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:107371 Archived-At: Eli Zaretskii writes: > I think you are wrong about suspend making no sense on GUI terminals: > we have (in Emacs 23) suspend-frame that does work on GUI. Since GUI terminals are basically a connection to a graphical display, it doesn't (IMHO) make sense to talk about "suspending" the terminal. As long as the display connection is open, you can minimize/iconify frames on a GUI terminal individually. In contrast, suspending a text terminal actually does cause Emacs to relinquish control of the tty, and this operation acts on all frames on that terminal. > Anyway, the examples I gave were just that: examples. Here's another > example: we have make-frame-on-display, make-frame-on-tty, and > make-terminal-frame; and then we have make-frame that can do all of > the above. IMO, it's terribly confusing. make-terminal-frame should probably be renamed. This is an internal function that is not useful except when called from faces.el anyway. Maybe we should call it internal-make-tty-frame. > But again, maybe I'm the only one who is confused. My confusion is > exasperated by the fact that I cannot find any useful methodical way > to describe all these functions with partially overlapping > functionality in the ELisp manual. Suggestions welcome... As far as frame creation goes, there is just one primary Elisp interface for making frames: the function `make-frame'. The frame parameters passed to `make-frame' determine where the frame appears. The commands `make-frame-on-display' and `make-frame-on-tty' exist just for convenience: their purpose is to allow the user to interactively specify a display or tty name to `make-frame', using the minibuffer. Internal functions, such as x-create-frame-with-faces and tty-create-frame-with-faces, should not be documented in the Elisp manual.