From: Dmitry Gutov <dgutov@yandex.ru>
To: Risto Lahe <laheristo@gmail.com>, 36144@debbugs.gnu.org
Subject: bug#36144: 27.0.50; Xref problems
Date: Sun, 9 Jun 2019 17:34:16 +0300 [thread overview]
Message-ID: <17ad845a-7171-5c2c-b9dc-9bd357a7d985@yandex.ru> (raw)
In-Reply-To: <7c023e00-b8cd-6298-62f6-93d5b447d6d2@yandex.ru>
On 09.06.2019 12:04, Dmitry Gutov wrote:
> So yeah, you should file reports on the corresponding issues trackers.
FWIW, here's a PR for one of them:
https://github.com/alexmurray/ivy-xref/pull/20
prev parent reply other threads:[~2019-06-09 14:34 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
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 [this message]
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=17ad845a-7171-5c2c-b9dc-9bd357a7d985@yandex.ru \
--to=dgutov@yandex.ru \
--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).