all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Spencer Baugh <sbaugh@janestreet.com>
Cc: 62229@debbugs.gnu.org
Subject: bug#62229: 29.0.60; It's no longer possible to customize the xref ring size
Date: Fri, 17 Mar 2023 10:17:28 +0200	[thread overview]
Message-ID: <83v8izeqqv.fsf@gnu.org> (raw)
In-Reply-To: <ierh6ukjqit.fsf@janestreet.com> (message from Spencer Baugh on Thu, 16 Mar 2023 18:11:06 -0400)

> From: Spencer Baugh <sbaugh@janestreet.com>
> Date: Thu, 16 Mar 2023 18:11:06 -0400
> 
> 
> Emacs 28 had the function xref-set-marker-ring-length and the
> customizable variable xref-marker-ring-length which allowed growing
> the amount of history kept by xref.
> 
> This feature has been lost in Emacs 29; that variable has been
> obsoleted with no replacement.
> 
> It's not clear, looking at the change, whether this is because the
> size is now infinite or not.  The same commit that obsoleted that
> variable added the similar tags-location-ring-length.  However that
> variable has no docstring, no customize hooks, and setting it has no
> effect unless tags-reset-tags-tables is called.
> 
> At the very least, all this should be documented better, and the
> obsoleting of this function and variable should be mentioned in NEWS.
> If the history is indeed infinite now, that should be mentioned in
> NEWS as well.

Indeed, that change paid very little attention to documenting the
important aspects of adding Xref history and using it instead of a
limited-size ring.  We should do better.

I've now attempted to add the missing documentation; please take a
look at the latest emacs-29 branch.





  parent reply	other threads:[~2023-03-17  8:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-16 22:11 bug#62229: 29.0.60; It's no longer possible to customize the xref ring size Spencer Baugh
2023-03-17  0:03 ` Dmitry Gutov
2023-03-17  8:17 ` Eli Zaretskii [this message]
2023-03-17 12:02   ` Spencer Baugh
2023-03-17 12:16     ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83v8izeqqv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=62229@debbugs.gnu.org \
    --cc=sbaugh@janestreet.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 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.