Dear John, This does *not* work for me. See the attached files. I begin to suspect a very recent bug : I'm following MELPA, which updates about once a week. My org-version says: Org mode version 9.2.3 (9.2.3-11-g42abf5-elpaplus @ /home/charpent/.emacs.d/elpa/org-plus- contrib-20190429/). Cordially, --Emmanuel Charpentier Le mardi 30 avril 2019 à 13:46 -0400, John Kitchin a écrit : > This works as expected in LaTeX for me with org-ref (you could > probably use raw latex if you wanted): > #+caption: The first source block. label:src-1#+BEGIN_SRC > ipythonprint('Hello world')#+END_SRC > > Later we refer to the code in Listing ref:src-1 or ref:src-2. That is > different than Figure ref:fig-1. > #+caption: My figure. label:fig-1[[./test.png]] > > #+caption: The first source block. label:src-2#+BEGIN_SRC > ipythonprint('Hello world')#+END_SRC > The downside is that for html the src-block links are not numbered. I > don't know how easy that would be to fix in the export functions. > John > > ----------------------------------- > Professor John Kitchin > Doherty Hall A207F > Department of Chemical Engineering > Carnegie Mellon University > Pittsburgh, PA 15213 > 412-268-7803 > @johnkitchin > http://kitchingroup.cheme.cmu.edu > > > > On Tue, Apr 30, 2019 at 1:40 PM Emmanuel Charpentier < > emm.charpentier@free.fr> wrote: > > Hi, Nicolas ! > > > > > > > > Le mardi 30 avril 2019 à 19:05 +0200, Nicolas Goaziou a écrit : > > > > > Hello, > > > > > > > > > > Emmanuel Charpentier writes: > > > > > > > > > > > Whereas the HTML exporter correctly recognize a source block as > > > > > > such, > > > > > > the LaTeX/PDF exporter does not. > > > > > > > > > > > > This can be demonstrated in a (minimal) org file using *only* > > the > > > > > > built-in tools (no external packages), where a source block is > > > > > > labelled > > > > > > as such by the HTML exporter but as a figure by the LaTeX > > > > > > exporter.The > > > > > > generated LaTeX source shows a suspicious > > > > > > "\captionof{figure}{\label{orgf2d4160}" in the export of the > > source > > > > > > block. > > > > > > > > > > > > Further tests (not shown) show that the proble persists when > > org- > > > > > > mode > > > > > > is set up to use the minted package for LaTeX export of source > > > > > > blocks > > > > > > (minted is indeed used, but the block is s still mislabeled). > > > > > > > > > > What LaTeX code do you suggest instead? > > > > > > > > Dunno. Maybe \captionof{listing} ? Or let minted do its thing ? > > Anyway, > > > > in most cases, the code excerpts will be too long for a float ; the > > > > idea is to send them (unfloated but labeled/captioned) in an > > appendix > > > > and point to them via a link. > > > > > > > > [ BTW : we should stop suggesting to use listings, which is > > problematic > > > > for anything not strictly ASCII, bloody likely to occur at least on > > a > > > > comment/prompt for most of mankind... Listingsutf8 is but a patch > > > > working only for (a subset of) European languages. Arabic, Hebrew, > > > > Asian languages : nope. Minted in (xe|lua)tex is probably more > > usable > > > > (but needs --shell-escape, which can justifiably frowned upon... ]. > > > > > > > > > > The org source and resulting pdf and html files are available > > here > > > > > > : > > > > > > > > https://drive.google.com/drive/folders/1bQmaefiztW9ZDRNLcjOD_WbEmTg4d8dG?usp=sharing > > > > > > > > > > Could you send your ECM in the ML without requiring to access > > Google > > > > > Drive? > > > > > > > > Attached. > > > > > > > > But please coordinate with Bastien, who asked me just yesterday to > > > > avoid posting fat attachments to a message going to a lot of > > people. > > > > Which I did (to no avail : the "heavy" mail went through anyway. Go > > > > figure.... ;-). > > > > > > > > > > > > > Thank you. > > > > > > > > You're welcome ;-). Thank YOU for considering scratching *MY* > > itch... > > > > > > > > -- > > > > Emmanuel Charpentier > > > > > >