emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: daniela-spit@gmx.it
To: TRS-80 <trs-80@isnotmyreal.name>
Cc: Tom Gillespie <tgbugs@gmail.com>, Kyle Meyer <kyle@kyleam.com>,
	Emacs-orgmode
	<emacs-orgmode-bounces+orgmode.trs-80=isnotmyreal.name@gnu.org>,
	Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Emacs inserts hardwired org-agenda-files variable, overwriting user options
Date: Fri, 11 Dec 2020 05:32:39 +0100	[thread overview]
Message-ID: <trinity-e1bf4c60-3c78-4e5b-b536-70d25bc05705-1607661159060@3c-app-mailcom-bs06> (raw)
In-Reply-To: <7330ab95c71d5d41d7fa6faffeaf300f@isnotmyreal.name>



> Sent: Friday, December 11, 2020 at 4:59 AM
> From: "TRS-80" <trs-80@isnotmyreal.name>
> To: daniela-spit@gmx.it
> Cc: "Kyle Meyer" <kyle@kyleam.com>, "Tom Gillespie" <tgbugs@gmail.com>, "Org-Mode mailing list" <emacs-orgmode@gnu.org>, "Emacs-orgmode" <emacs-orgmode-bounces+orgmode.trs-80=isnotmyreal.name@gnu.org>
> Subject: Re: Emacs inserts hardwired org-agenda-files variable, overwriting user options
>
> On 2020-11-29 17:08, daniela-spit@gmx.it wrote:
> >
> > Yes, there are problems with the documentation.  I noticed recently
> > that
> > some guy criticised the manual, and so many got super defensive.  You
> > should
> > give him a medal for telling you how things are.
>
> I guess in my mind, complaining about the manual, to a bunch of
> volunteers and fellow users, is probably on the pretty unhelpful end of
> the scale.
>
> Making constructive criticism is then slightly better, at least you are
> not deriding (mostly volunteer) people's work and effort.  Although not
> by much, as this still does not require too much effort.
>
> However submitting a patch with an improvement to the documentation is
> quite valuable.  Pretty much on the opposite end of the scale in fact.
> And thus, only this level of contribution "deserves a medal" as far as I
> am concerned.
>
> I was not privy to particulars of conversation you mention, although I
> have seen this sort of entitled attitude often enough in F/LOSS to have
> somewhat of an idea of how it might have played out.
>
> Entitled users becoming demanding of things they expect (for free, no
> less) is not just a drag, it's the cancer that slowly kills F/LOSS
> projects.  As eventually actually valuable contributors (maintainers,
> devs, etc.) have had enough of it, get burnt out and leave the project.
> I have seen it far too many times over the years.
>
> So I imagine what you witnessed was a sort of natural defense mechanism,
> protecting the overall health of the community and project by having a
> strong reaction to such negative attitudes.

There are problems in Org-Agenda my friend.  And quite some confusion
on what mailing list to use.  Only one mailing list is mentioned, then
people start sending you here and there.  At other times, things are done
in a piecemeal process.  Elisp can be challenging and you will not learning
in school.  There needs to be some intermediate level manual if you want
people to get good enough to help the project.  I am quite sure that some
people do spend a long time testing the code.


> Cheers,
> TRS-80
>


  parent reply	other threads:[~2020-12-11  4:58 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-29 18:52 Emacs inserts hardwired org-agenda-files variable, overwriting user options daniela-spit
2020-11-29 20:07 ` Tom Gillespie
2020-11-29 20:19   ` daniela-spit
2020-11-29 21:01     ` Tom Gillespie
2020-11-29 21:02     ` Kyle Meyer
2020-11-29 22:08       ` daniela-spit
2020-12-11  3:59         ` TRS-80
2020-12-11  4:16           ` daniela-spit
2020-12-11  4:32           ` daniela-spit [this message]
2020-12-11  8:25             ` tomas
2020-12-11 13:47               ` daniela-spit
2020-12-11 13:59                 ` Detlef Steuer
2020-12-11 14:18                   ` daniela-spit
2020-12-11 14:23                   ` Christopher Dimech
2020-12-11 14:26                 ` Ihor Radchenko
2020-12-11 14:47                   ` daniela-spit
2020-12-12  2:35                   ` Jean Louis
2020-12-12  2:41                     ` daniela-spit
2020-12-13  5:19                       ` Jean Louis
2020-12-13  5:51                         ` daniela-spit
2020-12-13 13:19                           ` Jean Louis
2020-12-13 17:49                             ` Christopher Dimech
2020-12-13 20:28                               ` Jean Louis
2020-12-13  3:33                     ` TRS-80
2020-12-13  8:46                       ` Jean Louis
2020-12-13  9:28                         ` Ihor Radchenko
2020-12-13 17:31                           ` Jean Louis
2020-12-13 17:57                             ` Christopher Dimech
2020-12-13 17:59                             ` Christopher Dimech
2020-12-14 12:49                             ` Ihor Radchenko
2020-12-14 19:39                               ` Jean Louis
2020-12-11 14:43                 ` tomas
2020-12-11 14:54                   ` daniela-spit
2020-12-11 15:46                     ` tomas
2020-12-11 15:58                       ` daniela-spit
2020-12-11  6:25           ` Jean Louis
2020-11-29 20:15 ` Jean Louis
2020-11-29 20:46   ` daniela-spit
2020-11-29 20:58     ` Jean Louis

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-e1bf4c60-3c78-4e5b-b536-70d25bc05705-1607661159060@3c-app-mailcom-bs06 \
    --to=daniela-spit@gmx.it \
    --cc=emacs-orgmode-bounces+orgmode.trs-80=isnotmyreal.name@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=kyle@kyleam.com \
    --cc=tgbugs@gmail.com \
    --cc=trs-80@isnotmyreal.name \
    /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).