From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id KCiLAWCw8WUFxgAAqHPOHw:P1 (envelope-from ) for ; Wed, 13 Mar 2024 14:55:44 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:58f0::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0.migadu.com with LMTPS id KCiLAWCw8WUFxgAAqHPOHw (envelope-from ) for ; Wed, 13 Mar 2024 14:55:44 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=RfO83k7d; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1710338143; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=qeO0ufE0SSYh8i//DYbPC0RsivjckquUTkIpZpubq1Y=; b=hXTUMov2ChG8H9xu9udCA0SsnZkqedrs8ub1Ewc5ZXGl80vIv2Aqshj6/tg4HbCXTBPb+7 98Txv46YRo6gmsiLSpwDpNRAbzHsFOFsuDNPUg1ThulT8aDm1O+T5NqB/9CSbBKiDpS/0J eLbpWTQ10/NNaxDtn1D5ZVmQBzTFQ3K/846NZOz1CNFXlgkmpTrjdFojdu+tdkMMuMsj4A JyHDvP8MMpoq8wyOjs2OK6rG+oETQEdkCdmQcK55M3ivGBcQBKT660StlXbpRIL1UudsV4 wUM1hS71oRfKU0IlWcsD4ojwl9OpXuYY5M8WaJMWjnc8V27snozZrDOiZKL8pA== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1710338143; a=rsa-sha256; cv=none; b=pVvSZez5sGfDksE9gIU3EFKkMJIOvEWWSSkMYbKing29hIpWTCU6Q30+2nuTdVEQGjxngM qvXbIW3jZAjR6QbwomQATZ1wYxdpL+uChMl/4DkC5ikGx5qjZK6Pk4nRj006xCsMChPu/m gGMzNK0LgV1uIRHQGjHhvcE9pDaVfaCrZHvsW0wBIpXuLrKIyc5a48jzTykZtCd3M+zDLU 7YeQ9cC0fqoqWXNnDYdyglj3CqiBT7IZrt6ch8xAdjNyM/r5snNFldc+mvo25omsg+Rkcl Lg628juZxNXOKa4neWQK7kk4ez85HRx7G34XG3qNoDswASGLWWFehBpvkTNEZQ== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=RfO83k7d; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net 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 D635F69BCC for ; Wed, 13 Mar 2024 14:55:43 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rkP4U-0001R8-9M; Wed, 13 Mar 2024 09:55:06 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rkP4Q-0001QX-Cd for emacs-orgmode@gnu.org; Wed, 13 Mar 2024 09:55:02 -0400 Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rkP4I-0002yD-TY for emacs-orgmode@gnu.org; Wed, 13 Mar 2024 09:55:02 -0400 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 4A4B4240104 for ; Wed, 13 Mar 2024 14:54:52 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1710338092; bh=qeO0ufE0SSYh8i//DYbPC0RsivjckquUTkIpZpubq1Y=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding:From; b=RfO83k7dEsjl2raCkMfpa26FlZIbsc/xV4183mMAkGV6Hg+GEqVou3/RldA02k2G0 dtAgCUnQaGxcbg8hdxTou5MpObXa2eikbSKQELGHJ8Znji2zZpV3NRsC78VghGtRAD OBsZZzudAdHLr62Y6Ksl34mQ5iCpPZZHPmxbeHx4hEEOqNgQWYex3UJBxK9o4y1Nej /rrV54i1CGUfDCqBzBwoOFh7HZ1fnhDNKCpljjWe9Ljrxc+SyvWGs6Swb1AaLO03sN 6YMxH//t7lv058U1IY3CBsCNHsj5ew5OzpmYRkstHtnz3cB3igGsMuq8lfpNRfr8He 76vWv4K/DxtvA== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4TvsT72nyKz9rxN; Wed, 13 Mar 2024 14:54:51 +0100 (CET) From: Ihor Radchenko To: =?utf-8?Q?S=C3=A9bastien?= Gendre Cc: emacs-orgmode Subject: Re: Org-agenda: List project with deadlines In-Reply-To: <87v85sdqr4.fsf@k-7.ch> References: <87v85sdqr4.fsf@k-7.ch> Date: Wed, 13 Mar 2024 13:59:03 +0000 Message-ID: <871q8ew7vc.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=185.67.36.66; envelope-from=yantar92@posteo.net; helo=mout02.posteo.de X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 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-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Spam-Score: -9.49 X-Spam-Score: -9.49 X-Migadu-Queue-Id: D635F69BCC X-Migadu-Scanner: mx11.migadu.com X-TUID: 1M7N2vA/iCAS S=C3=A9bastien Gendre writes: > But how do I differentiate a project from a task for Org-mode=C2=A0? Tags > have inheritance. Do I use a property=C2=A0? It is completely up to you. It is, however, common to use either project tag to PROJ todo keyword to mark project. You can exclude specific tags from inheritance via `org-tags-exclude-from-inheritance'. > Is it a good idea to organize every thing by classes=C2=A0? Or is it bett= er > to have one Org file named "Assignments" to regroup every projects=C2=A0?= In > these files, I have other information recorded, like the taken notes, > the list of distributed documents and their notes and also the list of > class sessions to see them in my agenda. Depends. There is no silver bullet for task management. IMHO, the benefit of grouping by class could be when you sometimes need to suspect certain classes, excluding the related tasks from the agendas. Then, you can trivially comment or flag the whole class heading with a special tag (for example :HOLD:) and configure your agendas to not lists tasks with that tag (tasks inside commented headings are skipped by default, as defined in `org-agenda-skip-comment-trees'). However, if all you classes are mandatory, and your workflow does not involve focusing on certain classes and temporarily hiding others, global "Assignments" file may be more suitable. > ** List the projects > > To list only the projects, I wanted to use Org-agenda todo list view and > editing the column shown. But the manual say it may cause issues. Those issues are only relevant to more complex column views, when you utilize summary attribute (see 7.5.1.2 Column attributes). AFAIU, your needs are simpler. So, you don't need to worry here. > What can I do=C2=A0? Do I use it correctly or do I need to it in a comple= tely > different way=C2=A0? Is it better to use a column view for it=C2=A0? If y= es, is it > possible to build a column view from multiple files=C2=A0? Yes, you can build column view from multiple files in agenda. > ** List of tasks from a project > > What is the best way to do it=C2=A0? A custom Org-agenda view for each > project=C2=A0? A column view under the project top heading=C2=A0? You can use sparse tree from project heading. You can also narrow the agenda scope to heading at point ("<<" in agenda dispatcher) If you projects are taking a long time, you can create custom agenda views for those projects. > I have the felling that wanting to have everything well organized and > using Org-agenda push me to think of too much complex ways to do thing. > > Maybe I need to do like with a bullet journal, with an Org-mode file > instead of a page and don't try to use too much features. > > Do you have any suggestion=C2=A0? Do I forget something=C2=A0? For what I= have > suggested, am I completely wrong=C2=A0? I strongly discourage you from using many features all at once. Start simple and add things one by one, when you have free time and interest to improve workflow. Only add new things when you get used to the existing simpler workflow. --=20 Ihor Radchenko // yantar92, Org mode contributor, Learn more about Org mode at . Support Org development at , or support my work at