unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mario Lang <mlang@blind.guru>
Cc: emacs-devel@gnu.org
Subject: Re: blink-matching-paren jump-offscreen
Date: Fri, 30 Dec 2022 10:53:37 +0200	[thread overview]
Message-ID: <83cz816zn2.fsf@gnu.org> (raw)
In-Reply-To: <877cy95qwf.fsf@blind.guru> (message from Mario Lang on Fri, 30 Dec 2022 07:47:44 +0100)

> From: Mario Lang <mlang@blind.guru>
> Date: Fri, 30 Dec 2022 07:47:44 +0100
> 
> Updating to Emacs 29, I see that my setting of
> 
> blink-matching-paren
> 
> is apparently not honored.

What is "your setting", and how is it not honored by Emacs 29?  Please
tell the details, preferably in the form of a reproducible recipe
starting from "emacs -Q", so that we could investigate and try to fix
what became broken.

> About 2 years ago, I came here to let you know that at least me was
> really depending on blink-matching-paren to use a jumping point.  So
> the feature was, after having been rewritten recently, reinstated.
> Thanks for that.  However, next dev version, and the feature is
> apparently broken again.
> 
> It is great that Emacs has a lot of ongoing development.
> However, it would be even nicer if this ongoing development
> would not regularily destroy old-school features long-term power users
> depend on.

As a matter of fact, we are trying very hard not to break past
behavior, and when that is for some reason unavoidable (and I'm not
saying this is the case here), provide options to get back the old
behavior.  Occasionally, we make mistakes and fail to do TRT, but
there's definitely no intentional breakage of past behavior.  Quite
the contrary.

So please bear with us and help us repair what we inadvertently broke.

TIA



  reply	other threads:[~2022-12-30  8:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30  6:47 blink-matching-paren jump-offscreen Mario Lang
2022-12-30  8:53 ` Eli Zaretskii [this message]
2022-12-30  9:20   ` Mario Lang
2022-12-30 13:54     ` Eli Zaretskii

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=83cz816zn2.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mlang@blind.guru \
    /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).