all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Heime via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Werner LEMBERG <wl@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:56:58 +0000	[thread overview]
Message-ID: <COuZDIkJSkAUQJT3TcuSr3USSGx0-_4poW6lGfG9knIIa36ddn_pXfn2JKoKZRr8qnc0M7jKDdmCQZxCnFcP7CR9MFq1SU9100FxUc3wqUQ=@protonmail.com> (raw)
In-Reply-To: <20221016.081527.1515899148009941021.wl@gnu.org>

------- Original Message -------
On Sunday, October 16th, 2022 at 6:15 AM, Werner LEMBERG <wl@gnu.org> wrote:


> > > Please stop reporting duplicate bug reports. It is a waste of time
> > > and energy. It also makes it much more likely that your bug reports
> > > will simply be ignored in the future. Thanks in advance.
> > 
> > Ignoring bug reports as act of spite. Is this a new trend?
> 
> 
> You are missing the point. Saying 'ping' to a bug report is fully
> valid – and even quite useful so that the Emacs maintainers know that
> there is still interest in resolving the problem at hand. Doing this
> without referring to the original bug report number creates a new
> report, which means more administrative work nobody really likes to
> do, and which becomes annoying if this happens repeatedly. And yes,
> such annoyance eventually leads to ignoring a bug report, which
> essentially means that the report's priority is set to a very low
> value.
> 
> Please always bear in mind that maintaining Emacs is an unpaid job
> done in spare time for fun. Fixing bugs is especially unthankful, and
> being annoyed reduces the fun factor enormously.

> Werner

Shall keep your comments in mind.  Have heard people here screaming about 
wanting to get paid.  It is a shame that people contribute to the project
when they are still in a survival situation.  To work with love and devotion,
one has to raise oneself beyond survival to be a contributing member of society.

As for myself, fixing bugs is the most rewarding part.  Have been involved in
marshaling the fixing bugs for many years in industrial settings.  But here people
do not seem to be at ease.





  reply	other threads:[~2022-10-16 16:56 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 [this message]
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
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='COuZDIkJSkAUQJT3TcuSr3USSGx0-_4poW6lGfG9knIIa36ddn_pXfn2JKoKZRr8qnc0M7jKDdmCQZxCnFcP7CR9MFq1SU9100FxUc3wqUQ=@protonmail.com' \
    --to=bug-gnu-emacs@gnu.org \
    --cc=58554@debbugs.gnu.org \
    --cc=heimeborgia@protonmail.com \
    --cc=stefankangas@gmail.com \
    --cc=wl@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 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.