From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp12.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms5.migadu.com with LMTPS id CCqxMKRAV2PmywAAbAwnHQ (envelope-from ) for ; Tue, 25 Oct 2022 03:49:24 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp12.migadu.com with LMTPS id +Nv1MKRAV2OtBAEAauVa8A (envelope-from ) for ; Tue, 25 Oct 2022 03:49:24 +0200 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 6CED63DE5A for ; Tue, 25 Oct 2022 03:49:24 +0200 (CEST) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1on90X-0006ZW-5A; Mon, 24 Oct 2022 21:45:33 -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 1on90Q-0006XE-9Q for emacs-orgmode@gnu.org; Mon, 24 Oct 2022 21:45:26 -0400 Received: from mail-pj1-x102d.google.com ([2607:f8b0:4864:20::102d]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1on8zt-0006zo-2D for emacs-orgmode@gnu.org; Mon, 24 Oct 2022 21:45:23 -0400 Received: by mail-pj1-x102d.google.com with SMTP id h14so9490064pjv.4 for ; Mon, 24 Oct 2022 18:44:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:message-id:in-reply-to:date:subject:to:from:user-agent :references:from:to:cc:subject:date:message-id:reply-to; bh=8q/1k2okgGx+bM+Qrh8w5jlWW2LFALqEnO1c4+yAorc=; b=qYlmV/49xZGFjmWOfJDhVN0GGmE5xvB8QbuRK6hdjAqNiiYrvTVpJYSNXH6Agt/TQL 24Xp1LQ2IXk2A60z9KLy5TDWoDq4CXb0v2qSUqgOaeasnKmSH16Op0kW25EoQeDDqWS1 m/2+QuqJ6NXIXiUxNi62E+84M42XPkifFaiIOI9BL6pAQBr06wKy7Gb5Xhi75fWT2WF4 Nvia+LPH66FrxRpm6QYzg4j8CsCMbC4P+vcIiOwMFj1vbluQqUhvYfWRqeES8SG+wr5b P/zt/0nRuRMtHwt3+Flzg8ngpwDJLMYwZvTFfdgyuh/JVaN4mqUa5qIbIg+RE2m8Vvjx Invg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=mime-version:message-id:in-reply-to:date:subject:to:from:user-agent :references:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=8q/1k2okgGx+bM+Qrh8w5jlWW2LFALqEnO1c4+yAorc=; b=zg4ib2LBDoFOot4Jy4HDfMGIB15FyilM8hU7fJHzZ/TLickkeU1KAMXP/gEzgHB+Wh qkxNYDgiRphaAZjO7oL13C53vyzFy+oP6qxcZrsvNb+wEGBg1EnBKFoehf9X+udecmZy +gt4OniKQOAPMdkZHVQSmw9ud9Eg7lT439BKdQEegZ2k1lqZmCREb6gldZtphmO2R9AX 338HzpC00BK9dE9Oq2dykU5KhrwLu0dw33jmKSJA6eojwuJ4VFXVDsMM1g6DVqXcah87 LypWGIArVJ/ArNEjRGkZ5W66p1QwwwLIWuTAS5EMr3+/7kXU1AvZxTNkaYapRlCh/rMh IweQ== X-Gm-Message-State: ACrzQf3kMl3mIctSLV+Z7IqEOMbND1i3+g8kJWdDDgbn8PYTw6zNvE7Q sJWCBKen/m7jZYHVxYe1VBYt3FS0dlc= X-Google-Smtp-Source: AMsMyM5dvbCK8zRPgKA6pEwwGMb1v6XBntSoO90zT06wfhdC/x69RltrkbMQjXA27Q2uANwluYp5NQ== X-Received: by 2002:a17:90b:1982:b0:212:fe7f:4a49 with SMTP id mv2-20020a17090b198200b00212fe7f4a49mr12017491pjb.156.1666662287283; Mon, 24 Oct 2022 18:44:47 -0700 (PDT) Received: from dingbat (ppp121-45-155-118.bri-pow-que-bras32.tpg.internode.on.net. [121.45.155.118]) by smtp.gmail.com with ESMTPSA id z1-20020a170903018100b0017dd8c8009esm333099plg.4.2022.10.24.18.44.45 for (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 24 Oct 2022 18:44:46 -0700 (PDT) References: <87zgdms2lq.fsf@mat.ucm.es> <87k04ppp1t.fsf@localhost> User-agent: mu4e 1.9.1; emacs 29.0.50 From: Tim Cross To: emacs-orgmode@gnu.org Subject: Re: [BUG] Undocumented convention for org-time-stamp-custom-formats to be "<...>" (was: time-stamp in DONE tag is not really displayed) Date: Tue, 25 Oct 2022 12:29:52 +1100 In-reply-to: <87k04ppp1t.fsf@localhost> Message-ID: <861qqwk778.fsf@gmail.com> MIME-Version: 1.0 Content-Type: text/plain Received-SPF: pass client-ip=2607:f8b0:4864:20::102d; envelope-from=theophilusx@gmail.com; helo=mail-pj1-x102d.google.com X-Spam_score_int: -20 X-Spam_score: -2.1 X-Spam_bar: -- X-Spam_report: (-2.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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 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: , Sender: "Emacs-orgmode" Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1666662564; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post:dkim-signature; bh=8q/1k2okgGx+bM+Qrh8w5jlWW2LFALqEnO1c4+yAorc=; b=E4H8Lsy9Vqm7x2DVibwzqXghqKIw+HqLKFKP13LsV7y7xgWAzqIhWUARgPr23Ox+5G8Ttn WAtadAFHAaLZduJF9iI8ysEcloQF0eU2Gmdl74bB4jCg9HufoqGvQf7T6eHO+2BwVaJIBn lAL49jOd2+gOskQK8qLssmgh14izOEsmMLC+awiWSdtYtOgsMZWADJvsGQueLtolo1tSKH JVi7FGcedBzpLooGEvAvkzHNg+ExzXb1eiA7Otl3LvX+oRbpLaTjnFr4mvGJbbhCt29V3F w5AYxfvsFvUmaY0v0a0ZTtWdAlpW2znA8tqDam4aDfmhYCLoL+IQNABc83JPBQ== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1666662564; a=rsa-sha256; cv=none; b=Y2um87oNHEaGByq4tInC1CVs88wu+iNEAfoipxmHaOsSTDS+lmD06+hnvrsCZPFiO1Hd0u YeQcT0qJrUQKfh2+JC67Sjm12KgQ/1f+TVgZ+wplU52FCBqufe1f3PlrBYPRMlHk/ovHqF dsm0AtKRCl88gP2xy3NO2fElZDztPpX8tGsAP0qribe/B6XPp4I+yYfdFmdWDqitj6/MR2 SSjLsJfKRVHoFfBjEST9+YGmA5kZcSDN6jRIU3axn1T982g4HC/SJ3pYgAxXIoL6t7+OdB BYugUDWuR4U5gmRJT+FSSGwckJYZXwV9h84Mt5jMO/OgyFHivO99GiyJoGLqyA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b="qYlmV/49"; dmarc=pass (policy=none) header.from=gmail.com; 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" X-Migadu-Spam-Score: -3.91 Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=gmail.com header.s=20210112 header.b="qYlmV/49"; dmarc=pass (policy=none) header.from=gmail.com; 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" X-Migadu-Queue-Id: 6CED63DE5A X-Spam-Score: -3.91 X-Migadu-Scanner: scn1.migadu.com X-TUID: 2kaWn9EMvyky Ihor Radchenko writes: > Uwe Brauer writes: > >> My time-stamps are of the form <2022-10-23 Sun> >> I have an entry like this >> >> - State "DONE" from "WAIT" [2022-10-23 21:06] \\ >> >> >> >> However it is displayed when I use org-toggle-time-stamp-overlays as >> [23.10.%] >> >> Neither the year not the time is displayed, why! >> >> I have set >> org-time-stamp-custom-formats >> to >> (" %d.%m.%Y " . " %d.%m.%Y") >> >> I am puzzled, any ideas? > > Confirmed. > > This is because Org expects the first and the last characters in > org-time-stamp-custom-formats to be opening/closing brackets. > (undocumented) > > Why? > Because org-time-stamp-formats does so. > > Why does org-time-stamp-formats does so? > No idea. > This code dates back to initial Org commits. > > I think it would make sense to change it. > However, if we change special treatment of the first/last characters in > org-time-stamp-custom-formats, it will also make sense to change > org-time-stamp-formats constant. > > For backwards compatibility, we will need to keep special treatment to > strip brackets around the formats, if present. > > I propose to do the following: > 1. org-time-stamp-formats and org-time-stamp-custom-formats will be > treated as is, unless they contain "<" and ">" and the first and the > last char. > 2. If the formats do contain <...>, strip the "<" and ">". > 3. Document (2) in the docstrings. > > Any objections? Little unsure/confused regarding what is being proposed here. - If we are removing <...>, does that mean we just retain [..] for inactive timestamps and all other timestamps are 'active' by default? - How will this change impact code which distinguishes active/inactive timestamps based on presence/absence of <..> and [..]? - What impact will this have on existing org files? - Will this cause issues in parsing when you may have dates/times which are not supposed to be timestamps, but will look the same as timestamps? How will you distinguish them? Personally, I like the clear distinction between what is a timestamp and what isn't and what is an active timestamp and what is an inactive timestamp.