all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: George Plymale II <georgedp@orbitalimpact.com>
To: Ryan Thompson <rct@thompsonclan.org>
Cc: alan@idiocy.org, nick@tenpoint.co.nz,
	rct+github@thompsonclan.org, 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: Sat, 02 Jun 2018 14:56:18 -0400	[thread overview]
Message-ID: <m08t7xdnl9.fsf@georgedp.developer.orbitalimpact.com> (raw)
In-Reply-To: <CAHCt_ab3-G-RvH2LF7gjNnrqXgy7VYigFAg7RZVW1K2L-M1GKQ@mail.gmail.com> (message from Ryan Thompson on Sat, 2 Jun 2018 09:45:03 -0700)

Ryan Thompson <rct@thompsonclan.org> writes:

> Hello,
>
> As before, I don't have much to add, as I'm not familiar with the internals
> of Emacs responsible for the underlying issue. But as I've said before, I'm
> perfectly happy to have my "pseudo-daemon" code incorporated into Emacs
> itself, and I have already signed the copyright assignment papers for a few
> small prior contributions to Emacs. If there is interest, I can rewrite my
> mode as a patch to Emacs rather than advice.

Thanks a lot Ryan! I think you're probably the most qualified person to
help out with this. Importing your package as a patch is also probably a
good idea; an advice seems like more of a 3rd-party thing to do.

> One thing we should think about is what happens when my package is
> installed and enabled on an Emacs that also includes this behavior as
> a core feature. I believe that it shouldn't cause any problems, since
> only one or the other will ever activate, not both.

If it does cause any problems, perhaps you could add an ad-hoc variable
or something and include a check for it in your package. Perhaps it
could issue a warning if it detects that it's running on an Emacs which
has the fix in the core. E.g.,

"Warning: Your Emacs already has this fix in the core, so this package
is actually not needed"

> In practice, the main drawback to using this mode is that when the last
> existing frame is closed the new frame that it creates is briefly visible
> before being hidden. This isn't a major issue in general, but it could
> easily confuse people who don't know what's going on and make them think
> that a glitch has occurred. If anyone knows how to create a hidden frame
> without ever making it visible, I'd be happy to fix that.

It seems that Stefan has mentioned something on how to deal with this in
an earlier message. I think I've seen this glitch a few times in the
past, but it never bothered me so I didn't really care. I don't know
much else about this particular issue so I can't comment further on it.



      parent reply	other threads:[~2018-06-02 18:56 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
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 [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m08t7xdnl9.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=rct+github@thompsonclan.org \
    --cc=rct@thompsonclan.org \
    --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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.