From: Eli Zaretskii <eliz@gnu.org>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: Terminology in multi-tty primitives
Date: Mon, 29 Dec 2008 21:26:54 +0200 [thread overview]
Message-ID: <uy6xyaikh.fsf@gnu.org> (raw)
In-Reply-To: <87prjbh7j6.fsf@cyd.mit.edu>
> From: Chong Yidong <cyd@stupidchicken.com>
> Cc: emacs-devel@gnu.org
> Date: Mon, 29 Dec 2008 00:31:09 -0500
>
> > 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.
Thanks, but what I'm trying to do is arrange the new multi-tty
functions into some logical order of a few sections. These are not
limited to frame creation functions, see the corresponding portion of
etc/NEWS.
Maybe I should just stop trying to describe them together, and instead
put every function where it belongs elsewhere in the manual...
next prev parent reply other threads:[~2008-12-29 19:26 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-27 18:23 Terminology in multi-tty primitives Eli Zaretskii
2008-12-28 1:00 ` Chong Yidong
2008-12-28 4:09 ` Eli Zaretskii
2008-12-28 4:28 ` Chong Yidong
2008-12-28 19:18 ` Eli Zaretskii
2008-12-28 19:43 ` Juanma Barranquero
2008-12-29 5:31 ` Chong Yidong
2008-12-29 19:26 ` Eli Zaretskii [this message]
2008-12-29 22:09 ` Richard M Stallman
2008-12-30 2:18 ` Stephen J. Turnbull
2008-12-30 22:26 ` Richard M Stallman
2008-12-31 2:06 ` Stefan Monnier
2008-12-31 2:20 ` Dan Nicolaescu
2008-12-31 3:20 ` Stefan Monnier
2008-12-31 4:29 ` Eli Zaretskii
2008-12-31 6:25 ` Stefan Monnier
2008-12-31 18:47 ` Eli Zaretskii
2008-12-31 21:39 ` Dan Nicolaescu
2008-12-31 21:48 ` Eli Zaretskii
2008-12-31 21:55 ` Dan Nicolaescu
2008-12-31 22:10 ` Eli Zaretskii
2008-12-31 23:03 ` Dan Nicolaescu
2008-12-31 16:38 ` Richard M Stallman
2008-12-31 17:22 ` Stefan Monnier
2008-12-31 19:05 ` Eli Zaretskii
2009-01-01 17:13 ` Stefan Monnier
2009-01-02 13:56 ` Eli Zaretskii
2009-01-03 2:32 ` Stefan Monnier
2009-01-03 9:59 ` Eli Zaretskii
2009-01-04 3:14 ` Stefan Monnier
2009-01-04 3:29 ` Chetan Pandya
2009-01-04 3:41 ` Jason Rumney
2009-01-04 4:54 ` Chetan Pandya
2008-12-30 22:27 ` Richard M Stallman
2008-12-31 5:31 ` Stephen J. Turnbull
2008-12-31 6:28 ` Stefan Monnier
2008-12-31 8:33 ` Stephen J. Turnbull
2008-12-31 14:18 ` Chong Yidong
2008-12-31 15:42 ` Stephen J. Turnbull
2008-12-28 17:29 ` Richard M Stallman
2008-12-28 19:33 ` Eli Zaretskii
2008-12-30 19:53 ` Stefan Monnier
-- strict thread matches above, loose matches on Subject: below --
2008-12-27 18:16 Eli Zaretskii
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=uy6xyaikh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=cyd@stupidchicken.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).