all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: daniela-spit@gmx.it
To: Jean Louis <bugs@gnu.support>
Cc: Eli Zaretskii <eliz@gnu.org>, 44935@debbugs.gnu.org
Subject: bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options
Date: Sun, 29 Nov 2020 18:53:46 +0100	[thread overview]
Message-ID: <trinity-da1cf55f-257f-4a5b-8b9b-1f60962cd887-1606672425867@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.

For new users? Will never happen. Put the mailing lists in the damn webpage,
categorising them if necessary, but having them so anybody can see them.
Furthermore, Org is so integrated in Emacs that a large part of the user
community would not be in a position to determine whether it is a problem
of Emacs or Org.

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

God does not exist, get used to it!  Look, if you put the various lists there,
people would use them.  Making things difficult only wakes people give Emacs the
finger rather than concluding the developers are smart.  Does this not bother
Gnu Admins?

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

As long as developers continue thinking they are gods. they will get
no respect.  Grow up and do it quick!




  parent reply	other threads:[~2020-11-29 17:55 UTC|newest]

Thread overview: 39+ 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
2020-11-29 15:12   ` daniela-spit
2020-11-29 15:37     ` Basil L. Contovounesios
2020-11-29 15:37       ` Basil L. Contovounesios
2020-11-29 15:52       ` daniela-spit
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 [this message]
2020-11-29 17:53         ` daniela-spit
2020-11-29 18:08         ` 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
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
2020-11-29 17:59         ` daniela-spit
2021-06-01 15:42           ` Lars Ingebrigtsen
2021-06-01 15:42             ` Lars Ingebrigtsen
2020-11-29 15:07 ` Eli Zaretskii

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

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

  git send-email \
    --in-reply-to=trinity-da1cf55f-257f-4a5b-8b9b-1f60962cd887-1606672425867@3c-app-mailcom-bs12 \
    --to=daniela-spit@gmx.it \
    --cc=44935@debbugs.gnu.org \
    --cc=bugs@gnu.support \
    --cc=eliz@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.