concordance for child documents

[yihui]

the infrastructure functions are in concordance.R; just need time to arrange the line numbers appropriately

[jalvesaq]

It would be nice to have concordance for child documents implemented as it is by Sweave.
This feature would allow SyncTeX search forward from and backward to subdocuments. Moreover, text editors could take advantage of the enriched -concordance.tex to translate error locations from the LaTeX output to the Rnoweb subdocument source. The picture below shows the output of a master Rnoweb document with child Rnoweb and LaTeX files compiled with Sweave. I added a copy of a wide table in each document to produce Overfull \hboxes (multi_rnoweb.tar.gz). At the end of the compilation, the Vim-R-plugin shows in square brackets the location of errors in the Rnoweb documents:

[yihui]

Yes, I (partially) implemented this once before v1.2 and removed it later because it was too complicated to maintain.

[EmmanuelCharpentier]

I'm afraid I have to support jalvesaq's suggestion.

Jan Gleixner solved the problem of patching foo.synctex.gz with information out of foo-concordance.tex. After slight corrections, an R package has been prepared, to be submitted to CRAN (pending Jan's review), whose use has been tested with emacs and Eclipse+StatET.

The abllity to use the same chunks in different documents is especially important in a lot of Knitr use cases. The use of the concordance information to go back and forth between source .Rnw and target PDF is a HUGE help to debugging and refining such reports. To be able to have both wold be a huge boon in many complicated use cases.
What would it take to support both concordance and children documents ?

Sincerely,

[traminer]

I am wondering whether there is something new with this concordance-with-childs issue.

I confirm that such concordance would be a HUGE help, not only for the back and forth between source .Rnw and PDF, but also (when using the patchLog feature of patchDVI) for jumping from the .log to the concerned place in the source when a LaTeX error is detected.

Best,
Gilbert

[yihui]

Sorry, but no. It is just that I don't want to make the code complicated in this package. It is much easier to maintain it without having to think about concordance for child documents. Honestly I rarely use child documents myself. I use a single document even when writing a 300-page book.

[traminer]

Thanks for this answer. I personally also prefer to weave files independently. I just asked because we are currently extending the support for R, Sweave and knitr for the WinEdt editor with Karl Koeller from the WinEdt team, and we received multiple requests to add something to handle child files.
But no worry. I understand your position.

Best.
Gilbert

From: Yihui Xie [mailto:notifications@github.com]
Sent: Saturday, June 13, 2015 01:37
To: yihui/knitr
Cc: Gilbert Ritschard
Subject: Re: [knitr] concordance for child documents (#225)

Sorry, but no. It is just that I don't want to make the code complicated in this package. It is much easier to maintain it without having to think about concordance for child documents. Honestly I rarely use child documents myself. I use a single document even when writing a 300-page book.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/225#issuecomment-111641539.

[yihui]

Thanks for your understanding.

[github-actions]

This old thread has been automatically locked. If you think you have found something related to this, please open a new issue by following the issue guide (https://yihui.org/issue/), and link to this old issue if necessary.