Listing linerange markers sometimes not being recognised











up vote
0
down vote

favorite












I am documenting several large XSLT scripts using the lstinputlisting command. I have set Processing Instructions in the scripts to mark off suitably-sized blocks of code to document, mostly 10–20 lines each block, in the format



<?doc val1?>


and



<?doc val2?>


(etc; many dozens of these) and included the options rangeprefix=<?doc ,rangesuffix=?>,linerange=val1-val2



After the first code block has been done (correctly), it stops recognising the PI pattern and just includes all of the rest of the script to the end of the file, even displaying the PIs that it was supposed to have recognised.



These scripts are not mine to publish here, but before I try to construct a MWE, I wanted to know if anyone else has hit this problem. It only seems to occur with larger files (the current problematic one is 92KB and 2330 lines).



This happens with both pdflatex Version 3.14159265-2.6-1.40.16 and XeLaTeX Version 3.14159265-2.6-0.99992, both with LaTeX <2016/02/01> and listings.sty 1.6 (2015/06/04)










share|improve this question






















  • Can you post a complete minimal working example, including an XSLT file?
    – Andrew
    8 mins ago















up vote
0
down vote

favorite












I am documenting several large XSLT scripts using the lstinputlisting command. I have set Processing Instructions in the scripts to mark off suitably-sized blocks of code to document, mostly 10–20 lines each block, in the format



<?doc val1?>


and



<?doc val2?>


(etc; many dozens of these) and included the options rangeprefix=<?doc ,rangesuffix=?>,linerange=val1-val2



After the first code block has been done (correctly), it stops recognising the PI pattern and just includes all of the rest of the script to the end of the file, even displaying the PIs that it was supposed to have recognised.



These scripts are not mine to publish here, but before I try to construct a MWE, I wanted to know if anyone else has hit this problem. It only seems to occur with larger files (the current problematic one is 92KB and 2330 lines).



This happens with both pdflatex Version 3.14159265-2.6-1.40.16 and XeLaTeX Version 3.14159265-2.6-0.99992, both with LaTeX <2016/02/01> and listings.sty 1.6 (2015/06/04)










share|improve this question






















  • Can you post a complete minimal working example, including an XSLT file?
    – Andrew
    8 mins ago













up vote
0
down vote

favorite









up vote
0
down vote

favorite











I am documenting several large XSLT scripts using the lstinputlisting command. I have set Processing Instructions in the scripts to mark off suitably-sized blocks of code to document, mostly 10–20 lines each block, in the format



<?doc val1?>


and



<?doc val2?>


(etc; many dozens of these) and included the options rangeprefix=<?doc ,rangesuffix=?>,linerange=val1-val2



After the first code block has been done (correctly), it stops recognising the PI pattern and just includes all of the rest of the script to the end of the file, even displaying the PIs that it was supposed to have recognised.



These scripts are not mine to publish here, but before I try to construct a MWE, I wanted to know if anyone else has hit this problem. It only seems to occur with larger files (the current problematic one is 92KB and 2330 lines).



This happens with both pdflatex Version 3.14159265-2.6-1.40.16 and XeLaTeX Version 3.14159265-2.6-0.99992, both with LaTeX <2016/02/01> and listings.sty 1.6 (2015/06/04)










share|improve this question













I am documenting several large XSLT scripts using the lstinputlisting command. I have set Processing Instructions in the scripts to mark off suitably-sized blocks of code to document, mostly 10–20 lines each block, in the format



<?doc val1?>


and



<?doc val2?>


(etc; many dozens of these) and included the options rangeprefix=<?doc ,rangesuffix=?>,linerange=val1-val2



After the first code block has been done (correctly), it stops recognising the PI pattern and just includes all of the rest of the script to the end of the file, even displaying the PIs that it was supposed to have recognised.



These scripts are not mine to publish here, but before I try to construct a MWE, I wanted to know if anyone else has hit this problem. It only seems to occur with larger files (the current problematic one is 92KB and 2330 lines).



This happens with both pdflatex Version 3.14159265-2.6-1.40.16 and XeLaTeX Version 3.14159265-2.6-0.99992, both with LaTeX <2016/02/01> and listings.sty 1.6 (2015/06/04)







listings






share|improve this question













share|improve this question











share|improve this question




share|improve this question










asked 1 hour ago









Peter Flynn

1,46621319




1,46621319












  • Can you post a complete minimal working example, including an XSLT file?
    – Andrew
    8 mins ago


















  • Can you post a complete minimal working example, including an XSLT file?
    – Andrew
    8 mins ago
















Can you post a complete minimal working example, including an XSLT file?
– Andrew
8 mins ago




Can you post a complete minimal working example, including an XSLT file?
– Andrew
8 mins ago















active

oldest

votes











Your Answer








StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "85"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});














 

draft saved


draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f461645%2flisting-linerange-markers-sometimes-not-being-recognised%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown






























active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes
















 

draft saved


draft discarded



















































 


draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f461645%2flisting-linerange-markers-sometimes-not-being-recognised%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown





















































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown

































Required, but never shown














Required, but never shown












Required, but never shown







Required, but never shown







Popular posts from this blog

A CLEAN and SIMPLE way to add appendices to Table of Contents and bookmarks

Calculate evaluation metrics using cross_val_predict sklearn

Insert data from modal to MySQL (multiple modal on website)