* bug#58554: Bash functions with hyphen not showing up in speedbar
@ 2022-10-15 14:02 Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-16 4:13 ` Stefan Kangas
0 siblings, 1 reply; 11+ messages in thread
From: Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2022-10-15 14:02 UTC (permalink / raw)
To: 58554
[-- Attachment #1: Type: text/plain, Size: 284 bytes --]
Have seen there was a bug report about bash functions with hyphen not showing up in speedbar. Many
months have passed and would like a solution because I have some bash functions where it would be
good for mo to use hyphen and be able to use the speedbar to access the function names.
[-- Attachment #2: Type: text/html, Size: 547 bytes --]
^ permalink raw reply [flat|nested] 11+ messages in thread
* bug#58554: Bash functions with hyphen not showing up in speedbar
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
0 siblings, 1 reply; 11+ messages in thread
From: Stefan Kangas @ 2022-10-16 4:13 UTC (permalink / raw)
To: Heime, 58554
forcemerge 21477 58554
thanks
Heime via "Bug reports for GNU Emacs, the Swiss army knife of text
editors" <bug-gnu-emacs@gnu.org> writes:
> Have seen there was a bug report about bash functions with hyphen not
^^^^^^^^^^^^^^^^^^^^^^
> showing up in speedbar. Many months have passed and would like a
> solution because I have some bash functions where it would be good for
> mo to use hyphen and be able to use the speedbar to access the
> function names.
(This is a duplicate of bug#21477, so I'm merging them.)
So why are you reporting it again? I note that this is the same bug
that was previously reported as:
Bug#52319 by fatiparty <at> tutanota.com
Bug#52928 by tolugboji <at> protonmail.com
Bug#54265 by angelomolina <at> tutanota.com
Bug#56003 by carlmarcos <at> tutanota.com
Bug#57255 by uzibalqa <uzibalqa <at> proton.me>
You don't get any points for reporting the same bug more than once, and
you especially don't get any for doing it under several different
pseudonyms. It is very easy to see that all of these aliases are in
fact one and the same person.
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.
^ permalink raw reply [flat|nested] 11+ messages in thread
* bug#58554: Bash functions with hyphen not showing up in speedbar
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 6:30 ` Eli Zaretskii
0 siblings, 2 replies; 11+ messages in thread
From: Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2022-10-16 4:19 UTC (permalink / raw)
To: Stefan Kangas; +Cc: 58554
------- Original Message -------
On Sunday, October 16th, 2022 at 4:13 AM, Stefan Kangas <stefankangas@gmail.com> wrote:
> forcemerge 21477 58554
> thanks
>
> Heime via "Bug reports for GNU Emacs, the Swiss army knife of text
> editors" bug-gnu-emacs@gnu.org writes:
>
> > Have seen there was a bug report about bash functions with hyphen not
>
> ^^^^^^^^^^^^^^^^^^^^^^
>
> > showing up in speedbar. Many months have passed and would like a
> > solution because I have some bash functions where it would be good for
> > mo to use hyphen and be able to use the speedbar to access the
> > function names.
>
>
> (This is a duplicate of bug#21477, so I'm merging them.)
>
> So why are you reporting it again? I note that this is the same bug
> that was previously reported as:
>
> Bug#52319 by fatiparty <at> tutanota.com
>
> Bug#52928 by tolugboji <at> protonmail.com
>
> Bug#54265 by angelomolina <at> tutanota.com
>
> Bug#56003 by carlmarcos <at> tutanota.com
>
> Bug#57255 by uzibalqa <uzibalqa <at> proton.me>
>
>
> You don't get any points for reporting the same bug more than once, and
> you especially don't get any for doing it under several different
> pseudonyms. It is very easy to see that all of these aliases are in
> fact one and the same person.
Think whatever you like.
> 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?
^ permalink raw reply [flat|nested] 11+ messages in thread
* bug#58554: Bash functions with hyphen not showing up in speedbar
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
1 sibling, 1 reply; 11+ messages in thread
From: Werner LEMBERG @ 2022-10-16 6:15 UTC (permalink / raw)
To: heimeborgia; +Cc: 58554, stefankangas
>> 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
^ permalink raw reply [flat|nested] 11+ messages in thread
* bug#58554: Bash functions with hyphen not showing up in speedbar
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 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 16:42 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
1 sibling, 2 replies; 11+ messages in thread
From: Eli Zaretskii @ 2022-10-16 6:30 UTC (permalink / raw)
To: Heime; +Cc: 58554, stefankangas
> 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).
^ permalink raw reply [flat|nested] 11+ messages in thread
* bug#58554: Bash functions with hyphen not showing up in speedbar
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
1 sibling, 1 reply; 11+ messages in thread
From: Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2022-10-16 6:43 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 58554, Heime, stefankangas
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!
^ permalink raw reply [flat|nested] 11+ messages in thread
* bug#58554: Bash functions with hyphen not showing up in speedbar
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
0 siblings, 0 replies; 11+ messages in thread
From: Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2022-10-16 13:57 UTC (permalink / raw)
To: Po Lu; +Cc: Eli Zaretskii, 58554, stefankangas
------- 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.
^ permalink raw reply [flat|nested] 11+ messages in thread
* bug#58554: Bash functions with hyphen not showing up in speedbar
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 16:42 ` Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-10-16 16:47 ` Eli Zaretskii
1 sibling, 1 reply; 11+ messages in thread
From: Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2022-10-16 16:42 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 58554, stefankangas
------- 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.
^ permalink raw reply [flat|nested] 11+ messages in thread
* bug#58554: Bash functions with hyphen not showing up in speedbar
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
0 siblings, 1 reply; 11+ messages in thread
From: Eli Zaretskii @ 2022-10-16 16:47 UTC (permalink / raw)
To: Heime; +Cc: 58554, stefankangas
> Date: Sun, 16 Oct 2022 16:42:46 +0000
> From: Heime <heimeborgia@protonmail.com>
> Cc: 58554@debbugs.gnu.org, stefankangas@gmail.com
>
> > 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.
Then please in the future write to the same bug address as the
original report.
^ permalink raw reply [flat|nested] 11+ messages in thread
* bug#58554: Bash functions with hyphen not showing up in speedbar
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
0 siblings, 0 replies; 11+ messages in thread
From: Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2022-10-16 16:56 UTC (permalink / raw)
To: Werner LEMBERG; +Cc: 58554, stefankangas
------- 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.
^ permalink raw reply [flat|nested] 11+ messages in thread
* bug#58554: Bash functions with hyphen not showing up in speedbar
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
0 siblings, 0 replies; 11+ messages in thread
From: Heime via Bug reports for GNU Emacs, the Swiss army knife of text editors @ 2022-10-16 17:39 UTC (permalink / raw)
To: Eli Zaretskii; +Cc: 58554, stefankangas
------- Original Message -------
On Sunday, October 16th, 2022 at 4:47 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Sun, 16 Oct 2022 16:42:46 +0000
> > From: Heime heimeborgia@protonmail.com
> > Cc: 58554@debbugs.gnu.org, stefankangas@gmail.com
> >
> > > 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.
>
>
> Then please in the future write to the same bug address as the
> original report.
Yes Sir.
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2022-10-16 17:39 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
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
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.