From: Keisuke Nishida <kxn30@po.cwru.edu>
To: John Wiegley <johnw@gnu.org>
Cc: guile-emacs@sourceware.cygnus.com
Subject: Re: frames and windows
Date: Wed, 29 Mar 2000 07:49:00 -0000 [thread overview]
Message-ID: <m34s9pzshb.fsf@kei.cwru.edu> (raw)
In-Reply-To: <87r9cugjp4.fsf@PC486.Niemitalo.LAN>
John Wiegley <johnw@gnu.org> writes:
> > What about renaming them in terms of GTK+ when we use Emacs Scheme?
> > I know this is very confusing and controversial, but I would choose
> > renaming because it will help people after ten years.
>
> It's a question of whether you pick GTK or Emacs as the basis for
> nomenclature. I would recommend the latter.
Kalle Olavi Niemitalo <tosi@ees2.oulu.fi> writes:
> I believe it is easier to keep the frontier between Emacs and
> window systems. If someone uses guile-gtk to create a GTK+
> window, [s]he can't use that as an Emacs frame anyway.
Right. I guess I shouldn't resist the tradition...
prev parent reply other threads:[~2000-03-29 7:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-28 14:51 Keisuke Nishida
2000-03-29 2:33 ` Kalle Olavi Niemitalo
2000-03-29 7:49 ` Keisuke Nishida [this message]
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=m34s9pzshb.fsf@kei.cwru.edu \
--to=kxn30@po.cwru.edu \
--cc=guile-emacs@sourceware.cygnus.com \
--cc=johnw@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.
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).