From: Kyle Meyer <kyle@kyleam.com>
To: daniela-spit@gmx.it
Cc: Tom Gillespie <tgbugs@gmail.com>,
Org-Mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: Emacs inserts hardwired org-agenda-files variable, overwriting user options
Date: Sun, 29 Nov 2020 16:02:14 -0500 [thread overview]
Message-ID: <87im9nri5l.fsf@kyleam.com> (raw)
In-Reply-To: <trinity-32f38b35-9f65-4ae3-9c1d-4c4507f728bc-1606681185824@3c-app-mailcom-bs12>
daniela-spit@gmx.it writes:
>> From: "Tom Gillespie" <tgbugs@gmail.com>
[...]
>> If you have that then your list will be retained. However Emacs will
>> probably continue to ask you to remove the missing file until some
>> file exists at that path. Not sure about the org agenda behavior for
>> missing files since I populate org-agenda-files by scanning folders
>> for existing org files and then having a blacklist to exclude files I
>> do not want.
>
> Yes it gives you hell in its demand to delete or abort, rather than
> ignoring the file.
>
> That's why I called the problem a bug. If you don't find the file, ignore it.
If you want non-existing/unreadable files to be skipped, you can
configure org-agenda-skip-unavailable-files to a non-nil value.
That option unfortunately isn't mentioned in the manual or the docstring
of the org-agenda-files option. If anyone is interested, a patch
improving the documentation would of course be appreciated.
next prev parent reply other threads:[~2020-11-29 21:04 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-29 18:52 Emacs inserts hardwired org-agenda-files variable, overwriting user options daniela-spit
2020-11-29 20:07 ` Tom Gillespie
2020-11-29 20:19 ` daniela-spit
2020-11-29 21:01 ` Tom Gillespie
2020-11-29 21:02 ` Kyle Meyer [this message]
2020-11-29 22:08 ` daniela-spit
2020-12-11 3:59 ` TRS-80
2020-12-11 4:16 ` daniela-spit
2020-12-11 4:32 ` daniela-spit
2020-12-11 8:25 ` tomas
2020-12-11 13:47 ` daniela-spit
2020-12-11 13:59 ` Detlef Steuer
2020-12-11 14:18 ` daniela-spit
2020-12-11 14:23 ` Christopher Dimech
2020-12-11 14:26 ` Ihor Radchenko
2020-12-11 14:47 ` daniela-spit
2020-12-12 2:35 ` Jean Louis
2020-12-12 2:41 ` daniela-spit
2020-12-13 5:19 ` Jean Louis
2020-12-13 5:51 ` daniela-spit
2020-12-13 13:19 ` Jean Louis
2020-12-13 17:49 ` Christopher Dimech
2020-12-13 20:28 ` Jean Louis
2020-12-13 3:33 ` TRS-80
2020-12-13 8:46 ` Jean Louis
2020-12-13 9:28 ` Ihor Radchenko
2020-12-13 17:31 ` Jean Louis
2020-12-13 17:57 ` Christopher Dimech
2020-12-13 17:59 ` Christopher Dimech
2020-12-14 12:49 ` Ihor Radchenko
2020-12-14 19:39 ` Jean Louis
2020-12-11 14:43 ` tomas
2020-12-11 14:54 ` daniela-spit
2020-12-11 15:46 ` tomas
2020-12-11 15:58 ` daniela-spit
2020-12-11 6:25 ` Jean Louis
2020-11-29 20:15 ` Jean Louis
2020-11-29 20:46 ` daniela-spit
2020-11-29 20:58 ` Jean Louis
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=87im9nri5l.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=daniela-spit@gmx.it \
--cc=emacs-orgmode@gnu.org \
--cc=tgbugs@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).