From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Csepp <raingloom@riseup.net>
Cc: GNU Debbugs <control@debbugs.gnu.org>, 61882@debbugs.gnu.org
Subject: bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues
Date: Tue, 10 Oct 2023 21:47:13 -0400 [thread overview]
Message-ID: <8734yiexr2.fsf@gmail.com> (raw)
In-Reply-To: <cuca5sqf5eo.fsf@riseup.net> (Csepp's message of "Wed, 11 Oct 2023 00:52:51 +0200")
tags 61882 = moreinfo unreproducible
quit
Hi,
Csepp <raingloom@riseup.net> writes:
> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>
>> Hi,
>>
>> Csepp <raingloom@riseup.net> writes:
>>
>>> Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
>>>
>>>> tags 61882 +notabug
>>>> quit
>>>
>>> I don't think notabug applies until we actually know the root cause.
>>
>> Sadly I don't think there's anything actionable here until you can
>> reproduce the problem and share the recipe with us, so I wanted to close
>> the issue without it being marked as "resolved".
>
> Neither "resolved" nor "notabug" are applicable. If stalled incident
> reports / issues are a problem, they should probably be marked as
> stalled, or needinfo, for easy filtering. Marking it as notabug is just
> going to make the job of the next person harder when they search for
> issues related to these symptoms.
I don't think a bug as particular as 'my profile got corrupted' without
any way to recreate it has much value; it's also the first time I've
heard of such a report. That's why I'd prefer to treat it as an oddity
and close it; if it reproduces (by you or others) let's reopen it, with
fresh and clear information.
> I appreciate all the work going into closing old issues, but I don't
> think chasing a low open issue count should be a goal unto itself
> See https://fvsch.com/stale-bots .
To be clear, I wholly agree. I've now tagged it as moreinfo and
unreproducible.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-10-11 1:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-01 2:58 bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues Csepp
2023-03-01 9:25 ` Liliana Marie Prikler
2023-03-01 11:16 ` Csepp
2023-03-01 14:40 ` bokr
2023-03-01 16:11 ` Csepp
2023-03-02 7:11 ` Liliana Marie Prikler
2023-03-02 12:39 ` Csepp
[not found] ` <handler.61882.B.167763983720587.ack@debbugs.gnu.org>
2023-04-06 14:59 ` bug#61882: profile is frozen / packages can't be installed Csepp
2023-10-04 2:54 ` bug#61882: emacs-next-pgtk does not find emacs-org-roam, other path issues Maxim Cournoyer
2023-10-08 14:29 ` Csepp
2023-10-08 20:51 ` Maxim Cournoyer
2023-10-10 22:52 ` Csepp
2023-10-11 1:47 ` Maxim Cournoyer [this message]
2023-10-15 20:06 ` Csepp
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=8734yiexr2.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=61882@debbugs.gnu.org \
--cc=control@debbugs.gnu.org \
--cc=raingloom@riseup.net \
/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/guix.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.