unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: George Plymale II <georgedp@orbitalimpact.com>
To: George Plymale II <georgedp@orbitalimpact.com>
Cc: alan@idiocy.org, nick@tenpoint.co.nz, emacs-devel@gnu.org,
	p.stephani2@gmail.com, monnier@iro.umontreal.ca,
	van@scratch.space, eliz@gnu.org
Subject: Re: Should this package be included into the NS port?
Date: Tue, 29 May 2018 17:29:09 -0400	[thread overview]
Message-ID: <m0muwi9mmy.fsf@georgedp.developer.orbitalimpact.com> (raw)
In-Reply-To: <m0po1xbimh.fsf@georgedp.developer.orbitalimpact.com> (message from George Plymale II on Tue, 15 May 2018 01:19:50 -0400)

Hi again folks,

The discourse so far regarding this issue has been very interesting. It
seems there's been a lot of back-and-forth about how to solve this issue
in the core. I won't reiterate or re-hash all of it here, but suffice it
to say that it seems this brings some significant difficulties due to
the way Emacs and the NS machinery cooperate. I'm still wondering if
perhaps we shouldn't just put the band-aid of osx-pseudo-daemon on the
problem for now.

I don't want anyone to feel over-burdened with the task of taking on
this issue or to feel out of their depth, so I'm just putting this on
the table once more. I talked to Ryan C. Thompson on Github the other
day; he said he's already signed the FSF paperwork so his package should
be acceptable into the core with little to no issues on that front.

I think this package will be a significantly easier solution for the
time being (if incomplete), and it will give us a little more time to
mull over how to solve the real problem for good.

Thanks,
- George Plymale II



  parent reply	other threads:[~2018-05-29 21:29 UTC|newest]

Thread overview: 60+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-15  5:19 Should this package be included into the NS port? George Plymale II
2018-05-15 18:25 ` Stefan Monnier
2018-05-15 18:36   ` Alan Third
2018-05-16  2:48     ` George Plymale II
2018-05-18 19:36       ` Alan Third
2018-05-18 21:21         ` George Plymale II
2018-05-19  4:57           ` Nick Helm
2018-05-19 15:49             ` George Plymale II
2018-05-23  5:22               ` Nick Helm
2018-05-23 19:29                 ` George Plymale II
2018-05-19  9:50           ` Alan Third
2018-05-19 16:06             ` George Plymale II
2018-05-19 18:33             ` Stefan Monnier
2018-05-22  1:42               ` George Plymale II
2018-05-22  1:48                 ` Van L
2018-05-22 19:04                   ` Alan Third
2018-05-23  2:30                     ` Off Topic (was: Should this package be included into the NS port?) Van L
2018-05-23 20:43                       ` Alan Third
2018-05-24  1:27                         ` emacs-26.1-rc1: ./configure (was: Off Topic) Van L
2018-05-24  8:55                           ` emacs-26.1-rc1: ./configure Robert Pluim
2018-05-24 10:51                             ` Van L
2018-05-24 11:51                               ` Robert Pluim
2018-05-24 11:57                                 ` Van L
2018-05-24 23:47                               ` Van L
2018-05-22 19:15                 ` Should this package be included into the NS port? Alan Third
2018-05-22 20:09                   ` George Plymale II
2018-05-19  4:42         ` Nick Helm
2018-05-19 10:33           ` Alan Third
2018-05-19 11:51             ` Philipp Stephani
2018-05-19 16:52             ` George Plymale II
2018-05-23  4:55             ` Nick Helm
2018-05-23  5:11             ` Nick Helm
2018-05-23 15:26               ` Eli Zaretskii
2018-05-23 16:37                 ` Stefan Monnier
2018-05-23 17:23                   ` Eli Zaretskii
2018-05-23 21:21                 ` Alan Third
2018-05-24 16:37                   ` Eli Zaretskii
2018-05-24 17:46                     ` Philipp Stephani
2018-05-24 17:51                       ` Philipp Stephani
2018-05-24 18:14                       ` Eli Zaretskii
2018-05-16  2:44   ` George Plymale II
2018-05-17 22:13 ` George Plymale II
2018-05-18 18:50   ` Alan Third
2018-05-18 20:40     ` George Plymale II
2018-05-19  8:31     ` Michael Albinus
2018-05-19  4:29 ` Nick Helm
2018-05-19 15:38   ` George Plymale II
2018-05-29 21:29 ` George Plymale II [this message]
2018-05-29 21:42   ` Alan Third
2018-05-29 23:40     ` George Plymale II
2018-05-31 20:40       ` Alan Third
2018-06-01  1:58         ` Stefan Monnier
2018-06-02 18:31           ` George Plymale II
2018-06-02 19:39             ` Stefan Monnier
2018-06-02 20:11               ` Alan Third
2018-06-03  2:25                 ` Stefan Monnier
2018-06-02 18:26         ` George Plymale II
2018-06-02 16:45       ` Ryan Thompson
2018-06-02 17:22         ` Stefan Monnier
2018-06-02 18:56         ` George Plymale II

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=m0muwi9mmy.fsf@georgedp.developer.orbitalimpact.com \
    --to=georgedp@orbitalimpact.com \
    --cc=alan@idiocy.org \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=nick@tenpoint.co.nz \
    --cc=p.stephani2@gmail.com \
    --cc=van@scratch.space \
    /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).