From: Michael Abrahams <miabraha@gmail.com>
To: Joakim Verona <joakim@verona.se>
Cc: John Wiegley <jwiegley@gmail.com>,
emacs-tangents@gnu.org, Drew Adams <drew.adams@oracle.com>
Subject: Re: The xwidget branch origin story
Date: Sun, 22 Nov 2015 12:26:00 -0500 [thread overview]
Message-ID: <CADvwsn5D=cizWZsGpFVwL4FH9aHcjrTh6E1AYqD3BRcwFGduzw@mail.gmail.com> (raw)
In-Reply-To: <m3oaemgmti.fsf@exodia.verona.se>
[-- Attachment #1: Type: text/plain, Size: 783 bytes --]
ewidgets, egtk, gtk-widgets, emacs-widgets, elisp-widgets, elisp-gtk,
elisp-gtkw
On Sun, Nov 22, 2015 at 8:56 AM, <joakim@verona.se> wrote:
> John Wiegley <jwiegley@gmail.com> writes:
>
> >>>>>> Drew Adams <drew.adams@oracle.com> writes:
> >
> >> Since `xwidget' is misleading people, and the `x' doesn't help in any
> way,
> >> please just rename it. But we also already have Emacs code concerning
> >> widgets, so maybe try to come up with a name that is specific to these
> >> particular widgets or their use.
> >
> > Even ewidgets would be better.
>
> I can rename the feature and the right time would be now before merging
> it to master.
>
> But since I obviously fail at coming up with good names, I need some
> help. John?
>
>
>
> >
> > John
> >
>
> --
> Joakim Verona
>
>
[-- Attachment #2: Type: text/html, Size: 1406 bytes --]
next prev parent reply other threads:[~2015-11-22 17:26 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-14 20:13 The xwidget branch origin story joakim
2015-11-20 19:23 ` John Wiegley
2015-11-20 19:31 ` Drew Adams
2015-11-20 19:38 ` John Wiegley
2015-11-22 13:56 ` joakim
2015-11-22 17:26 ` Michael Abrahams [this message]
2015-11-22 19:19 ` joakim
2015-11-22 20:02 ` Michael Abrahams
2015-11-22 20:10 ` John Wiegley
2015-11-22 20:13 ` joakim
2015-11-22 20:16 ` John Wiegley
2015-11-24 23:05 ` Andy Moreton
2015-11-24 23:21 ` John Wiegley
2015-11-24 23:28 ` Drew Adams
2015-11-25 0:47 ` John Wiegley
2015-11-26 21:16 ` joakim
2015-11-26 21:51 ` Iñigo Serna
2015-11-27 7:28 ` Eli Zaretskii
2015-11-27 0:33 ` Andy Moreton
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='CADvwsn5D=cizWZsGpFVwL4FH9aHcjrTh6E1AYqD3BRcwFGduzw@mail.gmail.com' \
--to=miabraha@gmail.com \
--cc=drew.adams@oracle.com \
--cc=emacs-tangents@gnu.org \
--cc=joakim@verona.se \
--cc=jwiegley@gmail.com \
/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).