unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Emanuel Berg <incal@dataswamp.org>,
	"help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: RE: [External] : view-remove-frame-by-deleting ignored?
Date: Tue, 11 Oct 2022 15:17:06 +0000	[thread overview]
Message-ID: <SJ0PR10MB5488BB9ED955C19C58B0D0F6F3239@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <87y1to23q1.fsf@dataswamp.org>

> > I don't use non-released Emacs builds.
> 
> What does that mean, what builds are released?
> Change of first, second, or all (any) version number?

I think 28.2 is the latest release.  29.1 is
not yet released.  37.4 is not yet released.

When 42.x is released the universe will be
done with whatever it's been trying to do.
Or so I hear.  Which universe, you ask?  Each
in which you see this msg.
___

FWIW -

I generally use 26.3, as later releases broke
too much for me. :-(

I keep the latest build of each Emacs major
release (e.g. 24.5, but not 24.4 etc.).  But
I haven't bothered to pick up 28.2 yet.  I
use 27.2 and later only for some testing and
bug reporting.  I use 26.3 for my own use.

I byte-compile my libraries with the oldest
release for which each is compatible.  Which
means I need to load the source later, if I
need some feature from it that requires a
later release than the byte-compiled file.
Lots of code works just fine with Emacs 20.7.




  reply	other threads:[~2022-10-11 15:17 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 [this message]
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
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

  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=SJ0PR10MB5488BB9ED955C19C58B0D0F6F3239@SJ0PR10MB5488.namprd10.prod.outlook.com \
    --to=drew.adams@oracle.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=incal@dataswamp.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.
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).