unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: "Jan Djärv" <jan.h.d@swipnet.se>
Cc: emacs-devel@gnu.org, timo.savola@iki.fi
Subject: Re: XEmbed patches
Date: Sat, 21 Jul 2007 00:52:35 -0400	[thread overview]
Message-ID: <E1IC6xH-0000io-NX@fencepost.gnu.org> (raw)
In-Reply-To: <46A05B3F.2010704@swipnet.se> (message from Jan Djärv on Fri, 20 Jul 2007 08:50:39 +0200)

    One thing that would be cool to have is to be able to embed a
    frame from emacsclient.  You can do that now with frame parameters
    and eval, but I was thinking for something like a defun
    create-embedded-frame or something like that.  Just to simplify
    things.

Maybe you are right, but I'm not sure.

emacsclient is designed for programs that want to "invoke an editor"
without knowing which one.

By contrast, an Emacs window in the frame of some other app
would be created by an app that knows what it is doing.
Is emacsclient the right interface for that?

Perhaps what you mean is that the app should be able to ask an
existing Emacs to create the window, rather than starting a new Emacs.
The emacsclient mechanism might be the right way to do that.
But the interface to use is a separate question.

  reply	other threads:[~2007-07-21  4:52 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-18 14:25 XEmbed patches Timo Savola
2007-07-20  6:50 ` Jan Djärv
2007-07-21  4:52   ` Richard Stallman [this message]
2007-07-20  6:53 ` Jan Djärv
2007-07-20  8:24   ` Timo Savola
2007-07-20  8:40     ` Jason Rumney
2007-07-20  8:44       ` Timo Savola
2007-07-20  8:47         ` Jason Rumney
2007-07-20  8:59           ` Timo Savola
2007-07-20  9:02       ` David Kastrup
2007-07-20 10:33         ` Jan Djärv
2007-07-20 10:44           ` Jason Rumney
2007-07-20 12:28             ` Stephen J. Turnbull
2007-07-21  4:52       ` Richard Stallman
2007-07-20  9:24     ` Jan Djärv
2007-07-20  9:33       ` Timo Savola

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=E1IC6xH-0000io-NX@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=jan.h.d@swipnet.se \
    --cc=timo.savola@iki.fi \
    /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).