emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
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
Date: Mon, 30 Nov 2020 08:42:32 +0300	[thread overview]
Message-ID: <X8SGSJDiy7ivVm53@protected.rcdrun.com> (raw)
In-Reply-To: <trinity-4f6d2154-e65b-4d97-8c40-d16a08b44421-1606674690171@3c-app-mailcom-bs12>

> > From: "gyro funch" <gyromagnetic@gmail.com>
> > To: emacs-orgmode@gnu.org
> > Subject: Re: bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options
> > 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.

Those overworked, to shoulder the burden people need not answer any
issue. They are volunteers, so they need not answer. There will be
those who may answer.

Process I see there is:

- please report the bug! You are welcome
- user reports the bug
- why you reported the bug here? Report somewhere else.
- user asks where to report the bug and wonders why that routing
- user does report the bug to other place
- user is told not to ask other people

While all that has deeper meanings for one set of people and one may
understand it, there will be those pissed off who cannot understand
what is happening.

Please look at processes going on, analyze processes and what those
processes are not well designed when we have Emacs with programming
language to route users accordingly.

In the end neither developers will get insights from users about
potential bugs neither users will resolve the issue.

Final question is if problem with org-agenda-files got resolved?



  parent reply	other threads:[~2020-11-30 10:37 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 ` 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
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 [this message]
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=X8SGSJDiy7ivVm53@protected.rcdrun.com \
    --to=bugs@gnu.support \
    --cc=daniela-spit@gmx.it \
    --cc=emacs-orgmode@gnu.org \
    --cc=gyromagnetic@gmail.com \
    --subject='Re: bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options' \
    /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

Code repositories for project(s) associated with this 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).