all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: [External] : view-remove-frame-by-deleting ignored?
Date: Wed, 12 Oct 2022 19:04:08 +0300	[thread overview]
Message-ID: <83k055av0n.fsf@gnu.org> (raw)
In-Reply-To: <SJ0PR10MB54880418766D4D068DC3FEE3F3229@SJ0PR10MB5488.namprd10.prod.outlook.com> (message from Drew Adams on Wed, 12 Oct 2022 15:33:14 +0000)

> From: Drew Adams <drew.adams@oracle.com>
> CC: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Wed, 12 Oct 2022 15:33:14 +0000
> 
> > > > I generally use 26.3, as later releases
> > > > broke too much for me. :-(
> > >
> > > Too bad.  I see this a lot with Emacs users
> > > as of late, where they pick some version of
> > > Emacs that has not seen development in years
> > > (or even decades) and stick to it, because
> > > we break too much.
> > 
> > FTR, in this particular case, our requests that
> > Drew helps us debug the problem which caused him
> > stick to 26.3 were met with refusal.
> 
> That is _absolutely_ untrue.  A completely unfair
> characterization.

It's fair and true.  As you yourself describe:

> I provided the info I could, with the time and
> know-how I have available.  Trying to track down
> the problem in more detail is beyond me, as I've
> explained.

Exactly: once we asked for more effort than you were prepared to
invest you said no.  How is that not a refusal?  You were told several
times that you are the only one who can reproduce the problem, and you
still declined to help more.  So here we are today.

> I'm not expecting Emacs development to cater to
> my setup.  Never have.  I can't make good use of
> Emacs after release 26, but I don't expect that
> to change.

Then please make a point of saying this when you mention that you
stick to Emacs 26.3, lest people who aren't privy to the history of
this don't fall into the trap of thinking we break stuff and don't
bother fixing it.

> For some reason Eli, you never miss an opportunity
> to attack me personally.  Too bad.

It's actually the other way around.



  reply	other threads:[~2022-10-12 16:04 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-08 20:32 view-remove-frame-by-deleting ignored? Thorsten Bonow
2022-10-08 21:15 ` [External] : " Drew Adams
2022-10-08 21:29   ` Drew Adams
2022-10-08 23:45     ` Michael Heerdegen
2022-10-09  2:16       ` Drew Adams
2022-10-09 19:14         ` Thorsten Bonow
2022-10-09 19:24           ` Drew Adams
2022-10-09 19:31             ` Emanuel Berg
2022-10-11 15:17               ` Drew Adams
2022-10-12  0:57                 ` Po Lu
2022-10-12  1:39                   ` Drew Adams
2022-10-12  5:36                   ` Eli Zaretskii
2022-10-12 15:33                     ` Drew Adams
2022-10-12 16:04                       ` Eli Zaretskii [this message]
2022-10-12 17:13                         ` Drew Adams
2022-10-12 19:16                           ` Michael Heerdegen
2022-10-12 19:59                   ` Emanuel Berg
2022-10-09 19:48             ` Thorsten Bonow
2022-10-09 20:42               ` Drew Adams
2022-10-09 21:08           ` Michael Heerdegen
2022-10-10 15:15             ` Thorsten Bonow
2022-10-10 23:46               ` Michael Heerdegen

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=83k055av0n.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.org \
    /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.