From: Heime via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 58554@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#58554: Bash functions with hyphen not showing up in speedbar
Date: Sun, 16 Oct 2022 16:42:46 +0000 [thread overview]
Message-ID: <TVix8cBzmOWydfvSKrWQzomlEpRcQHfftrYUW_xS5Xfv-dURU05PaLt3KE2D9l66umHRB3WLPgqJzJdGATqjWCHSh5ufqTE9Mp3ioOjNZRA=@protonmail.com> (raw)
In-Reply-To: <835ygk5lgl.fsf@gnu.org>
------- Original Message -------
On Sunday, October 16th, 2022 at 6:30 AM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Cc: 58554@debbugs.gnu.org
> > Date: Sun, 16 Oct 2022 04:19:35 +0000
> > From: Heime via "Bug reports for GNU Emacs,
> > the Swiss army knife of text editors" bug-gnu-emacs@gnu.org
> >
> > Ignoring bug reports as act of spite. Is this a new trend?
>
>
> Bug reports are not ignored here. But we don't always have ideas for
> how to solve a particular bug, or the manpower or expertise to work on
> that. Then the bug could, unfortunately, stay unsolved for prolonged
> periods of time.
>
> Pinging an unsolved bug report is OK. But reporting it again under a
> different number just adds to the workload of the maintainers, so
> please make a point of pinging the original bug report (by replying to
> the same NNNN@debbugs.gnu.org address, where NNNN is the original bug
> number).
I am new to this and unaware about pinging an unsolved bug report. That's
what I had in mind.
next prev parent reply other threads:[~2022-10-16 16:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-15 14:02 bug#58554: Bash functions with hyphen not showing up in speedbar Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-16 4:13 ` Stefan Kangas
2022-10-16 4:19 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-16 6:15 ` Werner LEMBERG
2022-10-16 16:56 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-16 6:30 ` Eli Zaretskii
2022-10-16 6:43 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-16 13:57 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-16 16:42 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-10-16 16:47 ` Eli Zaretskii
2022-10-16 17:39 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
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='TVix8cBzmOWydfvSKrWQzomlEpRcQHfftrYUW_xS5Xfv-dURU05PaLt3KE2D9l66umHRB3WLPgqJzJdGATqjWCHSh5ufqTE9Mp3ioOjNZRA=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=58554@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=heimeborgia@protonmail.com \
--cc=stefankangas@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.