On 05/14/2018 01:28 PM, Jürgen Spitzmüller wrote: > Am Montag, den 14.05.2018, 13:18 -0400 schrieb Richard Kimberly Heck: >> I've been thinking about this, too, and had come to a somewhat >> similar >> conclusion, though not with nearly as much detail. I.e., it seemed to >> me >> that there was something wrong with how the parents were being >> assigned >> when we clone. Unfortunately, there is a reason that we clone from >> the >> master: There may be macros defined there that are needed in the >> child. >> (See 2d6173d8103.) It may be that we should have said that wasn't a >> bug: >> If you view only the child, then you shouldn't expect macros defined >> outside it to work. Maybe the include_only support allows people to >> do >> what they were trying to do here by viewing only the child? > That's definitely wrong. A child compiled standalone should not inherit > anything from a parent. This opens up for all sorts of bugs. > >> It seems to me that, in some ways, this is tied up with different >> understandings people have of the master-child relationship, and what >> it means to view "only the child". > Maybe. But "Viewing the child" is actually not what is the case here. > It's not a child in that case (we have includeonly support for that > case).
Yes, I agree, but I think that's how people often think of it. They're not really treating the child as a standalone document. They just want to see the PDF of that chapter (say), and not the whole thing. I think that must be what Joel is doing. Certainly Chapter 1 is not going to be a standalone document. (Joel, tell me if I'm wrong.) As you say, the right way to do that is to use the includeonly stuff. But I'm guessing Joel isn't the only person who would try to 'view only one chapter' this way. So probably 2d6173d8103 was a mistake: We should just have said that you can't do that. But that was before the includeonly support, I believe, so maybe it made sense then? I'm not sure. I wonder if it would help people here to have some LFUN that would allow one to "view only the child" in the way people want. What it would do, basically, is includeonly the current Buffer and its descendants, then view that. I.e., you wouldn't have to go to the master, fiddle with those settings, and then view. So it would work kind of like master-buffer-view, but take care of the includeonly stuff for you. Then again, that might not work in a lot of cases. E.g., you might need to include the bibliography always---which is why Joel has that complex ERT. (But then maybe there could be a setting for that? But maybe that gets too complicated....) Riki
