all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dmitry Gutov <dgutov@yandex.ru>
To: Eli Zaretskii <eliz@gnu.org>
Cc: lekktu@gmail.com, 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:33:55 +0200	[thread overview]
Message-ID: <2b1a90fa-4500-83f2-d76d-4759b03053c4@yandex.ru> (raw)
In-Reply-To: <83edtoriwi.fsf@gnu.org>

On 27/11/22 08:49, Eli Zaretskii wrote:
>> Date: Sun, 27 Nov 2022 03:54:27 +0200
>> Cc:59575@debbugs.gnu.org
>> From: Dmitry Gutov<dgutov@yandex.ru>
>>
>> On 26/11/22 15:03, Eli Zaretskii wrote:
>>> It is also possible to have xref.el define its customized
>>> add-log-current-defun-function, but that sounds like overkill to me.
>>> Dmitry, WDYT?
>> It seems like
>>
>>     (setq add-log-current-defun-function nil)
>>
>> should suffice.
> The value is already nil in the*xref*  buffer, so I'm unsure how will the
> above help.

Sorry, brain fart. I meant

   (setq add-log-current-defun-function #'ignore)





  reply	other threads:[~2022-11-27 12:33 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 [this message]
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
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=2b1a90fa-4500-83f2-d76d-4759b03053c4@yandex.ru \
    --to=dgutov@yandex.ru \
    --cc=59575@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=lekktu@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 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.