unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: chad <yandros@gmail.com>
Cc: p.d.oliver@mavit.org.uk, emacs-devel@gnu.org
Subject: Re: GUI X-FreeDesktop integration
Date: Sat, 29 May 2021 09:01:51 +0300	[thread overview]
Message-ID: <83lf7y6ptc.fsf@gnu.org> (raw)
In-Reply-To: <CAO2hHWbPq1drg936PFWJu5CtzkvK8sDHT3GZLEOj4eVADWvq3g@mail.gmail.com> (message from chad on Fri, 28 May 2021 13:05:30 -0700)

> From: chad <yandros@gmail.com>
> Date: Fri, 28 May 2021 13:05:30 -0700
> Cc: Peter Oliver <p.d.oliver@mavit.org.uk>,
>  EMACS development team <emacs-devel@gnu.org>
> 
> On Fri, May 28, 2021 at 12:16 PM Eli Zaretskii <eliz@gnu.org> wrote:
> 
>  I suggest to do this the other way around: make this new behavior
>  optional, until we are sure people expect that.
>  [...] We shouldn't bend our thinking
>  like that, just because we see some trend in other applications and
>  think we can easily follow it with something similar.
> 
> Sure, the conservative approach works here also. What I was suggesting was basically "let's give the distros
> both options and ask/see which they pick". Since we're generally sensitive to changing defaults on releases,
> I think there are ways to ask before releasing, but the data collection is likely to be sparse.

Distros can do whatever they like anyway, and we have no real control
of that.



  reply	other threads:[~2021-05-29  6:01 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-25 21:34 GUI X-FreeDesktop integration Peter Oliver
2021-05-26  8:49 ` Robert Pluim
2021-05-26 12:14 ` Peter Oliver
2021-05-26 12:19 ` Eli Zaretskii
2021-05-28 12:54   ` Peter Oliver
2021-05-28 13:03     ` Eli Zaretskii
2021-05-28 18:49       ` chad
2021-05-28 19:16         ` Eli Zaretskii
2021-05-28 20:05           ` chad
2021-05-29  6:01             ` Eli Zaretskii [this message]
  -- strict thread matches above, loose matches on Subject: below --
2021-08-12 12:42 Manuel Uberti
2021-08-12 12:51 ` Eli Zaretskii
2021-08-12 12:58   ` Lars Ingebrigtsen
2021-05-14  3:18 Boruch Baum
2021-05-14  3:46 ` Stefan Monnier
2021-05-16  3:26   ` Boruch Baum
2021-05-14  6:45 ` Eli Zaretskii
2021-05-14  7:20   ` Joost Kremers
2021-05-14  7:41     ` Eli Zaretskii
2021-05-14  7:53       ` Joost Kremers
2021-05-14 11:29         ` Yuri Khan
2021-05-14 13:51         ` Stefan Monnier
2021-05-16  3:33   ` Boruch Baum
2021-05-16  4:25     ` Eli Zaretskii
2021-05-16  4:36       ` Boruch Baum
2021-05-16 10:46         ` Robin Tarsiger
2021-05-16 20:07           ` Matthias Meulien

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=83lf7y6ptc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=p.d.oliver@mavit.org.uk \
    --cc=yandros@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.
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).