emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Christopher Dimech <dimech@gmx.com>
To: Tim Cross <theophilusx@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options
Date: Mon, 30 Nov 2020 02:27:39 +0100	[thread overview]
Message-ID: <trinity-c89c9c65-7e86-4426-890c-02790ef5f0bf-1606699659669@3c-app-mailcom-bs12> (raw)
In-Reply-To: <87lfejy80o.fsf@gmail.com>

> Sent: Monday, November 30, 2020 at 1:59 AM
> From: "Tim Cross" <theophilusx@gmail.com>
> To: "Christopher Dimech" <dimech@gmx.com>
> Cc: emacs-orgmode@gnu.org
> Subject: Re: bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options
>
>
> Christopher Dimech <dimech@gmx.com> writes:
>
> >> Sent: Monday, November 30, 2020 at 1:09 AM
> >> From: "Tim Cross" <theophilusx@gmail.com>
> >> To: emacs-orgmode@gnu.org
> >> Subject: Re: bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options
> >>
> >>
> >> daniela-spit@gmx.it writes:
> >>
> >> >> Sent: Sunday, November 29, 2020 at 10:51 PM
> >> >> From: "Gyro Funch" <gyromagnetic@gmail.com>
> >> >> To: daniela-spit@gmx.it, "Kyle Meyer" <kyle@kyleam.com>
> >> >> Cc: emacs-orgmode@gnu.org
> >> >> Subject: Re[2]: bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options
> >> >>
> >> >> >
> >> >> >>  Sent: Sunday, November 29, 2020 at 10:20 PM
> >> >> >>  From: "Kyle Meyer" <kyle@kyleam.com>
> >> >> >>  To: daniela-spit@gmx.it
> >> >> >>  Cc: "gyro funch" <gyromagnetic@gmail.com>, emacs-orgmode@gnu.org
> >> >> >>  Subject: Re: bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options
> >> >> >>
> >> >> >>daniela-spit@gmx.it writes:
> >> >> >>
> >> >> >>  >> From: "gyro funch" <gyromagnetic@gmail.com>
> >> >> >>  [...]
> >> >> >>  >> 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.
> >
> > Please be aware that it was pointed out that one can configure
> > org-agenda-skip-unavailable-files to a non-nil value if she wants
> > non-existing/unreadable files to be skipped.
> >
> > But that option isn't mentioned in the manual or the docstring of the
> > org-agenda-files option.  The problem is known and has been a source of great
> > frustration, that's why it was introduced.
> >
> > Daniela is quite right.  If multiple people don't want to help her, that's
> > fine, many others will.
> >
>
> The issue at this point wasn't about whether there is a problem with how
> org manages org-agenda-files or even the acknowledged weakness in the
> documentation which needs a patch. The issue here is about attitude and
> being respectful.
>
> We can disagree on things. Opposing views are a good thing provided the
> expression of these opposing views is done with respect. This means no
> personal attacks, no calling names, no personal abuse.
>
> We all have different levels of sensitivity and some have thicker skin
> than others. However, once multiple people express the opinion that an
> attitude is not appropriate for the list, the responsibility is with the
> originator to consider that feedback and either adjust to meet community
> expectations, leave the community or continue without change and accept
> whatever consequences (if any) the list decides is appropriate.

Ok, let me deal with this.  But please, can we be better ourselves.  Am
sure she wanted to send a report so things get better for others.  She
knew how to solve the problem by only putting a list of files that exist.

Furthermore, we are updating the manual on the available option that
addressed her problem, a detail that was most likely obscure.  Some good
she has done.  We are not doing the work specifically for her,
but to everybody.  Agreed?


> --
> Tim Cross
>


  reply	other threads:[~2020-11-30  1:31 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[2]: " 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 [this message]
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
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

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=trinity-c89c9c65-7e86-4426-890c-02790ef5f0bf-1606699659669@3c-app-mailcom-bs12 \
    --to=dimech@gmx.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=theophilusx@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/org-mode.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).