From: Heime via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
58554@debbugs.gnu.org, stefankangas@gmail.com
Subject: bug#58554: Bash functions with hyphen not showing up in speedbar
Date: Sun, 16 Oct 2022 13:57:15 +0000 [thread overview]
Message-ID: <gUP-KYPvzxboT3Oj0DLJo1wJ1JJJ_yHY9QNkm6Bpfu5DR56bhuPAPAYK6oZWWCzReAgsXeGx33djkEqQhR215PB2NawM0VysKBSJODOWWm4=@protonmail.com> (raw)
In-Reply-To: <8735bomfo3.fsf@yahoo.com>
------- Original Message -------
On Sunday, October 16th, 2022 at 6:43 AM, Po Lu <luangruo@yahoo.com> wrote:
> Eli Zaretskii eliz@gnu.org writes:
>
> > 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).
>
>
> In addition, reporting the same bug multiple times, and under multiple
> aliases, makes life harder for all of us. Not to mention that Heime
> (a.k.a fatiparty, uzibalqa, carlmarcos) has consistently been rude to
> people here, on help-bash and bug-bash, and help-gnu-emacs.
>
> Heime, please don't do that!
Fine. Still you do not know what you are talking about. The fact that some
people believe something is no guarantee of its truth. You are misguided
but then I would think you are not part of the real Gnu Team. Just an imitation.
next prev parent reply other threads:[~2022-10-16 13:57 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 [this message]
2022-10-16 16:42 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
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
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='gUP-KYPvzxboT3Oj0DLJo1wJ1JJJ_yHY9QNkm6Bpfu5DR56bhuPAPAYK6oZWWCzReAgsXeGx33djkEqQhR215PB2NawM0VysKBSJODOWWm4=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=58554@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=heimeborgia@protonmail.com \
--cc=luangruo@yahoo.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 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).