emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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
Date: Sun, 29 Nov 2020 11:20:13 -0700	[thread overview]
Message-ID: <d077a3b2-dca8-c08e-2687-4b5eb7c4cc05@gmail.com> (raw)
In-Reply-To: <trinity-57e444a4-55c2-4674-884b-bec92da370e5-1606673304407__39253.1388950133$1606673463$gmane$org@3c-app-mailcom-bs12>

On 11/29/2020 11:08 AM, daniela-spit@gmx.it wrote:
> 
> 
>> Sent: Sunday, November 29, 2020 at 6:22 PM
>> From: "Jean Louis" <bugs@gnu.support>
>> To: daniela-spit@gmx.it
>> Cc: "Eli Zaretskii" <eliz@gnu.org>, 44935@debbugs.gnu.org
>> Subject: Re: bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options
>>
>> * daniela-spit@gmx.it <daniela-spit@gmx.it> [2020-11-29 20:02]:
>>> Correct, everything tells you it is part of Emacs.  Then one sends a report and people
>>> start sending in in a long winded road to find the appropriate
>>> channel.
>>
>> We can consider those features of reporting bugs still in
>> development. I never knew since recently that there are various
>> reporting bug functions. You can discover it easier by using
>> completion such as ivy package.
> 
> Still in development?  How much thinking do people have to do
> for this.  I can make 34 mailing lists in a few hours!
> 


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.

-gyro



  parent reply	other threads:[~2020-11-29 18: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 [this message]
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
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=d077a3b2-dca8-c08e-2687-4b5eb7c4cc05@gmail.com \
    --to=gyromagnetic@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    /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).