From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id QNsmLI/lTF9vDAAA0tVLHw (envelope-from ) for ; Mon, 31 Aug 2020 11:57:03 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0 with LMTPS id 2FmNJ4/lTF9sNQAA1q6Kng (envelope-from ) for ; Mon, 31 Aug 2020 11:57:03 +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 E7560940538 for ; Mon, 31 Aug 2020 11:57:02 +0000 (UTC) Received: from localhost ([::1]:36322 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kCiQm-0007Jw-Ms for larch@yhetil.org; Mon, 31 Aug 2020 07:57:00 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:59514) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kCiQT-0007Jp-4w for emacs-orgmode@gnu.org; Mon, 31 Aug 2020 07:56:41 -0400 Received: from mail-qk1-x731.google.com ([2607:f8b0:4864:20::731]:36445) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1kCiQR-0006sO-FL for emacs-orgmode@gnu.org; Mon, 31 Aug 2020 07:56:40 -0400 Received: by mail-qk1-x731.google.com with SMTP id f2so3177865qkh.3 for ; Mon, 31 Aug 2020 04:56:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:subject:in-reply-to:references:date:message-id:mime-version :content-transfer-encoding; bh=SHRR/NkfMdeHo9lAgQIaFt2gJguX+0rvmqIS31k/ZyA=; b=MSbddTjAudtDqrmUg4ubiFhG8FLLFKBwT714QJk2laTn3X+0Dsu1E2wPXbClZGk7Dw uiU1DVgJffKxJsZOnK/tQ2+DXki+u0UIPtdAVV4ZX0h4uQh8hw0RZGC6iw6X+mve3CbU yqSsWLUe/w9ls8DXhLgJ+PrmAKpIdQGAJOeomnSP+fT+8M/rgzK6EEBIC0eJJxDmybZA reXGZdpvS/KjodKTZyMekimXIZXrINS71PnFzR6E8NOxWzsonT3tJkLsz2N2Km01HVW6 ZVZ7PsuQ7cZ3I0oh5izl9en5+e5cFdEtNfYs9Hx1mgx/ogXHgZd5BDWFXxTFt8YvF6ZY BG4A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:in-reply-to:references:date :message-id:mime-version:content-transfer-encoding; bh=SHRR/NkfMdeHo9lAgQIaFt2gJguX+0rvmqIS31k/ZyA=; b=fk1GCd3xgUuSpZvdxVXYIu9ftVYuUzfZKHy2noDEXetsR5Lnc6J3rkJq3cCebLHnaB hBPOGuS0yXDk7RxXzjCp1xCJ6fbQbnGxQ+VeSzSBjcUtTdgj5vh7fXu4ECb1fykuYbDM mcECT96W6AdozeLUbCgO5oWvak5tHtJGR+Znhy363sg5iqL/WFU493WBT78szEpeA5Oj M8B1noFcMesWOMhhERaHkzE9UAunxZubiXrEnFi19RH+fxbd2nFejxbQoohUwkQMzeyR ZMZBlA2Fnb2JrAOaSDT2AmP210fd2SXAbxlUGq88hOSzef2z9IhZ90aUPw3z93Kkl31X sugQ== X-Gm-Message-State: AOAM532gTbbcd9zxvmKjR78SSoai2Dxu/Jr3z8jJK7fceKFlJfvz60Bc VGf90JRnLh1JU6/BQIGZe1QWiyxcBFkuOQ== X-Google-Smtp-Source: ABdhPJx7/KrvhljevAcEfRwSVAuJE/GTDXGFnI5F+xh6OLR+GtAKoj0up/JiEB17jectG78/NsOx2w== X-Received: by 2002:ae9:f310:: with SMTP id p16mr879906qkg.81.1598874998023; Mon, 31 Aug 2020 04:56:38 -0700 (PDT) Received: from localhost ([208.167.241.222]) by smtp.gmail.com with ESMTPSA id g184sm9176526qkd.51.2020.08.31.04.56.35 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 31 Aug 2020 04:56:36 -0700 (PDT) From: Ihor Radchenko To: Julius =?utf-8?Q?M=C3=BCller?= , emacs-orgmode@gnu.org Subject: Re: [feature request] A new cookie type [!] showing the last note taken In-Reply-To: References: <87zh6eymxs.fsf@localhost> <87h7skldpt.fsf@nicolasgoaziou.fr> <875z90xvqk.fsf@localhost> <871rjo8kgr.fsf@nicolasgoaziou.fr> <873644xr6y.fsf@localhost> <87sgc470lk.fsf@nicolasgoaziou.fr> <87y2lvwny0.fsf@localhost> Date: Mon, 31 Aug 2020 19:55:38 +0800 Message-ID: <87sgc3do79.fsf@localhost> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=2607:f8b0:4864:20::731; envelope-from=yantar92@gmail.com; helo=mail-qk1-x731.google.com X-detected-operating-system: by eggs.gnu.org: No matching host in p0f cache. That's all we know. X-Spam_score_int: -17 X-Spam_score: -1.8 X-Spam_bar: - X-Spam_report: (-1.8 / 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_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, 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.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=pass header.d=gmail.com header.s=20161025 header.b=MSbddTjA; 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-Spam-Score: -1.21 X-TUID: u70VU4ahxrwT > Make it easier perhaps -- once the tool has been changed to the new > syntax. But you might break current usage. And not everyone using such > tools has coding skills to make those tools work again. > Prof. Kitchin kindly gifted me with some code for a flash card learning > system. That code uses org-add-log-setup directly. Notes added like that > might not follow your newly added syntax. Note that the syntax I proposed is not new. It is already used by org-add-note (which is, by the way, calling org-add-log-setup -> org-add-log-note -> org-store-log-note. org-log-note-headings is only directly used in the last function). I do not propose to change the old behaviour. I just propose to take the de-facto used syntax and say "that's what org-mode calls a note". None of the existing org-mode functions need to be changed to conform with this formalised note syntax. However, we can implement a new set of functionality (like what I asked in this feature request) that will work assuming notes are created with the newly introduced syntax. Any old notes created using alternative syntax (which can be anything, since note syntax was never formalised) will simply not be recognised (as they are not recognised now because of lack of "note" definition). If external tools defined an alternative syntax for a note, notes created following that syntax will not be broken. Those external tools can keep using their own syntax. The only difference is that **new** org-mode functions supporting the new syntax will not be able to work with third-party notes. However, these new org-mode functions will not be possible if we keep the note syntax undefined. Best, Ihor Julius M=C3=BCller writes: > Am 31.08.20 um 04:26 schrieb Ihor Radchenko: >> I would not call defining syntax for notes "a syntax change". Rather >> addition to syntax. Since there was no formal definition of notes in the >> past, introducing formal syntax for notes should not break any existing >> tool. If anything, it should make it easier for those tools to deal with >> notes. > > Make it easier perhaps -- once the tool has been changed to the new > syntax. But you might break current usage. And not everyone using such > tools has coding skills to make those tools work again. > > Prof. Kitchin kindly gifted me with some code for a flash card learning > system. That code uses org-add-log-setup directly. Notes added like that > might not follow your newly added syntax. > > Julius