From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp11.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms9.migadu.com with LMTPS id kO2UKSEV+2TdNAAA9RJhRA:P1 (envelope-from ) for ; Fri, 08 Sep 2023 14:35:45 +0200 Received: from aspmx1.migadu.com ([2001:41d0:306:2d92::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp11.migadu.com with LMTPS id kO2UKSEV+2TdNAAA9RJhRA (envelope-from ) for ; Fri, 08 Sep 2023 14:35:45 +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 3EC6731F2F for ; Fri, 8 Sep 2023 14:35:45 +0200 (CEST) Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=itccanarias.org header.s=default header.b=IZtoZt19; 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"; dmarc=pass (policy=quarantine) header.from=itccanarias.org ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1694176545; 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:dkim-signature; bh=QBOU5u2YXopXoHTwsgkyN7Oia7Jkm84gt3MulJB3BVM=; b=jJNCKjD4dozZd2VoNGkh1dI6o1vRY/3W7TvBTbs6Err8PtOXfiuEkutVcbFeLz9qh3HAx7 6R6HZwoD+jgHoK4mXNJuiCfNdC8dDUX+wcu3unsOuGHspi9iTzFjstRFfG/OsT4YYKaXof Nq0cWxA4SVzxv1eUJmbfNQsf6dIDfioZgc4jsUQr+J1BmYXtAcALSQROtVxtOtb0RRZ8jI sjh1F2HpZZKUw7P/c7tYNJ7OqFyEt2f20pyRxIRC1wQYBjMyKlcNZK/BcKzxo2XMBS/d6v qPy4Wl1TbBvFh7zkss2oaPlhz59gUWu3+TVcqx0G0+Ks9LGurFAb6yg5N++M5g== ARC-Seal: i=1; s=key1; d=yhetil.org; t=1694176545; a=rsa-sha256; cv=none; b=OhYKzDRHWGDUG1wV6PJcks9JEypUZZ1trNm9d07eoiewHJsF1qsZSW74tlA37eb/yC+EAe ao7HH0q7rmLLHLnPxbhC1n8/HnsVHn+IszCzxe+8u5/L9mMm4R0m8QRvEcqysnm/wdbHE8 Aj0szm68YdbZhURb3/kgz7LhXG7P6QjQqaRpMKnXrKYNYzDZhV70+eo0iSH/jCoqSp5LHe Dc/qD47HT7zDWGuFIk5TArnKsz/nSPaL5pcnKP4Bvc3csMPPg2qysS4mMqqGQlIf+p0r5+ M4OkVK6YZHvhL8QHZFTl52anLidhBaGO3R3r60CjcS1LKjs0Z87pmP6SIkZHHw== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=itccanarias.org header.s=default header.b=IZtoZt19; 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"; dmarc=pass (policy=quarantine) header.from=itccanarias.org Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1qeagu-0002ix-JD; Fri, 08 Sep 2023 08:34:28 -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 1qeagr-0002ih-Na for emacs-orgmode@gnu.org; Fri, 08 Sep 2023 08:34:25 -0400 Received: from relay.itccanarias.org ([62.174.94.155]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1qeago-0001W6-9X for emacs-orgmode@gnu.org; Fri, 08 Sep 2023 08:34:25 -0400 Received: from localhost (localhost [127.0.0.1]) by relay.itccanarias.org (Postfix) with ESMTP id 6C13943B36; Fri, 8 Sep 2023 13:34:18 +0100 (WEST) Received: from relay.itccanarias.org ([127.0.0.1]) by localhost (gwmail-lp.corp.itccanarias.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Min7as884JIV; Fri, 8 Sep 2023 13:34:18 +0100 (WEST) Received: from Erasure.corp.itccanarias.org (erasure.corp.itccanarias.org [10.141.187.131]) (using TLSv1.2 with cipher ECDHE-ECDSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by relay.itccanarias.org (Postfix) with ESMTPS id 505FE43B16; Fri, 8 Sep 2023 13:34:18 +0100 (WEST) Content-Type: text/plain; charset="us-ascii" Content-Disposition: inline DKIM-Signature: v=1; a=rsa-sha256; d=itccanarias.org; s=default; c=relaxed/relaxed; t=1694176457; h=from:subject:to:date:message-id; bh=QBOU5u2YXopXoHTwsgkyN7Oia7Jkm84gt3MulJB3BVM=; b=IZtoZt19z/rK8n4eyA8hOEYJ5DJkcTGg6/E6mF1xmO1MoM7gm83F7/5C6jEskjqIbiTu+tFwbZ9 QCiAqecGbBfs/tQXperVwZEc/jWP6kZDR/m3qoeb6Hy4YvOQwj8d0s6aalMfjvIDpeqm8FmUYTqPL Pit5RfKZrbCHetRZkYiMGifg3G2CXhyzOL8lT8VBqc3TBmMM+7hlG+HLGFZDmFE3b89T5QzRUDXB2 g9bBuMbxjH8uC8LZBWu1N4a7kWWyjUUugxlT4XVls1Y51CpZ8yNCBRsjSHleVIta4fow/Kejrp/Cg qAmmiA3Rdc3mnhB3Waobq34XMK5CaZosWOdA== Received: from itccanarias.org (10.141.153.141) by Erasure.corp.itccanarias.org (10.141.187.131) with Microsoft SMTP Server (TLS) id 14.3.498.0; Fri, 8 Sep 2023 13:34:17 +0100 Date: Fri, 8 Sep 2023 13:34:15 +0100 From: Eduardo Suarez-Santana To: Ihor Radchenko CC: Subject: Re: Feature request: kill-buffer for org-capture-finalize Message-ID: References: <87sf7o987k.fsf@localhost> MIME-Version: 1.0 In-Reply-To: <87sf7o987k.fsf@localhost> Received-SPF: pass client-ip=62.174.94.155; envelope-from=eduardo@itccanarias.org; helo=relay.itccanarias.org 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, 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: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Country: US X-Migadu-Flow: FLOW_IN X-Migadu-Scanner: mx2.migadu.com X-Spam-Score: -5.56 X-Migadu-Queue-Id: 3EC6731F2F X-Migadu-Spam-Score: -5.56 X-TUID: HpwE1t/BLDaz On Fri, Sep 08, 2023 at 12:10:23PM +0000, Ihor Radchenko wrote: > Eduardo Suarez writes: > > > The function org-capture-finalize allows an argument to 'jump-to-capture'. I > > think it may be a good idea to add a new argument to 'kill-buffer' after the > > capture is finalized. This would be useful to avoid having to kill the capture > > buffer manually. I assume that if ':kill-buffer' is intended as the default > > behavior, then it would be better to set it in the capture template. > > May you explain a bit more about the problem you are trying to solve? > Isn't the temporary capture buffer killed after capture already? > Or do you refer to the org buffer where the capture is recorded? Sorry about that. I refer to the org buffer where the capture is recorded. I meant: "This would be useful to avoid having to kill the target buffer manually." I like to keep the target buffer open after the capture is finalized so I can review the changes later, but sometimes I'd rather prefer to kill it because I already assume that the changes are correct. This helps to keep the buffer list clean.