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
András Major andras.g.ma...@gmail.com writes:
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,
Eric Schulte schulte.eric at gmail.com writes:
Are you /sure/ that this doesn't work for you? On my system C-c C-e A
in the following attached org-mode file (posted earlier in this thread)
I've just pulled the code again, now it seems to work. I'm not sure
what went wrong last night
Hi András,
András Major andras.g.ma...@gmail.com writes:
I fully agree with you, but it looks like I didn't express my point
clearly enough.
Thanks for taking the time to make this clear.
if the tag :noexport: is only supposed
to work in headlines, then I consider it a bug if it works
Hi András,
András Major andras.g.ma...@gmail.com writes:
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,
Yes, a *major documentation bug*.
but likewise anything it does do which the docs don't
Hi Tom,
t...@tsdye.com (Thomas S. Dye) writes:
I think I understand. Would it suffice to add this disclaimer to the
documentation for starters?
Features used in ways not explicitly documented here cannot be
guaranteed future support.
This is stating the obvious, and this gives a feeling
Bastien b...@altern.org writes:
Hi Tom,
t...@tsdye.com (Thomas S. Dye) writes:
I think I understand. Would it suffice to add this disclaimer to the
documentation for starters?
Features used in ways not explicitly documented here cannot be
guaranteed future support.
This is stating the
Hi,
here is an example that delivers an error reference 'table1' not
found in this buffer when trying to export to HTML (others not tried
yet):
#+tblname: table1 :noexport:
| n | x | y1 | y2 |
|---+---+-+--|
| 0 | 1 | 2.0 | 3.0 |
| 1 | 2 | 2.1 | 2.0 |
| 2 | 3 | 2.0
Hi András al.,
András Major wrote:
here is an example that delivers an error reference 'table1' not
found in this buffer when trying to export to HTML (others not tried
yet):
#+tblname: table1 :noexport:
| n | x | y1 | y2 |
|---+---+-+--|
| 0 | 1 | 2.0 | 3.0 |
Hi Sebastian,
I will let answer the ones who decide on such things. Though, I am amazed you
put a tag on the table itself.
I'd have expected the noexport tag to be on a section containing the table.
I forgot to mention in the report that of course I tried that too: if
I place the table and
András Major andras.g.ma...@gmail.com writes:
Hi,
here is an example that delivers an error reference 'table1' not
found in this buffer when trying to export to HTML (others not tried
yet):
#+tblname: table1 :noexport:
| n | x | y1 | y2 |
|---+---+-+--|
| 0 | 1
Hi Eric,
This is the first time I've seen a tag applied to a table. I've updated
the results regular expression so that it will now admit examples like
yours above. Please let me know if this doesn't work with the latest
Org-mode.
That's good news! Well, the bad news is that it doesn't
András Major andras.g.ma...@gmail.com writes:
Hi Eric,
This is the first time I've seen a tag applied to a table. I've updated
the results regular expression so that it will now admit examples like
yours above. Please let me know if this doesn't work with the latest
Org-mode.
That's
Hi Eric,
That's good news! Well, the bad news is that it doesn't work. I've
just pulled the current version (release_7.7.174.g63fae) and now the
behaviour is different:
- :noexport: in the #+tblname: has no effect.
I'm not sure that it is legal to apply tags to tables, so I'm not
Hi András,
András Major andras.g.ma...@gmail.com writes:
here is an example that delivers an error reference 'table1' not
found in this buffer when trying to export to HTML (others not tried
yet):
#+tblname: table1 :noexport:
| n | x | y1 | y2 |
|---+---+-+--|
|
Hi András,
András Major andras.g.ma...@gmail.com writes:
I'd have expected the noexport tag to be on a section containing the table.
I forgot to mention in the report that of course I tried that too: if
I place the table and the code in two sections and tag the section
containing the table
Hi Eric,
Eric Schulte schulte.e...@gmail.com writes:
I'm not sure that it is legal to apply tags to tables, so I'm not sure
if this is a bug.
I confirm tags are for headlines only.
If we want to add more export options to tables, let's use the usual
#+[option] syntax -- like #+caption
Hi András,
András Major andras.g.ma...@gmail.com writes:
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
Your file uses #+data: where I use #+tblname: -- which one is the
official one? I have the impression that it's #+data:, but I haven't
come across that in the manual or elsewhere before. If #+tblname:
isn't supposed to be used as a target for a variable in the code
block, then we should
Hi Bastien,
I'm not sure I understand -- does it mean that C-cC-c on #+begin_src
fails in the example below?
No, it means that exporting to HTML fails with that error message. It
should actually evaluate the code and include the resulting PNG in the
output (and that's what it does when
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
Hi Eric,
Your file uses #+data: where I use #+tblname: -- which one is the
official one? I have the impression that it's #+data:, but I haven't
come across that in the manual or elsewhere before. If #+tblname:
isn't supposed to be used as a target for a variable in the code
block,
András Major andras.g.ma...@gmail.com wrote:
Hi Eric,
Your file uses #+data: where I use #+tblname: -- which one is the
official one? I have the impression that it's #+data:, but I haven't
come across that in the manual or elsewhere before. If #+tblname:
isn't supposed to be used
András Major andras.g.ma...@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
Nick Dokos nicholas.do...@hp.com writes:
András Major andras.g.ma...@gmail.com wrote:
Hi Eric,
Your file uses #+data: where I use #+tblname: -- which one is the
official one? I have the impression that it's #+data:, but I haven't
come across that in the manual or elsewhere before.
Eric Schulte schulte.e...@gmail.com writes:
Nick Dokos nicholas.do...@hp.com writes:
András Major andras.g.ma...@gmail.com wrote:
Hi Eric,
Your file uses #+data: where I use #+tblname: -- which one is the
official one? I have the impression that it's #+data:, but I haven't
come
26 matches
Mail list logo
