From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id AATgIFD7wl+cawAA0tVLHw (envelope-from ) for ; Sun, 29 Nov 2020 01:37:20 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id 2JiGHFD7wl/ZPwAAbx9fmQ (envelope-from ) for ; Sun, 29 Nov 2020 01:37:20 +0000 Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id B4E06940416 for ; Sun, 29 Nov 2020 01:37:19 +0000 (UTC) Received: from localhost ([::1]:40026 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kjBeP-0001st-Po for larch@yhetil.org; Sat, 28 Nov 2020 20:37:17 -0500 Received: from eggs.gnu.org ([2001:470:142:3::10]:42502) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kjBdl-0001sk-4T for emacs-orgmode@gnu.org; Sat, 28 Nov 2020 20:36:37 -0500 Received: from mail-pg1-x52d.google.com ([2607:f8b0:4864:20::52d]:33652) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kjBdj-0007vc-2H for emacs-orgmode@gnu.org; Sat, 28 Nov 2020 20:36:36 -0500 Received: by mail-pg1-x52d.google.com with SMTP id o4so5161762pgj.0 for ; Sat, 28 Nov 2020 17:36:34 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=references:user-agent:from:to:subject:in-reply-to:message-id:date :mime-version; bh=r+JfQRnzWvjD1xOtuAAh8ob5BjwqDpjjvhE4KUjVFpo=; b=VYPYWd+ZJWBrfrkEOy3hT6AtPdsGsvj6IwvXDAlbDHKx4+OUoOySXeG3KekPouUQjK 3RfAzour/7BX5iPitUnhjLU6dH2pdQtXPh94vN/4e2bq9AZWepxSfNExp26fIv65dCZr acpFSorvtWr/Gd2iHCwQzwtdPsrVCfqVGJLKE48fLb5D4JR9xXnc18mUvjhe6KfFFCgM NVH1VLuuX2q8FrumXgZHRMpO+AylTTAta66OLD5PdTiN63NoQ47pbotF7A8rwoIlfbW3 PslrGE67ZpXrrpEIDvRmy7Odg4Q6TxsVHUozaCjwFbi8zedaUqTSqc1dupeHrkXQ/bDV F90Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:subject :in-reply-to:message-id:date:mime-version; bh=r+JfQRnzWvjD1xOtuAAh8ob5BjwqDpjjvhE4KUjVFpo=; b=G0N9d4dMTjtKn/jS5ITyDe/sFiK+H6NEetiiyriIgt5Fy3D3XiszXPsq9KSVt0I6Zt HGIK7dJOauLD+i8cNSMoKuJXmLl2I5fEsDiwRGHKRD0YmhMQCXd/w03lxfj9miijf8xd tQdiTy0sA43RH9tT3YjQTbJUf3EDfZw23ytnzf/tQYU00ZImOBIN+LNbs7wE8PXUPj2i ICJhgdkU3hwBAQamhXbCzi0p51rXJoQu2GxFRHIWLZbIzRzAjLJNJ3o4CSTT0t+qixwv rsUBEsji5ZBuvfxC/SgLdmJ6YiAFjLR871Bf4Bd1p8M8PWJC6rFQ4BjLwq+Ytph+QZK5 4fmg== X-Gm-Message-State: AOAM532XSSYfpURXE6iaYVKdVxIVzX8bubA1t2Q6a7uyNvtde0oOxNg9 B8BMhxf4gFEE/UoJjxOqDcIbe3rb2RSoSg== X-Google-Smtp-Source: ABdhPJzUY1sbSPXQzVdzN/8pGxKR0yGJRarg243eMb0zUUHaFKVNeRSbv/NjhaqnMAsZU2JjDyGsAA== X-Received: by 2002:a17:90a:8586:: with SMTP id m6mr18625625pjn.9.1606613792905; Sat, 28 Nov 2020 17:36:32 -0800 (PST) Received: from tim-desktop (106-69-142-109.dyn.iinet.net.au. [106.69.142.109]) by smtp.gmail.com with ESMTPSA id i16sm11581745pfr.183.2020.11.28.17.36.30 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 28 Nov 2020 17:36:31 -0800 (PST) References: <87tut9fmqx.fsf@gmail.com> <87mtz1fkfx.fsf@gmail.com> <87ft4tfgpv.fsf@gmail.com> <874kl9fe7m.fsf@gmail.com> <87wny5dy6j.fsf@gmail.com> <87r1od181i.fsf@gmail.com> <87h7p9135u.fsf@gmail.com> User-agent: mu4e 1.5.7; emacs 27.1.50 From: Tim Cross To: emacs-orgmode@gnu.org Subject: Re: Adding Org Files to org-agenda-files In-reply-to: Message-ID: <87sg8tymeb.fsf@gmail.com> Date: Sun, 29 Nov 2020 12:36:28 +1100 MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2607:f8b0:4864:20::52d; envelope-from=theophilusx@gmail.com; helo=mail-pg1-x52d.google.com X-Spam_score_int: -10 X-Spam_score: -1.1 X-Spam_bar: - X-Spam_report: (-1.1 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: "Emacs-orgmode" X-Migadu-Flow: FLOW_IN X-Migadu-Spam-Score: -2.97 X-Scanner: ns3122888.ip-94-23-21.eu Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20161025 header.b=VYPYWd+Z; dmarc=pass (policy=none) header.from=gmail.com; spf=pass (aspmx1.migadu.com: domain of emacs-orgmode-bounces@gnu.org designates 209.51.188.17 as permitted sender) smtp.mailfrom=emacs-orgmode-bounces@gnu.org X-TUID: rdDFKYek25tZ daniela-spit@gmx.it writes: >> Sent: Sunday, November 29, 2020 at 12:18 AM >> From: "Jeremie Juste" >> To: daniela-spit@gmx.it >> Cc: "Org-Mode mailing list" >> Subject: Re: Adding Org Files to org-agenda-files >> >> || On Saturday, 28 Nov 2020 at 22:45, daniela-spit@gmx.it wrote: >> > >> > Many thanks for helping me. I would not have got to this stage without >> > your helpful commands and checks. >> You are welcome ;-) >> > >> > Getting used to a problem to the extent of depending on it is not a good system. >> > Emacs should follow what the user demands by default, with perhaps the option >> > for the user to change that behaviour. But it is the user that should demand >> > it. In situations when Emacs gets to do something so drastic, it should inform >> > the user what is happening and put that information in a log file. >> What you see as a problem some see as a solution. For instance, it depends how many >> org-files you want to add to the agenda. Some users including me have 2 >> or three files in org-agenda-files so I never interact with this >> variable directly. > > I have many and they change quite frequently, depending on project. > So often torture emacs hard. Have sent a bug-report about it. Keen > for a change to go through. > What was the bug tracking number? I'd be interested in seeing what you are wanting or what exactly you feel is a bug. >From following the thread and adding a lot of assumptions/guess work, I think there are quite a few options to satisfy your requirements. Some of them are fairly easy, some may need some basic elisp and some may require a shift in user perspective. The choice depends a lot on what the user is comfortable with. This list is often really good at providing assistance. However, often it is better to also outline what your actual high-level goal is rather than as how to do a specific step in what you believe is the answer to achieving your goal. Org mode is a powerful and feature rich system which can take a bit of time to really understand. Sometimes, what you believe is the solution to your problem can turn out to be something which already exists, but in a slightly different form, so is not recognised, or maybe is a bad idea or perhaps can be achieved easily by slightly modifying the requirements in a way that does not impact on the final goal. As an example, you asked how to send a capture buffer to two files. It would be good to understand why you want to do this because on the face of it, there are some really good reasons NOT to do this. For example, this will create two copies of the same data. If, for whatever reason, you later need to update this information, you will have two places you need to remember to update. If you only update one, at some point in the future, you will be in a situation where you have two bits of information about the same thing which are different and won't know which is correct. Understanding why you want to do this will give list members the opportunity to point out alternative solutions which may meet your requirements, but avoid the possible problems with your current approach. It is a similar story with respect to the management of org agenda files. There are many different approaches to this and understanding your requirements rather than just helping you to fix the problem can help. >From reading the thread and seeing the problems you had with executing commands etc, I'm assuming you are relatively new to both Emacs and org-mode. That is great and welcome! One of the big challenges for those new to org mode is learning how to best use it for your needs. Unfortunately, because it is such a flexible system and because everyone has different needs and priorities, it is impossible for org to set defaults which will satisfy everyone. It tries hard to find a middle ground, but cannot be expected to always get it right. There is also a need for the user to be willing to adjust their perspective to work with org and not against it. This is largely true of Emacs generally. Those who are most successful with adopting Emacs and org mode tend to also be those who are willing to see new possibilities and perspectives. Jeremy has mentioned he only has a few agenda files. I'm the polar opposite - I have lots of agenda files and lots of org files which are not members of the agenda file list. It took me a while to find the best balance for my requirements and while how I manage things may not fit with your requirements, I'm hoping outlining them and how I got to my solution may give you some ideas. Initially, I put pretty much everything into the agenda file list. This worked fairly well until the size of these files began to get very large. The biggest problem I had was my agendas were just getting too large and complicated/distracting. I then moved to a workflow where the agenda files really only contained tasks and notes, references, pretty much everything else was put into other org files not part of the agenda file list. I didn't like that workflow. It complicated refiling and I lost the ability to keep all related things together in a meaningful way. I then came up with a workflow which worked a lot better where I had a function (very simple one) which would change the list of agenda files based originally on what project I was working on and then later a more general type of work I was doing (at the time, I had 4 different 'roles' - main job, consulting work, volunteer work and home). This worked well for reducing the number/size of data which needed to be scanned when I called up the agenda. However, I still found there was too much or too many items in the agenda. At this point, I started using tags to provide a way to generate smaller agendas based on some specific criteria, such as the project I was working on. This really began to help and I soon came up with some standard agenda searches and views which really worked for me. My basic workflow was functioning well. >From this point, it was about refinement. For example, realised there are some tasks, such as scheduled tasks, which you always want to show up in the normal agenda, regardless of which work 'mode' (work, consulting, volunteer, home) I was in. I now have a setup I'm very happy with. The final solution actually comprises components from all my workflow iterations, but typically in a much simpler and stripped down version. I still have the ability to modify the agenda file list via a function 'on the fly', but only use it sparingly (where I have a work situation where it needs to be kept completely separate from everything else). What I did discover during this process was that 90% or more of what I needed already existed, I just didn't recognise it or understand it enough to recognise it. Nearly all my customisation is now built using org facilities, which is great because it makes things very stable. I rarely get issues with org or emacs version upgrades. What I learned from this process can best be summarised as - 1. When asking for help/guidance, outline the high level goal, not just the details of a problem you are having in implementing your solution. 2. Initially, avoid customisation when possible. Work with the system in default configuration for a while, even if some of it seems frustrating. There are often subtle reasons things are configured in certain ways by default which only become evident after using them for a while. Lots of people have used and contributed to org over the years and how it works has been refined to benefit from that experience. 3. If you think you need to change/adjust the list of files in the agenda frequently, your probably wrong or are doing things in a sub-optimal way. Consider how you can achieve your goal without changing the agenda file list. 4. The first areas you will likely want to customise are capture templates and agenda views. If your not familiar with elisp, you are best off using the customise system to do this. HTH Tim -- Tim Cross