all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: cyd@stupidchicken.com, "Stephen J. Turnbull" <stephen@xemacs.org>,
	eliz@gnu.org, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Terminology in multi-tty primitives
Date: Tue, 30 Dec 2008 18:20:32 -0800 (PST)	[thread overview]
Message-ID: <200812310220.mBV2KWv4001309@mothra.ics.uci.edu> (raw)
In-Reply-To: <jwvprj9t7zt.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 30 Dec 2008 21:06:27 -0500")

Stefan Monnier <monnier@iro.umontreal.ca> writes:

  > > 	(make-frame '((terminal DESCRIPTOR)
  > > 		      (terminal-type TYPE)))
  > 
  > > I think this is not very different from the current situation, as
  > > regards Lisp calls.  The reason for make-frame-on-display and
  > > make-frame-on-tty is for invocation with M-x, where you need to
  > > specify the terminal with a string.
  > 
  > > These commands could be merged by using a heuristic to
  > > tell whether the argument is a tty device or an X server.
  > 
  > I don't think it's important to merge them.  More important is to make
  > it clear why they exist.  E.g. by marking them as "not for use from
  > Elisp" and/or by documenting which `make-frame' call is equivalent when
  > called from Elisp.

BTW is `make-frame-on-tty' useful as an interactive function?  What
would the use-case be for that?  I'd say: drop the interactive spec for it...




  reply	other threads:[~2008-12-31  2:20 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
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 [this message]
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

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

  git send-email \
    --in-reply-to=200812310220.mBV2KWv4001309@mothra.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=cyd@stupidchicken.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=rms@gnu.org \
    --cc=stephen@xemacs.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 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.