emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Manish <mailtomanish.sharma@gmail.com>
To: Carsten Dominik <dominik@science.uva.nl>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Including files, line numbers and codeline references
Date: Thu, 8 Jan 2009 17:10:30 +0530	[thread overview]
Message-ID: <e7cdbe30901080340k4c372d8flf561e3d532660793@mail.gmail.com> (raw)
In-Reply-To: <5C213F1D-AFD7-45A8-8681-CDD6EF372E19@uva.nl>

  On Thu, Jan 8, 2009 at 4:45 PM, Carsten Dominik wrote:
  > Hi Manish,
  > On Jan 8, 2009, at 9:35 AM, Manish wrote:
  >
  > 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?)
  >
  > Yes, you can now just add the switched to the end of the INCLUDE line.

Already?!  Yep, works now.

  >
  > 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.)
  >
  > This should now work

It does too. :)

  >
  > 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
  > `----
  >
  > I guess you have some math snippets in the file, and
  >  (setq org-export-with-LaTeX-fragments t)
  >
  > ?? Then all these snippets will be processed though LaTeX to create images
  > for inclusion into the HTML file.

I will investigate it but I do not recall having added any math stuff
in that file.

  >
  > Also, I was trying the example from documentation with:
  >
  > #+INCLUDE "~/.emacs" src emacs-lisp
  >
  > I cannot reproduce it, I guess you have something
  > like "END_HTML" in your .emacs file? Try to make a minimal example.

Sure.  I will try to create one.

Thanks again!

Best regards,
-- 
Manish

      reply	other threads:[~2009-01-08 11:40 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08  8:35 Manish
2009-01-08 11:15 ` Carsten Dominik
2009-01-08 11:40   ` Manish [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e7cdbe30901080340k4c372d8flf561e3d532660793@mail.gmail.com \
    --to=mailtomanish.sharma@gmail.com \
    --cc=dominik@science.uva.nl \
    --cc=emacs-orgmode@gnu.org \
    --subject='Re: Including files, line numbers and codeline references' \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Code repositories for project(s) associated with this inbox:

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).