From: Chetan Pandya <pandyacus@sbcglobal.net>
To: Eli Zaretskii <eliz@gnu.org>, Stefan Monnier <monnier@iro.umontreal.ca>
Cc: cyd@stupidchicken.com, emacs-devel@gnu.org, stephen@xemacs.org,
rms@gnu.org
Subject: Re: Terminology in multi-tty primitives
Date: Sat, 3 Jan 2009 19:29:26 -0800 (PST) [thread overview]
Message-ID: <475362.53773.qm@web83203.mail.mud.yahoo.com> (raw)
In-Reply-To: <jwv7i5bn4ui.fsf-monnier+emacs@gnu.org>
--- On Sun, 1/4/09, Stefan Monnier <monnier@iro.umontreal.ca> wrote:
> > However, are we really that sure users won't want to have an ability
> > to create frames on other tty's? By the same token, why do we have
> > make-frame-on-display? the same reason(s) would be arguments to retain
> > make-frame-on-tty.
>
> Not really: 99.99% of the time, ttys are controlled by a shell, or some
> other program, so if we use M-x make-frame-on-tty RET we get into
> a situation where 2 programs use this tty at the same time, without any
> synchronization between them. I've used it for debug
> purposes (to circumvent the server.el and emacsclient code), but it
> tends to give you various forms of display corruption, so it's not really
> appropriate for a user command.
>
> >> - still, when make-frame is called with an explicit `tty' argument but
> >> without an explicit `window-system' argument, the right thing to do is
> >> to give precedence to the `tty' and choose an appropriate window-system for it.
>
> > If we don't need this, why introduce it?
>
> It's not crucial indeed.
>
>
> Stefan
On my system I cannot create a tty frame, but isn't there supposed to be the ability to create multiple frames on a terminal?
Would it make sense to fix the problems, if there are any, or just remove the ability to do that, if not?
Chetan
next prev parent reply other threads:[~2009-01-04 3:29 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
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 [this message]
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=475362.53773.qm@web83203.mail.mud.yahoo.com \
--to=pandyacus@sbcglobal.net \
--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 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).