unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: cyd@stupidchicken.com, stephen@xemacs.org, rms@gnu.org,
	emacs-devel@gnu.org
Subject: Re: Terminology in multi-tty primitives
Date: Thu, 01 Jan 2009 12:13:53 -0500	[thread overview]
Message-ID: <jwvfxk3oss4.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <usko4np0p.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 31 Dec 2008 21:05:58 +0200")

>> > By the way, why does it need the conditional that tests window-system?
>> > Should the proper handling of window-system be built into `make-frame'
>> > instead?  If it is needed for all frame creation on MSDOG, putting it
>> > in `make-frame' is best because that way it only needs to be done once
>> > and callers are all simpler.
>> My thought exactly,

> Could you two please explain the details of your thoughts?
> The original make-frame-on-tty, before I added the `pc' condition, did
> this:

>     (make-frame `((window-system . nil) (tty . ,tty) (tty-type . ,type) . ,parameters))))

> Now, what do you want to change exactly, and which part do you want to
> move to make-frame?

I think calls to make-frame-on-tty should be replaceable by just

   (make-frame `((tty . ,tty) (tty-type . ,type) . ,parameters))))

I.e. the explicit `tty' parameter should be interpreted by make-frame as
overriding the window-system of the current frame.


        Stefan




  reply	other threads:[~2009-01-01 17:13 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
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 [this message]
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=jwvfxk3oss4.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=cyd@stupidchicken.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --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 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).