From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.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 cB7YAq/lcGIGTwEAbAwnHQ (envelope-from ) for ; Tue, 03 May 2022 10:19:59 +0200 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id UDTxAq/lcGK7pgAA9RJhRA (envelope-from ) for ; Tue, 03 May 2022 10:19:59 +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 6E3173AA16 for ; Tue, 3 May 2022 10:19:58 +0200 (CEST) Received: from localhost ([::1]:40232 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nlnlF-0007XD-4U for larch@yhetil.org; Tue, 03 May 2022 04:19:57 -0400 Received: from eggs.gnu.org ([2001:470:142:3::10]:59174) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nlncY-0000q5-0s for emacs-orgmode@gnu.org; Tue, 03 May 2022 04:10:58 -0400 Received: from mail-vs1-f49.google.com ([209.85.217.49]:33318) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nlncW-00006L-8p for emacs-orgmode@gnu.org; Tue, 03 May 2022 04:10:57 -0400 Received: by mail-vs1-f49.google.com with SMTP id v139so15769379vsv.0 for ; Tue, 03 May 2022 01:10:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xsTN2+xPYb6RM4uz/QFY+E41Vfu8aQ3IurFlmR/7iw4=; b=5GioI/1yILGBcO1tSBYq1rQ5BmJe6H0O0N2ItWeSs/NewC3Oe+52FXeoMaTXhxi02/ EcZ/QS3wV53P5x64mU1qnMYUff1LCoiCci9ZADOkyOL9Jcd0KHuuLzcPXPok/Fhkrgx8 D9DUEl8Zb+7vHYb5fT3hwh55EOuEdLcNCOqNkMX/VfSoc65YW4/yV7ortuwnzkx5NHBq sdeRXbAlWIzBJJeSmp3r5icJB5eSs9e83mh66auoKe9TSYsCL8vuJW3qCI8vienl7oqC UHvpSbfTC1i8FKeUaxbg4/+ge10q51jAmuKlR7lMplGHeclljTQfgShrrSdqNylkOFD6 /xJQ== X-Gm-Message-State: AOAM531uR6HKysuaI06yCYuaJIOcbdHw2oftb23Sp0a0BJ/pqCPtDHV1 BFfEXz5H6K3eqdlNz4aIWi+EI8tTcRpV0VlNJPPbbWcPziU= X-Google-Smtp-Source: ABdhPJwo/RAtjstr6KkUJVLkoa5qagh2K99TOfNvtV53YFQ5BVPZ9MX2l6lwcpRevtX8jUBfe1ev9+au5WII4948hY4= X-Received: by 2002:a67:1a02:0:b0:320:a51f:8067 with SMTP id a2-20020a671a02000000b00320a51f8067mr4699514vsa.38.1651565454904; Tue, 03 May 2022 01:10:54 -0700 (PDT) MIME-Version: 1.0 References: <87ee1bgu06.fsf@localhost> In-Reply-To: <87ee1bgu06.fsf@localhost> From: Phil Hudson Date: Tue, 3 May 2022 09:10:43 +0100 Message-ID: Subject: Re: [PATCH] Re: [BUG] org-element-map doco should refer to org-element-parse-buffer [9.5.2 (9.5.2-gfbff08 @ /home/phil/.emacs.d/elpa/org-9.5.2/)] To: Ihor Radchenko Cc: emacs orgmode-mailinglist Content-Type: text/plain; charset="UTF-8" Received-SPF: pass client-ip=209.85.217.49; envelope-from=philhudsonster@gmail.com; helo=mail-vs1-f49.google.com X-Spam_score_int: -13 X-Spam_score: -1.4 X-Spam_bar: - X-Spam_report: (-1.4 / 5.0 requ) BAYES_00=-1.9, FREEMAIL_FORGED_FROMDOMAIN=0.249, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no 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" X-Migadu-Flow: FLOW_IN X-Migadu-To: larch@yhetil.org X-Migadu-Country: US ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1651565998; 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:in-reply-to:in-reply-to: references:references:list-id:list-help:list-unsubscribe: list-subscribe:list-post; bh=xsTN2+xPYb6RM4uz/QFY+E41Vfu8aQ3IurFlmR/7iw4=; b=IjsC3eaFHG3ZEFabUgJafIqOS/eOLBb+r93EctzUOIt1qAXUf3Gr6WDEZARheLKLVxoHm0 7BtJQ2HWr/RcUXRN44yChvilhncDPdFQzkj+kjV3UlK9sA0kZzWCAsRNtgxH+usx3TDKVY piXD2P3nEJQjBAUTTd3Wkq4wM/sWJteqr8rkA+cINalb8MS+XgvnV7xdA7kveWc3RZ5qfi us6R6Vn+Pwvvf694+RIbw1Wqa3sxBFAzG7gxAoO5o1vL5EN7I75MsrcqZoMB0VRFmSygR2 g5/WDsJ97QB+m0ZZUPs3gb+LmesV2WcsFwVFX9jTLwiWHyrQ8aq9PUqpNusaPw== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1651565998; a=rsa-sha256; cv=none; b=GQBgPngk9FASryYXSVzbuufmXbnOY8IUrsZmAVkSNeyF1O/gQFBn6ysYpsEiwqjUZPjTq3 2NHcafNfEvZpWkh0pWx9KS2+42ruyezw2e/T2EVO30WFAlO9ueQjhbp3CjEjsurcYWIuy7 iF4/FsD/Htz5VJds9vy3qJjddyjdUM5q6JqPEp6zVb+H1gStaTUOemPfHcWm7Efg0wtvnG U9QfYJZT5XBMILrEAFcy1f9MSAlDbHJzlVGWLIIizBTv8wIpIUJns47eBDmZ1wzzWcAUmi mlU0lvUog0mGf5SkC/sOOv633Z/zFLE8YLocRvc5IBYz6iAN3ehAF1v7K4oQkA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=none; 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: -2.78 Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; 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: 6E3173AA16 X-Spam-Score: -2.78 X-Migadu-Scanner: scn1.migadu.com X-TUID: 8IVCwwwkfiKe Thanks Ihor, that's great! One tiny nit-pick: I think "e.g." is deprecated in favor of the explicit literal "for example". My source for this is (info "(elisp) Documentation Tips"). Also, just spotted what I think is a pre-existing typo, "objects types", which I think should probably be just "object types". Might as well fix that while we're at it. Best, Phil On Tue, 3 May 2022 at 04:43, Ihor Radchenko wrote: > > Phil Hudson writes: > > > The documentation for function `org-element-parse-buffer' helpfully > > directs the user to that of function `org-element-map', but the > > documentation for the latter makes no mention of > > `org-element-parse-buffer'. It contains lengthy and helpful explanations > > of what to do with its `data' parameter, but no hint as to how to obtain > > that data. > > Sounds reasonable. > Will something like the attached do? > > Best, > Ihor >