From: Juanma Barranquero <lekktu@gmail.com>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Eli Zaretskii <eliz@gnu.org>, 59575@debbugs.gnu.org
Subject: bug#59575: 29.0.50; add-log-current-defun-header-regexp matches Windows drive letter
Date: Sun, 27 Nov 2022 14:18:45 +0100 [thread overview]
Message-ID: <CAAeL0SShvZLrkkALAaQ_iBPjrbAKQj5i2k6d021PSynCE8GOJw@mail.gmail.com> (raw)
In-Reply-To: <8273f7a6-23d2-b5b6-ffe3-cb3d0f0c26f8@yandex.ru>
[-- Attachment #1: Type: text/plain, Size: 603 bytes --]
On Sun, Nov 27, 2022 at 2:05 PM Dmitry Gutov <dgutov@yandex.ru> wrote:
> I don't mind this approach either, but given that the "definitions" in
> Xref buffers are often only 1 line long, or maybe a few, wouldn't
> showing the file name again somewhere nearby (e.g. the header bar) just
> be redundant?
Sometimes you've got a lot of matches. Also, I tend to display the output
of xref (and, generally speaking, of all kinds of "locating"/"matching"
functions, like occur, etc) in small windows, usually less than ten lines
high. And anyway, this won't bother anyone who's not already using
which-func.
[-- Attachment #2: Type: text/html, Size: 1320 bytes --]
next prev parent reply other threads:[~2022-11-27 13:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 15:53 bug#59575: 29.0.50; add-log-current-defun-header-regexp matches Windows drive letter Juanma Barranquero
2022-11-26 13:03 ` Eli Zaretskii
2022-11-26 13:17 ` Juanma Barranquero
2022-11-27 1:54 ` Dmitry Gutov
2022-11-27 6:49 ` Eli Zaretskii
2022-11-27 12:33 ` Dmitry Gutov
2022-11-27 12:40 ` Juanma Barranquero
2022-11-27 8:29 ` Juanma Barranquero
2022-11-27 11:11 ` Juanma Barranquero
2022-11-27 11:22 ` Juanma Barranquero
2022-11-27 13:04 ` Dmitry Gutov
2022-11-27 13:22 ` Juanma Barranquero
2022-11-27 13:05 ` Dmitry Gutov
2022-11-27 13:18 ` Juanma Barranquero [this message]
2022-11-27 13:41 ` Dmitry Gutov
2022-11-27 14:02 ` Juanma Barranquero
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=CAAeL0SShvZLrkkALAaQ_iBPjrbAKQj5i2k6d021PSynCE8GOJw@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=59575@debbugs.gnu.org \
--cc=dgutov@yandex.ru \
--cc=eliz@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 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.