From: Tim Cross <firstname.lastname@example.org>
Subject: Re: bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options
Date: Mon, 30 Nov 2020 12:20:02 +1100 [thread overview]
Message-ID: <email@example.com> (raw)
> Sent: Monday, November 30, 2020 at 1:09 AM
>> From: "Tim Cross" <firstname.lastname@example.org>
>> To: email@example.com
>> Subject: Re: bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options
>> firstname.lastname@example.org writes:
>> >> Sent: Sunday, November 29, 2020 at 10:51 PM
>> >> From: "Gyro Funch" <email@example.com>
>> >> To: firstname.lastname@example.org, "Kyle Meyer" <email@example.com>
>> >> Cc: firstname.lastname@example.org
>> >> Subject: Re: bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options
>> >> >
>> >> >> Sent: Sunday, November 29, 2020 at 10:20 PM
>> >> >> From: "Kyle Meyer" <email@example.com>
>> >> >> To: firstname.lastname@example.org
>> >> >> Cc: "gyro funch" <email@example.com>, firstname.lastname@example.org
>> >> >> Subject: Re: bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options
>> >> >>
>> >> >>email@example.com writes:
>> >> >>
>> >> >> >> From: "gyro funch" <firstname.lastname@example.org>
>> >> >> [...]
>> >> >> >> If I'm not mistaken, all of the development is done by volunteers.
>> >> >> >>
>> >> >> >> Perhaps you could help resolve your issue instead of asking other
>> >> >> >> people, who are likely already overworked, to shoulder the burden.
>> >> >> >
>> >> >> > Is there a mailing list for abuse? If I want abuse I shall ask for it.
>> >> >> > Loser!
>> >> >
>> >> >> I don't see anything that gyro said as abuse. Name calling, on the
>> >> >> other hand, has no place on this list.
>> >> >
>> >> >One asks for help, and people tell you to go fix it yourself. If there
>> >> >is any disrespect, you bring it upon yourselves. And now you start.
>> >> >Another Gnu Goon.
>> >> I have found that people on this list are extremely friendly, courteous,
>> >> and helpful.
>> >> I suggest that you look back at the way you asked for/demanded help and
>> >> the various responses you gave in this thread.
>> >> Taking on an attitude of entitlement and showing a lack of respect for
>> >> others, their perspectives, and efforts may not be the best way to get
>> >> help.
>> > Nonsense.
>> Not nonsense at all. You responses have become rude and unhelpful. I can
>> understand how you may be frustrated by the bug reporting situation, but
>> your response to that frustration has been to complain and be critical in
>> a very non-constructive manner. You have now descended into name calling
>> and personal abuse. You are beginning to exhibit behaviour
>> which is not welcome here and which will result in people ignoring your
>> posts. Multiple people have now pointed this out, which should make you
>> stop and think rather than become emotional and respond defensively.
>> the ball is now in your court. How you respond will influence how others
>> respond to your requests and suggestions going forward.
> Look. First I was an an emacs mailing list, then was told that it was not
> the right place. Then was directed to sent it here, etc etc. Then all the
> talk about being volunteers and only do things when they like. WTF!
Even though it might not seem like it, many on this list, including me,
understand your frustration. This is not the first time people have
expressed frustration with how bug reports are managed on the list.
However, what you are likely not ware of are many of the complicating
factors involved which have made it difficult to implement a better
solution. To understand that, you really need to look at the many
threads on both the org and emacs development list where the issue of
bug reporting has been discussed.
You might say you don't care about all of that and just want to be able
to easily report an issue and know it reaches the right people. That is
fair enough. You may even have a need to express that frustration, which
is also fair enough. However, attributing that failure to laziness,
incompetence or lack of interest in doing something is not. Name calling
and personal abuse is unacceptable regardless of the situation or level
Once you have expressed frustration about something, there is little
gained by repetition. At the end of the day, it is how it is and if we
cannot do something about it, such as providing a patch or improve the
documentation or define a new process and work towards getting it
implemented, we either have to accept it or walk away.
next prev parent reply other threads:[~2020-11-30 1:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <trinity-80d8aadc-661f-4964-b2d6-28992e59cda7-1606599247632@3c-app-mailcom-bs11>
2020-11-29 15:07 ` bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options Eli Zaretskii
2020-11-29 15:12 ` daniela-spit
2020-11-29 15:37 ` Basil L. Contovounesios
2020-11-29 15:52 ` daniela-spit
[not found] ` <X8PMXhbf6c9gUrLo@protected.rcdrun.com>
2020-11-29 16:59 ` daniela-spit
[not found] ` <X8PY831MFXCGSLMO@protected.rcdrun.com>
2020-11-29 17:53 ` daniela-spit
2020-11-29 18:08 ` daniela-spit
2020-11-29 23:51 ` Tim Cross
2020-11-30 0:05 ` Christopher Dimech
2020-11-30 8:42 ` tomas
[not found] ` <trinity-57e444a4-55c2-4674-884b-bec92da370e5-1606673304407__39253.1388950133$1606673463$gmane$org@3c-app-mailcom-bs12>
2020-11-29 18:20 ` gyro funch
2020-11-29 18:31 ` daniela-spit
2020-11-29 21:20 ` Kyle Meyer
2020-11-29 21:32 ` daniela-spit
2020-11-29 21:51 ` Re: " Gyro Funch
2020-11-29 22:10 ` daniela-spit
2020-11-30 0:09 ` Tim Cross
2020-11-30 0:26 ` Christopher Dimech
2020-11-30 0:59 ` Tim Cross
2020-11-30 1:27 ` Christopher Dimech
2020-11-30 2:50 ` Tim Cross
2020-11-30 3:19 ` Christopher Dimech
2020-11-30 5:16 ` Jean Louis
2020-11-30 0:51 ` daniela-spit
2020-11-30 1:20 ` Tim Cross [this message]
2020-11-30 5:42 ` Jean Louis
2020-11-29 17:21 ` Eli Zaretskii
2020-11-29 17:39 ` Glenn Morris
2020-11-29 17:59 ` daniela-spit
2021-06-01 15:42 ` Lars Ingebrigtsen
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).