unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: emacsq <laszlomail@protonmail.com>
To: "emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Releasing small, not critical features as bugfixes
Date: Sun, 10 Apr 2022 06:16:30 +0000	[thread overview]
Message-ID: <nQMMUUunU1Zw8KLJgnODxY8bmVM-IoOx-DPg7XAhfcjdsYjNv1yf_jC94fX-jXTc1NfIQ75zVW5nImcffyb4hCuxksDPJE4gg5Xcs6-2aG0=@protonmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1014 bytes --]

I checked if show-paren can show context from off screen and it can, in Emacs 29:

*** New user option 'show-paren-context-when-offscreen'.

When non-nil, if the point is in a closing delimiter and the opening

delimiter is offscreen, shows some context around the opening
delimiter in the echo area.

Emacs 28.1 was just released. Judging from the previous release history Emacs 29 is 1.5/2 years away.

Such small, useful improvements which don't cause critical errors could be released along with Emacs 28 bugfixes, so users can get them earlier, instead of waiting for them for two years.

Of course, there are bigger, more complex improvements which have to be tested thoroughly, but features like the above could be released sooner with the bugfixes, because they are pretty safe improvements.

Or maybe there could be a branch like emacs-future where these small useful improvements could be put, so there is the stable banch (28), this low risk future branch (between 28 and 29) and the bleeding edge (29).

[-- Attachment #2: Type: text/html, Size: 2739 bytes --]

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

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-10  6:16 emacsq [this message]
2022-04-10 11:45 ` Releasing small, not critical features as bugfixes Po Lu
2022-04-10 16:37   ` emacsq
2022-04-10 18:31     ` Corwin Brust
2022-04-10 20:00       ` emacsq
2022-04-11  3:20     ` Po Lu

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='nQMMUUunU1Zw8KLJgnODxY8bmVM-IoOx-DPg7XAhfcjdsYjNv1yf_jC94fX-jXTc1NfIQ75zVW5nImcffyb4hCuxksDPJE4gg5Xcs6-2aG0=@protonmail.com' \
    --to=laszlomail@protonmail.com \
    --cc=emacs-devel@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 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).