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 17:59:06 +0100	[thread overview]
Message-ID: <trinity-0ffdeee9-bf2b-42f2-8611-f33086a57807-1606669146939__902.596143872358$1606669500$gmane$org@3c-app-mailcom-bs11> (raw)
In-Reply-To: <X8PMXhbf6c9gUrLo@protected.rcdrun.com>

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.

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.

> Sent: Sunday, November 29, 2020 at 5:29 PM
> From: "Jean Louis" <bugs@gnu.support>
> To: "Eli Zaretskii" <eliz@gnu.org>
> Cc: daniela-spit@gmx.it, 44935@debbugs.gnu.org
> Subject: Re: bug#44935: Emacs inserts hardwired org-agenda-files variable, overwriting user options
>
> * Eli Zaretskii <eliz@gnu.org> [2020-11-29 18:08]:
> > Shouldn't this be reported to the Org developers?
>
> We have discussed that Org is part of Emacs and users shall be at all
> time welcome to report their bugs and pointers can be made how to
> closer report to Org mailing list. It makes it confusing to users, and
> is not logical. Org is part of Emacs so it is Emacs bug.
>
> While there is pointer under Org menu how to report the bug, it is not
> as obvious as "Help - Report Bug". So sometimes Org bugs will arrive
> here.
>
> Org bugs should be then simply forwarded to mailing list or tagged as
> being Org so that they may be picked up by mailing list.
>
> I find this more mailing list manager job to properly forward bugs.
>
> For Org one can submit {M-x org-submit-bug-report RET}
>
> For this bug, I do not think it is bug. Isn't it for all variables
> like that that when they are customized by user on top of the init
> file that they customization during the session will overwrite the
> customizations set by user on top of the init file?
>
> If this is so how I think, then users who do not want Emacs to
> overwrite their customization in init file should not use the
> customize for those variables. Then the user's customization will take
> effect.
>
> I do not see differences here with org-agenda.
>
> Are there any?
>





  parent reply	other threads:[~2020-11-29 16:59 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 [this message]
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

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-0ffdeee9-bf2b-42f2-8611-f33086a57807-1606669146939__902.596143872358$1606669500$gmane$org@3c-app-mailcom-bs11' \
    --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).