unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nicolas Petton <nicolas@petton.fr>
To: joakim@verona.se, Emacs developers <emacs-devel@gnu.org>
Cc: johnw@gnu.org, monnier@IRO.UMontreal.CA
Subject: Re: merging the xwidget_mvp branch
Date: Thu, 05 Nov 2015 13:13:05 +0100	[thread overview]
Message-ID: <87fv0kiqzy.fsf@petton.fr> (raw)
In-Reply-To: <m3bnbapyrw.fsf@exodia.verona.se>

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

joakim@verona.se writes:

> Stefan expressed interest in merging the xwidget_mvp branch before the
> Emacs 25 release. If we could make that happen it would be great. If
> not, so be it, but I would need to know well in advance, because of other
> possible commitments. 
>
> For those who don't know, the xwidget_mvp branch is allows embedding of
> an webkit widget in an emacs window. (There is also an xwidget branch
> that has more features but it is not ready for inclusion). 
>
> The branch wouldn't actually be merged, rather a patch would be
> extracted and applied to master, because the branch has irrelevant
> history.

I just tried it, switching to the xwidget_mvp branch and compiling
Emacs, but I get the following errors after a `M-x xwidget-browse-url':

read-string: Symbol’s value as variable is void: xwidget-view-list
xwidget-kill-buffer-query-function: Symbol’s function definition is
void: get-buffer-xwidgets

I guess I'm doing something wrong, or not compiling it properly.

Nico

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 512 bytes --]

  parent reply	other threads:[~2015-11-05 12:13 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-03 21:18 merging the xwidget_mvp branch joakim
2015-11-03 21:23 ` John Wiegley
2015-11-03 21:37   ` joakim
2015-11-03 21:51     ` John Wiegley
2015-11-04 11:01       ` Nicolas Petton
2015-11-04 16:37         ` raman
2015-11-04 17:22           ` Michael Abrahams
2015-11-04 13:52       ` Stefan Monnier
2015-11-06 21:21         ` John Wiegley
2015-11-08 16:34           ` joakim
2015-11-08 17:13             ` Eli Zaretskii
2015-11-09 19:53               ` Join us on emacs-tangents! (was: merging the xwidget_mvp branch) John Wiegley
2015-11-09 20:08                 ` Join us on emacs-tangents! Rasmus
2015-11-09 21:31                   ` John Wiegley
2015-11-09 20:17                 ` Dmitry Gutov
2015-11-09 21:30                   ` John Wiegley
2015-11-09 23:58                 ` Join us on emacs-tangents! (was: merging the xwidget_mvp branch) Aaron Ecay
2015-11-10 10:47                   ` Join us on emacs-tangents! Jose E. Marchesi
2015-11-11 10:33           ` merging the xwidget_mvp branch joakim
2015-11-11 16:32             ` John Wiegley
2015-11-04 15:29       ` Eli Zaretskii
2015-11-05 12:13 ` Nicolas Petton [this message]
2015-11-05 12:19   ` joakim
2015-11-08 16:32   ` joakim
2015-11-09  9:17     ` Nicolas Petton

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=87fv0kiqzy.fsf@petton.fr \
    --to=nicolas@petton.fr \
    --cc=emacs-devel@gnu.org \
    --cc=joakim@verona.se \
    --cc=johnw@gnu.org \
    --cc=monnier@IRO.UMontreal.CA \
    /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).