Re: Bug: :noexport: tag prevents table functioning as babel code block input [7.7 (release_7.7.167.gfceb)]

[Bastien <bzg@altern.org>]

Hi András,

András Major <andras.g.major@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 with :noexport:, the result is exactly the same.

I'm not sure I understand -- does it mean that C-cC-c on #+begin_src 
fails in the example below?

,----
| * Headline :noexport:
| 
|   #+tblname: table1
|   | n | x |  y1 |   y2 |
|   |---+---+-----+------|
|   | 0 | 1 | 2.0 |  3.0 |
|   | 1 | 2 | 2.1 |  2.0 |
|   | 2 | 3 | 2.0 |  0.3 |
|   | 3 | 4 | 1.0 |  0.6 |
|   | 4 | 5 | 1.4 | -0.1 |
|   | 5 | 6 | 1.6 |  1.2 |
| 
|   #+begin_src gnuplot :file bug_gnuplot.png :var t=table1
|     set size square
|     plot t u 2:3 w lp, t u 2:4 w lp
|   #+end_src
`----

It works for me.


> In my little experience, it work, and I think it's a desirable feature
> too.  I'm not really keen on creating a section for a table just so
> that I can hide it.

Tags only have meaning on headlines, whether it's for really tagging the
headlines or for (un)selecting them during the export process.  

If we want export-related function specifically for tables, I'd rather 
use something like #+export_table: and a list of options.  

HTH,

-- 
 Bastien