unofficial mirror of emacs-tangents@gnu.org
 help / color / mirror / Atom feed
From: John Wiegley <jwiegley@gmail.com>
To: joakim@verona.se
Cc: emacs-tangents@gnu.org
Subject: Re: The xwidget branch origin story
Date: Fri, 20 Nov 2015 11:23:09 -0800	[thread overview]
Message-ID: <m2twogtqzm.fsf@newartisans.com> (raw)
In-Reply-To: <m3pozcgx0a.fsf@exodia.verona.se> (joakim@verona.se's message of "Sat, 14 Nov 2015 21:13:25 +0100")

>>>>> joakim  <joakim@verona.se> writes:

> Another thing that gets asked a lot is the xwidget name. I just combined 'x'
> meaning any, and widget, thus xwidget. I needed a prefix in the code. In
> retrospect the name wasn't very descriptive, because people believe that the
> branch is only meant for X windows, which it isn't, even if I only have
> tested it there.

Thanks for the background history, Joakim! And yes, until I read this, I had
thought it was only for X11 as well. :)

John



  reply	other threads:[~2015-11-20 19:23 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 [this message]
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
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=m2twogtqzm.fsf@newartisans.com \
    --to=jwiegley@gmail.com \
    --cc=emacs-tangents@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. 
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).