emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: daniela-spit@gmx.it
To: Jean Louis <bugs@gnu.support>
Cc: 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 21:46:27 +0100	[thread overview]
Message-ID: <trinity-438f48cc-fd90-4da3-a2be-8c224df775f2-1606682787444@3c-app-mailcom-bs12> (raw)
In-Reply-To: <X8QBRhAB2fgbWM/7@protected.rcdrun.com>



> Sent: Sunday, November 29, 2020 at 9:15 PM
> From: "Jean Louis" <bugs@gnu.support>
> To: daniela-spit@gmx.it
> Cc: "Org-Mode mailing list" <emacs-orgmode@gnu.org>
> Subject: Re: Emacs inserts hardwired org-agenda-files variable, overwriting user options
>
> * daniela-spit@gmx.it <daniela-spit@gmx.it> [2020-11-29 21:54]:
> > I have identified a problem. Let a user set the files to be used for
> > Org Agenda in .emacs as follows, and consider the situation when the
> > file writing.rcl.org does not exist.
> > 
> > (setq org-agenda-files
> >    '("~/02histr/gadmin/writing.rcl.org"
> >      "~/02histr/gadmin/meeting.rcl.org"
> >      "~/02histr/gadmin/household.rcl.org"))
> > 
> > Emacs demands that the file writing.rcl.org be removed from org-agenda-files.
> > Then Emacs sabotages the user's settings by hardwiring org-agenda-files at the
> > end of the file .emacs by inserting:
> 
> I know that nugging. Look what I have found for variable
> `org-agenda-files' by using inspection with
> {C-h v RET org-agenda-files RET}
> 
> ,----
> | Documentation:
> | The files to be used for agenda display.
> | 
> | If an entry is a directory, all files in that directory that are matched
> | by ‘org-agenda-file-regexp’ will be part of the file list.
> | 
> | If the value of the variable is not a list but a single file name, then
> | the list of agenda files is actually stored and maintained in that file,
> | one agenda file per line.  In this file paths can be given relative to
> | ‘org-directory’.  Tilde expansion and environment variable substitution
> | are also made.
> | 
> | Entries may be added to this list with ‘M-x org-agenda-file-to-front’
> | and removed with ‘M-x org-remove-file’.
> `----
> 
> Maybe you could try the approach to customize it not to be a list by
> single file name. Then in that file name you put files one by one.
 
Yes, but initially people and going to take my dani.el file and if they
happen to delete their file, the whole setup will break down.  

Org should stop trying to delete the file from the list.

One can use 
(file-expand-wildcards "~/02histr/gadmin/*.org")

Not everyone wants agenda to simply use all the files.
For instance I usually want agenda on just a few projects in the
directory.  I have all the files exist now so do not get problems.
 
But, for those coping the file and trying to get it to work is fraught
with difficulties, with emacs trying to do weird things behind your
back.



  reply	other threads:[~2020-11-29 20:48 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
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 [this message]
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=trinity-438f48cc-fd90-4da3-a2be-8c224df775f2-1606682787444@3c-app-mailcom-bs12 \
    --to=daniela-spit@gmx.it \
    --cc=bugs@gnu.support \
    --cc=emacs-orgmode@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 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).