From: Paul Eggert <eggert@cs.ucla.edu>
To: joakim@verona.se, Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Initial documentation for xwidgets
Date: Fri, 12 Feb 2016 13:55:34 -0800 [thread overview]
Message-ID: <56BE54D6.3010100@cs.ucla.edu> (raw)
In-Reply-To: <m37fi9d2uk.fsf@exodia.verona.se>
On 02/12/2016 01:40 PM, joakim@verona.se wrote:
> Sorry, there was the proposed change to remove unused arguments from
> make-xwidget as well. So two api changes.
I'd say go for it. This API is not part of any Emacs release yet.
next prev parent reply other threads:[~2016-02-12 21:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-30 8:13 Initial documentation for xwidgets Eli Zaretskii
2016-02-12 21:08 ` joakim
2016-02-12 21:20 ` Paul Eggert
2016-02-12 21:25 ` Eli Zaretskii
2016-02-12 21:35 ` joakim
2016-02-12 21:40 ` joakim
2016-02-12 21:55 ` Paul Eggert [this message]
2016-02-13 9:09 ` Eli Zaretskii
2016-02-13 9:09 ` 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=56BE54D6.3010100@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
/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).