From: Eli Zaretskii <eliz@gnu.org>
To: Risto Lahe <laheristo@gmail.com>
Cc: 36144@debbugs.gnu.org
Subject: bug#36144: 27.0.50; Xref problems
Date: Sun, 09 Jun 2019 09:29:45 +0300 [thread overview]
Message-ID: <835zpfcluu.fsf@gnu.org> (raw)
In-Reply-To: <CAB7mf2gXSmwWczKpD51f7vHBHbdJneb-cqirjwq5ayPNQ5qtag@mail.gmail.com> (message from Risto Lahe on Sun, 9 Jun 2019 07:43:28 +0300)
> From: Risto Lahe <laheristo@gmail.com>
> Date: Sun, 9 Jun 2019 07:43:28 +0300
>
> Helm-xref and ivy-xref packages have stopped working on master. Other guy in #emacs IRC have confirmed
> it too.
> recent commits containing “xref” in their subject:
Was this reported to the Helm and Ivi developers? If so, did they
conclude that the problem was in Emacs core and not in the respective
packages? It could be, for example, that these packages rely on some
internal implementation details which were now changed; in that case,
the packages should modify their code to unbreak themselves.
If you didn't yet report this to the developers of Helm and Ivy,
please do so, and let's wait for their conclusions.
Thanks.
next prev parent reply other threads:[~2019-06-09 6:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 4:43 bug#36144: 27.0.50; Xref problems Risto Lahe
2019-06-09 6:29 ` Eli Zaretskii [this message]
2019-06-09 9:10 ` Dmitry Gutov
2021-12-05 4:19 ` bug#36144: 27.0.50; xref-show-xrefs-function changed calling convention Lars Ingebrigtsen
2019-06-09 8:59 ` bug#36144: 27.0.50; Xref problems Dmitry Gutov
2019-06-09 9:04 ` Dmitry Gutov
2019-06-09 14:34 ` Dmitry Gutov
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=835zpfcluu.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36144@debbugs.gnu.org \
--cc=laheristo@gmail.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 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).