From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: 46056@debbugs.gnu.org, gnunar@stoffe-pro.net
Subject: bug#46056: hardcoded ~/.emacs.d in elpa package excorporate
Date: Sun, 24 Jan 2021 12:34:26 -0500 [thread overview]
Message-ID: <m3sg6qw865.fsf@fitzsim.org> (raw)
In-Reply-To: <87h7n6vgfu.fsf@gmx.de> (Michael Albinus's message of "Sun, 24 Jan 2021 10:21:09 +0100")
Michael Albinus <michael.albinus@gmx.de> writes:
> Thomas Fitzsimmons <fitzsim@fitzsim.org> writes:
>
>> Hi Gunnar,
>
> Hi Thomas,
>
>> P.S. The results of the following steps don't include this bug report; I
>> wonder why:
>>
>> M-x debbugs-gnu-search RET
>> Enter search phrase: excorporate RET
>> Enter attribute: RET
>
> I suppose it takes time to add this bug to the hyperestraier index. See
> (info "(debbugs-ug) Searching Bugs")
>
> The search engine uses an index over the bug database. This index
> is refreshed daily; search hits may not include recent changes made
> the same day.
OK, thanks for the explanation. I do see this bug report in the results
now. I didn't have the Debbugs UG manual installed until just now when
I upgraded to 0.27. Looks nice!
Is this daily refresh already using incremental registration [1]? Is
performing incremental registration of each bug report as it is filed
infeasible?
Thomas
1. https://dbmx.net/hyperestraier/intro-en.html#deployment
next prev parent reply other threads:[~2021-01-24 17:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-23 18:13 bug#46056: hardcoded ~/.emacs.d in elpa package excorporate Gunnar Horrigmo
2021-01-23 22:31 ` Basil L. Contovounesios
2021-01-24 2:45 ` Gunnar Horrigmo
2021-01-24 3:16 ` Thomas Fitzsimmons
2021-01-24 9:21 ` Michael Albinus
2021-01-24 17:34 ` Thomas Fitzsimmons [this message]
2021-01-24 17:40 ` Michael Albinus
2021-01-24 12:04 ` Basil L. Contovounesios
2021-01-24 12:48 ` Gunnar Horrigmo
2021-01-24 11:58 ` Basil L. Contovounesios
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=m3sg6qw865.fsf@fitzsim.org \
--to=fitzsim@fitzsim.org \
--cc=46056@debbugs.gnu.org \
--cc=gnunar@stoffe-pro.net \
--cc=michael.albinus@gmx.de \
/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.