unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Timo Savola <timo.savola@iki.fi>
Cc: emacs-devel@gnu.org
Subject: Re: GtkPlug patch
Date: Mon, 02 Jan 2006 11:18:44 +0200	[thread overview]
Message-ID: <1136193524.8222.10.camel@localhost.localdomain> (raw)
In-Reply-To: <E1EtDVV-00007z-A6@fencepost.gnu.org>

[-- Attachment #1: Type: text/plain, Size: 595 bytes --]

>     > Does anyone know what we need to do
>     > to make the Xt versions of Emacs handle XEmbed?
> 
>     Since Emacs has its own event loop, the implementation for non-Xt (i.e. pure 
>     Xlib) would be the same as for Xt.  Like the drop part of drag and drop is now.
> 
> So much the better--but still, does someone know how to make the event loop
> handle these?

I guess I could take a look at it unless someone more familiar with the
Emacs X code (or the existing XEmbed implementations in GTK+ or Qt) is
willing to.

Is there a chance of getting the GTK version into Emacs 22?

timo



[-- Attachment #2: Type: text/plain, Size: 595 bytes --]


This message has been scanned by F-Secure Anti-Virus

###  OXFORD INSTRUMENTS   http://www.oxford-instruments.com/  ###

Unless stated above to be non-confidential, this E-mail and any
attachments are private and confidential and are for the addressee
only and may not be used, copied or disclosed save to the addressee.
If you have received this E-mail in error please notify us upon receipt
and delete it from your records. Internet communications are not secure
and Oxford Instruments is not responsible for their abuse by third
parties nor for any alteration or corruption in transmission.

[-- Attachment #3: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

  reply	other threads:[~2006-01-02  9:18 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-26 23:09 GtkPlug patch Timo Savola
2005-12-29  7:02 ` Timo Savola
2005-12-31 11:06   ` Jan Djärv
2005-12-31 11:23     ` Jan Djärv
2005-12-31 17:24     ` mr mike
2006-01-01  2:14       ` Richard M. Stallman
2006-01-01 15:57         ` Jan Djärv
2006-01-02  0:25           ` Richard M. Stallman
2006-01-02  9:18             ` Timo Savola [this message]
2006-01-02  9:51               ` Timo Savola
2006-01-02 23:48               ` Richard M. Stallman
2006-01-03  8:45                 ` Timo Savola
2006-01-03  7:53             ` Jan D.
2006-01-03 18:27               ` Richard M. Stallman
2006-01-03 18:37                 ` David Kastrup
2006-01-03 20:29                   ` Timo Savola
2006-01-04  6:15                     ` Richard M. Stallman
2006-01-04 22:11                     ` Jan D.
2006-01-04 22:09                   ` Jan D.
2006-01-05  6:13                     ` Timo Savola
2006-01-05 10:34                       ` Jan D.
2006-01-03 13:41 ` Lőrentey Károly

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=1136193524.8222.10.camel@localhost.localdomain \
    --to=timo.savola@iki.fi \
    --cc=emacs-devel@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.
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).