From mboxrd@z Thu Jan 1 00:00:00 1970 From: Samuel Wales Subject: Re: [BUG] org-agenda-skip-*-if-* variables change log mode Date: Mon, 31 Dec 2018 13:48:45 -0700 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([208.118.235.92]:52627) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ge4UT-0000Yq-Up for emacs-orgmode@gnu.org; Mon, 31 Dec 2018 15:48:50 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ge4US-0005fC-WB for emacs-orgmode@gnu.org; Mon, 31 Dec 2018 15:48:49 -0500 Received: from mail-lj1-x236.google.com ([2a00:1450:4864:20::236]:43171) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ge4US-0005dd-Ol for emacs-orgmode@gnu.org; Mon, 31 Dec 2018 15:48:48 -0500 Received: by mail-lj1-x236.google.com with SMTP id q2-v6so24229416lji.10 for ; Mon, 31 Dec 2018 12:48:48 -0800 (PST) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode On 12/22/18, Samuel Wales wrote: > at least i /think/ this is a bug. [what i mean is, as opposed to there already being a fix, or it being an intentional feature. i am pretty sure it is a bug: you either have stuff you don't need in the agenda, or you have a broken log mode.] but i'm wondering if my emails are reaching the list. > > i like to set log mode to show everything. i also go to > previous dates to find out what i did. > > however, the skip variables can change log mode. > > =3D=3D=3D > > consider org-agenda-skip-scheduled-if-done. showing is > useful for "what was doneified at an unspecified date but > was first scheduled today or on that day". > > it is not intended for "what you did today or on that day". > > in my case, the latter is useful, but the former is not. > > =3D=3D=3D > > if you have it set to the default of nil, and have log mode > on, it will redundantly show a closed non-timed scheduled in > both the timed section as a closed log mode item, and in the > non-timed section. > > thus it is tempting to set it to t to remove the redundancy. > > =3D=3D=3D > > but if you do that, YOU ARE ALSO REMOVING ITEMS FROM LOG > MODE. (note: untested in -Q.) > > assuming log mode is set to show closed tasks: > > - if it was UNSCHEDULED and done, it will show in log mode. > - if it was SCHEDULED and done, it will not show in log mode. > > this absence might get lost. you might notice closed tasks, > and not notice that you turned off scheduled tasks. > > =3D=3D=3D > > i doubt that many want to skip scheduled done tasks in log > mode, especially when unscheduled done tasks show. > > imagine a user with a "memacs type mindset". he or she > would probably be surprised that this variable omits items > from log mode. > > it seems impossible to skip without also affecting log mode. > > my suggested fix is a new or changed non-nil value to skip without > changing log mode. > > -- > The Kafka Pandemic: > > The disease DOES progress. MANY people have died from it. And ANYBODY > can get it at any time. > > "You=E2=80=99ve really gotta quit this and get moving, because this is mu= rder > by neglect." --- > . > --=20 The Kafka Pandemic: The disease DOES progress. MANY people have died from it. And ANYBODY can get it at any time. "You=E2=80=99ve really gotta quit this and get moving, because this is murd= er by neglect." --- .