From: tsd@tsdye.com (Thomas S. Dye)
To: "András Major" <andras.g.major@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: :noexport: tag prevents table functioning as babel code block input [7.7 (release_7.7.167.gfceb)]
Date: Tue, 23 Aug 2011 13:38:12 -1000 [thread overview]
Message-ID: <m1vctnr95n.fsf@tsdye.com> (raw)
In-Reply-To: <loom.20110824T003644-61@post.gmane.org> ("András Major"'s message of "Tue, 23 Aug 2011 22:44:01 +0000 (UTC)")
András Major <andras.g.major@gmail.com> writes:
> Hi Bastien,
>
>> > I think that anything that works despite being designed and documented
>> > otherwise is confusing to the user and should be considered a bug.
>> > I'm happy that it no longer works and hope that it stays that way.
>>
>> I think tags are clearly documented as being properties of the
>> headlines -- if there is places in the manual that we can improve
>> in this respect, please suggest a patch.
>
> I'm not talking about the manual. In my opinion, if there is a
> function that works only on headlines according to the manual, then it
> *must not* work in any other place. Otherwise some users might try
> the function they once heard of in a sense not specified in the
> documentation (here: in a table) and see that it works, and be
> surprised when it no longer does (in a future version of org-mode, or
> on a different computer). Therefore such "ghost features" must
> actively be eliminated.
>
> 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.
All the best,
Tom
>
>> I don't think it's reasonable to document the fact that tags are
>> not meant to be used in tables, blocks, lists, timestamps, etc.
>
> I fully agree.
>
> András
>
>
>
>
--
Thomas S. Dye
http://www.tsdye.com
next prev parent reply other threads:[~2011-08-23 23:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-23 11:04 Bug: :noexport: tag prevents table functioning as babel code block input [7.7 (release_7.7.167.gfceb)] András Major
2011-08-23 11:26 ` Sebastien Vauban
2011-08-23 11:38 ` András Major
2011-08-23 14:23 ` Bastien
2011-08-23 22:35 ` András Major
2011-08-23 14:09 ` Bastien
2011-08-23 14:38 ` Eric Schulte
2011-08-23 15:12 ` András Major
2011-08-23 15:47 ` Eric Schulte
2011-08-23 16:01 ` András Major
2011-08-23 16:18 ` Bastien
2011-08-23 22:44 ` András Major
2011-08-23 23:38 ` Thomas S. Dye [this message]
2011-08-24 6:35 ` András Major
2011-08-24 7:22 ` Thomas S. Dye
2011-08-24 8:28 ` Bastien
2011-08-24 16:41 ` Thomas S. Dye
2011-08-24 8:26 ` Bastien
2011-08-24 8:34 ` Bastien
2011-08-23 17:19 ` Eric Schulte
2011-08-23 22:51 ` András Major
2011-08-23 23:03 ` Nick Dokos
2011-08-23 23:44 ` Eric Schulte
2011-08-24 0:14 ` Thomas S. Dye
2011-08-24 7:41 ` András Major
2011-08-23 16:14 ` Bastien
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1vctnr95n.fsf@tsdye.com \
--to=tsd@tsdye.com \
--cc=andras.g.major@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).