unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 67018@debbugs.gnu.org
Subject: bug#67018: [PATCH] Add autoload cookie to vc-git-grep
Date: Thu, 09 Nov 2023 16:05:32 +0100	[thread overview]
Message-ID: <87ttpv3r2b.fsf@alyssa.is> (raw)
In-Reply-To: <83pm0jynuv.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]

Eli Zaretskii <eliz@gnu.org> writes:

>> From: Alyssa Ross <hi@alyssa.is>
>> Date: Thu,  9 Nov 2023 15:46:30 +0100
>> 
>> ---
>>  lisp/vc/vc-git.el | 1 +
>>  1 file changed, 1 insertion(+)
>> 
>> diff --git a/lisp/vc/vc-git.el b/lisp/vc/vc-git.el
>> index 707fc7cfc07..fe48d5fbd3d 100644
>> --- a/lisp/vc/vc-git.el
>> +++ b/lisp/vc/vc-git.el
>> @@ -1930,6 +1930,7 @@ vc-git-prepare-patch
>>  (defvar compilation-environment)
>>  
>>  ;; Derived from `lgrep'.
>> +;;;###autoload
>>  (defun vc-git-grep (regexp &optional files dir)
>>    "Run git grep, searching for REGEXP in FILES in directory DIR.
>>  The search is limited to file names matching shell pattern FILES.
>
> Thanks, but please explain the motivation.  Which package needs to
> autoload this function and why?

Often running M-x vc-git-grep is the first thing I do after starting
Emacs.  I think it would be good if it was autoloaded, so I didn't have
to M-x load-library vc-git first, or try to set up autoloading just for
myself in my Emacs configuration.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  reply	other threads:[~2023-11-09 15:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-09 14:46 bug#67018: [PATCH] Add autoload cookie to vc-git-grep Alyssa Ross
2023-11-09 14:59 ` Eli Zaretskii
2023-11-09 15:05   ` Alyssa Ross [this message]
2023-11-09 15:13     ` Eli Zaretskii
2023-11-09 19:34       ` Dmitry Gutov
2023-12-24 14:47         ` Stefan Kangas
2023-12-24 16:37           ` Dmitry Gutov
2024-01-11 21:17             ` Stefan Kangas

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=87ttpv3r2b.fsf@alyssa.is \
    --to=hi@alyssa.is \
    --cc=67018@debbugs.gnu.org \
    --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 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).