From mboxrd@z Thu Jan 1 00:00:00 1970 From: =?utf-8?b?QW5kcsOhcw==?= Major Subject: Re: Bug: :noexport: tag prevents table functioning as babel code block input [7.7 (release_7.7.167.gfceb)] Date: Wed, 24 Aug 2011 06:35:10 +0000 (UTC) Message-ID: References: <87pqjwfb0b.fsf@gmail.com> <87bovgf7tc.fsf@gmail.com> <87sjosxft3.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([140.186.70.92]:38267) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qw73d-0007IT-A2 for emacs-orgmode@gnu.org; Wed, 24 Aug 2011 02:35:26 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Qw73b-0005mE-Sb for emacs-orgmode@gnu.org; Wed, 24 Aug 2011 02:35:25 -0400 Received: from lo.gmane.org ([80.91.229.12]:60116) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Qw73b-0005m4-Js for emacs-orgmode@gnu.org; Wed, 24 Aug 2011 02:35:23 -0400 Received: from list by lo.gmane.org with local (Exim 4.69) (envelope-from ) id 1Qw73a-0002Hv-TB for emacs-orgmode@gnu.org; Wed, 24 Aug 2011 08:35:22 +0200 Received: from dslb-092-074-177-167.pools.arcor-ip.net ([92.74.177.167]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 24 Aug 2011 08:35:22 +0200 Received: from andras.g.major by dslb-092-074-177-167.pools.arcor-ip.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 24 Aug 2011 08:35:22 +0200 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-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org Hi Tom, > > To me, the documentation is the leading specification of a piece of > > software. Anything the software doesn't do that is in the docs is a > > bug, but likewise anything it does do which the docs don't cover is > > also a bug. > > Aloha Andras, > > As an avocational programmer who has had the pleasure of making small > changes to the Org-mode manual and on-line documentation, this last bit > seems to raise the bar impractically high. Part of Org-mode's appeal to > me is that people frequently find new, and at least to me unexpected, > ways to use it productively. I find it interesting to see how best to > change the documentation to incorporate the new "discovery." That said, > the idea that the docs cover *everything* that Org-mode is capable of > doing is wonderful and I'll be happy to chip in when I can to help you > achieve that goal. I fully agree with you, but it looks like I didn't express my point clearly enough. I'm talking about very particular behaviour when, for instance, a certain keyword is encountered. The example in this bug report is a good illustration: if the tag :noexport: is only supposed to work in headlines, then I consider it a bug if it works elsewhere, so the developers must actually make sure that this never happens. Otherwise, an unsuspecting new user (like myself) reads the documentation, and accidentally tries the tag on something other than what's in the documentation. "Hooray, it works, and what a great piece of software this is" -- but that doesn't last long since a newer version of org-mode behaves differently and his undocumented and unintended "feature" no longer works. As a software user (in this case), I want to have a clear idea of what works and what doesn't, and if I try something and it works, I suppose it to be an official way of doing it. Had I not filed this bug report, I might have carried on using :noexport: on tables until, one day, suddenly all my documents break because this "feature" silently goes away. By saying that a "feature" must work if and only if it is so documented I refer to individual features (such as keywords, tags, keystrokes, etc.), not use cases. AndrĂ¡s