From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carlos Pita Subject: Re: Feature Request: allow export yes/no for blocks that are valid babel inputs Date: Sat, 23 Mar 2019 18:35:26 -0300 Message-ID: References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: Received: from eggs.gnu.org ([209.51.188.92]:43958) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1h7oIl-0005Vu-Hz for emacs-orgmode@gnu.org; Sat, 23 Mar 2019 17:35:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1h7oIk-00028G-Mm for emacs-orgmode@gnu.org; Sat, 23 Mar 2019 17:35:39 -0400 Received: from mail-yw1-xc2f.google.com ([2607:f8b0:4864:20::c2f]:40425) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1h7oIk-00027g-Gv for emacs-orgmode@gnu.org; Sat, 23 Mar 2019 17:35:38 -0400 Received: by mail-yw1-xc2f.google.com with SMTP id p64so4411929ywg.7 for ; Sat, 23 Mar 2019 14:35:38 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs-orgmode Or maybe the other way around: #+noexport: mylist mytable ... Then there is the question of what to do with src blocks, which have their own, more complex, export control mechanism. What if both #+noexport and :exports were set with non consistent values? Should one forbid that possibility? Or simply make :exports win?