Including files, line numbers and codeline references

* Including files, line numbers and codeline references
@ 2009-01-08  8:35 Manish
  2009-01-08 11:15 ` Carsten Dominik
  0 siblings, 1 reply; 3+ messages in thread
From: Manish @ 2009-01-08  8:35 UTC (permalink / raw)
  To: emacs-orgmode@gnu.org

There are multiple but related issues and requests in the mail below.
Wasn't sure so haven't split into separate emails.  Please excuse me
if this is not correct form.

  On Mon, Jan 5, 2009 at 6:02 PM, Carsten Dominik wrote:
  >
  > I have just uploaded 6.17a which revamps the codeline references stuff,
  > in the following way:
  >
  > 1. The default label now looks like   (ref:name)
  >
  > 2. The default format is defined in org-coderef-label-format,
  >  with the default value "(ref:%s)".
  >

This is very nice.

  > 3. You can change the format for each individual snippet with the -l switch:
  >
  >   #+BEGIN_SRC pascal -n -r -l "((%s))"

Is it possible to use this line numbering facility for files included
in by "#+INCLUDE" mechanism (sec. 12.1 of manual?)

  >
  > 4. Links to the labels have also changed, they are now
  >
  >    [[(name)]] or [[(name)][in line (name)]]
  >
  >  instead of
  >
  >    [[((name))]] or [[((name))][in line ((name))]]
  >
  >  i.e. only single parenthesis around the label name.

I added a (ref:string) after a comment mark in the original file being
included and created a link like shown above.  The highlighting works
fine but the link does not reflect the line number of the text (didn't
also expect to work until lines were numbered.)

Surprisingly, publish (HTML) attempt also tries to create some .tex
files, not sure why.

,----[ *Messages* ]
| Publishing file d:/home/zms/gehc.git/gdoc/dg.org
| Exporting...
| OVERVIEW
| CONTENTS...done
| Creating LaTeX image 1
| Creating LaTeX image 2
| Creating LaTeX image 3
| Failed to create dvi file from d:/home/zms/tmp/orgtex34725Zc.tex
| Creating LaTeX image 4
| Failed to create dvi file from d:/home/zms/tmp/orgtex3472Gki.tex
| Creating LaTeX image 5
| Failed to create dvi file from d:/home/zms/tmp/orgtex3472Tuo.tex
| Creating LaTeX image 6
| Failed to create dvi file from d:/home/zms/tmp/orgtex3472g4u.tex
| Creating LaTeX image 7
| Failed to create dvi file from d:/home/zms/tmp/orgtex3472tC1.tex
| Exporting... [2 times]
| Saving file d:/home/zms/gehc.git/gdoc_pub/dg.html...
| Wrote d:/home/zms/gehc.git/gdoc_pub/dg.html
| Exporting... done
`----

Also, I was trying the example from documentation with:

#+INCLUDE "~/.emacs" src emacs-lisp

But it fails with following error:
"org-export-select-backend-specific-text: Stack overflow in regexp matcher"
It works when I trim the file size down.  Is there some
variable that controls the size of file it can fontify during export?

Thanks for another great feature.

-- 
Manish

^ permalink raw reply	[flat|nested] 3+ messages in thread