Re: [O] Renaming of +NAME for code blocks to in HTML export, no longer user defined

2016-01-21 Thread Adam Aviv
On Thu, Jan 21, 2016 at 4:20 AM, Nicolas Goaziou wrote: > That and the fact that one might introduce forbidden characters in the > name (e.g., ask the user to know about forbidden characters in the > target format). The generic names are pretty safe. > > Anyway, what about using special blocks to

Re: [O] Renaming of +NAME for code blocks to in HTML export, no longer user defined

2016-01-21 Thread Nicolas Goaziou
Hello, Adam Aviv writes: > Interesting. I don't know if it is a bug, though, as this seems intentional > and matches my experience. The idea being that if you want to label > something, you use the :name tag, but this will make it so the second item > is evaluated, producing a unique identifier.

Re: [O] Renaming of +NAME for code blocks to in HTML export, no longer user defined

2016-01-05 Thread Adam Aviv
On Mon, Jan 4, 2016 at 1:29 PM, Nick Dokos wrote: > It may be a bug: the code (in org-html-src-block) looks like this > > (label (let ((lbl (and (org-element-property :name src-block) > (org-export-get-reference src-block > info >

Re: [O] Renaming of +NAME for code blocks to in HTML export, no longer user defined

2016-01-04 Thread Nick Dokos
Adam Aviv writes: > Hi all, > > I've been using org-mode for some time to manage a course website, and I > developed a hack for source > blocking where if I use the +NAME tag for source doe like so: > > #+NAME: helloworld.cpp > #+BEGIN_SRC c++ -r > #include (ref:include) > > using namespace std

[O] Renaming of +NAME for code blocks to in HTML export, no longer user defined

2016-01-04 Thread Adam Aviv
Hi all, I've been using org-mode for some time to manage a course website, and I developed a hack for source blocking where if I use the +NAME tag for source doe like so: #+NAME: helloworld.cpp #+BEGIN_SRC c++ -r #include (ref:include) using namespace std; (ref:namespace) // Hello World in C++