unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: daniela-spit@gmx.it
To: Jean Louis <bugs@gnu.support>
Cc: 44935@debbugs.gnu.org
Subject: bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options
Date: Sun, 29 Nov 2020 19:08:24 +0100	[thread overview]
Message-ID: <trinity-57e444a4-55c2-4674-884b-bec92da370e5-1606673304407@3c-app-mailcom-bs12> (raw)
In-Reply-To: <X8PY831MFXCGSLMO@protected.rcdrun.com>



> 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!

> There is:
>
> - report-calc-bug
> - calc-report-bug
> - c-submit-bug-report
> - TeX-submit-bug-report
> - org and Emacs maybe others
>
> > You look at "Emacs Asking for help" and "Emacs Reporting bugs" and you get only two things
> > help-gnu-emacs@gnu.org and bug-gnu-emacs@gnu.org.  Have been following discussions here
> > and people herd together telling others they are doing everything backwards. And insisting
> > everything is fine, makes serious people not happy at all.  I do not want to hurt anyone,
> > but there exists a wall between maintainers and users who basically use Gnu Tools to do
> > something else.
>
> Users could assign to themselves specific level such as Beginner,
> Intermediate, Advance and God.
>
> Beginner would be welcomed to submit bugs and kindly explained that
> there exists specialized mailing list with more people able to help
> it.
>
> Intermediate user would be simply told to go somewhere else.
>
> Advanced user would be anyway submitting patches and be active in
> Emacs development, so there would be no problem with this level.
>
> God would never tell anything to anybody just as what is usual that
> God does, I guess M-x something...
>
>





      parent reply	other threads:[~2020-11-29 18:08 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-28 21:34 bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options daniela-spit
2020-11-29 15:07 ` Eli Zaretskii
     [not found] ` <837dq4mcb1.fsf@gnu.org>
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
2020-11-29 17:21     ` Eli Zaretskii
2020-11-29 17:39       ` Glenn Morris
2020-11-29 17:59         ` daniela-spit
     [not found]         ` <trinity-4ce650a4-ddc3-4a15-adfe-2402d5074be1-1606672748859@3c-app-mailcom-bs12>
2021-06-01 15:42           ` Lars Ingebrigtsen
     [not found]     ` <trinity-0ffdeee9-bf2b-42f2-8611-f33086a57807-1606669146939@3c-app-mailcom-bs11>
     [not found]       ` <X8PY831MFXCGSLMO@protected.rcdrun.com>
2020-11-29 17:53         ` daniela-spit
2020-11-29 18:08         ` daniela-spit [this message]

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.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=trinity-57e444a4-55c2-4674-884b-bec92da370e5-1606673304407@3c-app-mailcom-bs12 \
    --to=daniela-spit@gmx.it \
    --cc=44935@debbugs.gnu.org \
    --cc=bugs@gnu.support \
    /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.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).