emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Tim Cross <theophilusx@gmail.com>
To: Jeremie Juste <jeremiejuste@gmail.com>
Cc: daniela-spit@gmx.it, emacs-orgmode@gnu.org,
	Jean Louis <bugs@gnu.support>
Subject: Re: Adding Org Files to org-agenda-files
Date: Mon, 30 Nov 2020 11:21:21 +1100	[thread overview]
Message-ID: <87o8jfy9ry.fsf@gmail.com> (raw)
In-Reply-To: <878saj992x.fsf@gmail.com>


Jeremie Juste <jeremiejuste@gmail.com> writes:

> Hello,
>
>>> If you have *both* a settings in your emacs init file for
>>> org-agenda-files using (setq org-agenda-files...) and you have a line in
>>> your (custom ...) section, you should remove one of them to avoid
>>> confusion. In general, what is in the custom section will take
>>> preference as it is usually loaded last. If your going to remove the one
>>> in the custom section, run M-x customize-variable <ret> org-agenda-files
>>> <ret> and then select the options under the 'state' button to 'Erase
>>> Customisation', don't just erase the values in the 'Value Menu' box.
>>
>> Emacs automatically introduced the custom, did not write it myself.
>>
> I fear I might have been the source of the confusion by suggesting
> the command (org-agenda-file-to-front), which has triggered another
> definition of org-agenda-file in the custom-set-variables section.  I
> hadn't realized fully the consequences.
>
> I apologize for this and I hope that it won't turn any user
> against each other. I must confess that among the mailing-lists I have
> subscribed to, this mailing list is the most cordial.
>
> Yes using both the `custom-set-variables` section and setting variable
> can introduce confusion. I am sure many of us have fallen prey to
> (counting me many times).
>
> At the same time it is convenient for some people to be able to
> customize easily some variable and some users might use
> custom-set-variables exclusively.
>
> We just need to understand the consequences of it and I guess many
> users of emacs eventually come to do with these two options and even use
> the best of both world modifying directly variables in the init files
> and using the custom-set-variables section.
>
> It is a bug? I wouldn't say so. Can we explain to (new) users better
> about it? Probably.
>

I think your right. In addition, based on more info which has come out
on the list, I agree with what Kyle has pointed out re: variable to tell
org to ignore missing files. This needs to be referenced in the manual
and the documentation for org-agenda-files.

If nobody else has done it by the time I have finished my current
priorities, I will put a patch together to add such references. This
won't be for a couple of weeks.

--
Tim Cross


  reply	other threads:[~2020-11-30  0:22 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-28 15:39 Adding Org Files to org-agenda-files daniela-spit
2020-11-28 16:51 ` Jeremie Juste
2020-11-28 16:54   ` daniela-spit
2020-11-28 17:01   ` daniela-spit
2020-11-28 17:41     ` Jeremie Juste
2020-11-28 18:12       ` daniela-spit
2020-11-28 18:30       ` daniela-spit
2020-11-28 18:43       ` daniela-spit
2020-11-28 19:01         ` Jeremie Juste
2020-11-28 19:16           ` daniela-spit
2020-11-28 19:26             ` Detlef Steuer
2020-11-28 19:44               ` daniela-spit
2020-11-28 19:55             ` Jeremie Juste
2020-11-28 20:06               ` daniela-spit
2020-11-28 20:11               ` daniela-spit
2020-11-28 20:27                 ` Jeremie Juste
2020-11-28 20:40                   ` daniela-spit
2020-11-28 21:32                     ` Jeremie Juste
2020-11-28 21:45                       ` daniela-spit
2020-11-28 23:18                         ` Jeremie Juste
2020-11-28 23:29                           ` daniela-spit
2020-11-29  1:36                             ` Tim Cross
2020-11-29  2:54                               ` daniela-spit
2020-11-29  3:51                                 ` Tim Cross
2020-11-29  4:05                                   ` daniela-spit
2020-11-29  5:23                                     ` Tim Cross
2020-11-29  9:30                                       ` Jean Louis
2020-11-29  6:50                                     ` Jean Louis
2020-11-29  6:41                                   ` Jean Louis
2020-11-29 12:28                                     ` Ihor Radchenko
2020-11-29 13:00                                       ` Tim Cross
2020-11-29 17:11                                         ` Jean Louis
2020-11-29 17:05                                       ` Jean Louis
2020-12-01  2:24                                         ` Ihor Radchenko
2020-12-01  8:59                                           ` Jean Louis
2020-12-13 15:36                                             ` Ihor Radchenko
2020-12-13 16:27                                               ` steve-humphreys
2020-12-25  2:17                                                 ` Ihor Radchenko
2020-12-13 20:21                                               ` Jean Louis
2020-12-13 20:59                                               ` Tim Cross
2020-12-13 21:59                                                 ` pietru
2020-12-13 23:28                                                 ` Jean Louis
2020-11-29  4:46                             ` Jean Louis
2020-11-29 14:46                               ` daniela-spit
2020-11-29 17:01                                 ` Tim Cross
2020-11-29 17:38                                   ` daniela-spit
2020-11-29 20:55                                     ` Jeremie Juste
2020-11-30  0:21                                       ` Tim Cross [this message]
2020-11-28 23:36                           ` daniela-spit
2020-11-29  5:51                             ` Jean Louis
2020-11-28 20:28                 ` daniela-spit
2020-11-28 18:50       ` 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.orgmode.org/

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

  git send-email \
    --in-reply-to=87o8jfy9ry.fsf@gmail.com \
    --to=theophilusx@gmail.com \
    --cc=bugs@gnu.support \
    --cc=daniela-spit@gmx.it \
    --cc=emacs-orgmode@gnu.org \
    --cc=jeremiejuste@gmail.com \
    /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).