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 Ivv7HINZbl9BJwAA0tVLHw (envelope-from ) for ; Fri, 25 Sep 2020 20:56:35 +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 WPlFGINZbl91CwAAbx9fmQ (envelope-from ) for ; Fri, 25 Sep 2020 20:56:35 +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 B238E940393 for ; Fri, 25 Sep 2020 20:56:34 +0000 (UTC) Received: from localhost ([::1]:52858 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kLuld-0001IA-FQ for larch@yhetil.org; Fri, 25 Sep 2020 16:56:33 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:51796) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kLulG-0001I2-Dj for emacs-orgmode@gnu.org; Fri, 25 Sep 2020 16:56:10 -0400 Received: from static.214.254.202.116.clients.your-server.de ([116.202.254.214]:51918 helo=ciao.gmane.io) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kLulE-0007Z5-TP for emacs-orgmode@gnu.org; Fri, 25 Sep 2020 16:56:10 -0400 Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1kLulA-0006N5-TX for emacs-orgmode@gnu.org; Fri, 25 Sep 2020 22:56:04 +0200 X-Injected-Via-Gmane: http://gmane.org/ To: emacs-orgmode@gnu.org From: Nick Dokos Subject: Re: Bug: Infinite loop caused by org-agenda-property-list [9.4 (9.4-elpa @ /home/dsmasterson/.emacs.d/elpa/org-9.4/)] Date: Fri, 25 Sep 2020 16:55:57 -0400 Message-ID: <87h7rly3s2.fsf@alphaville.usersys.redhat.com> References: <87blhwrrgf.fsf@alphaville.usersys.redhat.com> Mime-Version: 1.0 Content-Type: text/plain User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cancel-Lock: sha1:1COu56q7mfpPXqJIdN/GnqAHzBs= Received-SPF: pass client-ip=116.202.254.214; envelope-from=geo-emacs-orgmode@m.gmane-mx.org; helo=ciao.gmane.io X-detected-operating-system: by eggs.gnu.org: First seen = 2020/09/25 16:56:05 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: 13 X-Spam_score: 1.3 X-Spam_bar: + X-Spam_report: (1.3 / 5.0 requ) BAYES_00=-1.9, DKIM_ADSP_CUSTOM_MED=0.001, FORGED_GMAIL_RCVD=1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, FUZZY_DR_OZ=1, HEADER_FROM_DIFFERENT_DOMAINS=0.248, NML_ADSP_CUSTOM_MED=0.9, 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-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=fail reason="SPF not aligned (relaxed), No valid DKIM" header.from=gmail.com (policy=none); 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-Spam-Score: -0.41 X-TUID: h0cnIst0+rGU David Masterson writes: > Nick Dokos writes: > >> From what I can gather, this does not have much to do with Org mode >> proper, which has no org-agenda-property-list at all. I presume that >> you have >> >> https://github.com/Malabarba/org-agenda-property/blob/master/org-agenda-property.el >> >> installed, which does provide such a variable, but all that one can >> say atm is that that library has a bug *or* is incompatible with >> (current?) Org mode. In either case, I think you should report it as >> an issue to the above site. Once they have figured out what is wrong, >> then maybe an RFE against Org mode *might* be indicated. > > Ah! That makes sense. I'll look into it. > You might be able to work around the problem by having org-agenda-property put the property on the same line: (setq org-agenda-property-position 'same-line) and adjusting the position on the line with (setq org-agenda-property-column 100) if necessary. If the infinite loop goes away in that case, then you have some confirmation of your theory about two-line agenda entries. -- Nick "There are only two hard problems in computer science: cache invalidation, naming things, and off-by-one errors." -Martin Fowler