Word wrap 64 character hexadecimal strings in verbatim JSON












0















I'd like to document example requests/replies in our protocol per How to write narrative documentation. We're using the texlive-latex-base on Ubuntu for our documentation, and I'm linting with lacheck and chktex - I've managed to fix all warnings.



From questions such as this one I've managed to get runs of hex in my paragraphs flowing well, with the seqsplit package (might have to accept an extra dependency for it).



I need to document JSON with 32 byte hex encoded values. I've tried wrapping verb|| with seqsplit{} and with begin{lstlisting}...end{lstlisting} without success. I've tried putting verb only around the { "key": " and " } parts, and using texttt and seqsplit on the inner part without success - the line still merrily flows right off the page. Ah, these are in items of a begin{description}...end{description} block if relevant.



How can I get these verbatim long lines to wrap? The common answer appears to be lstlisting, but it has not worked for me, and additionally causes the linter to complain about "s from the JSON.










share|improve this question







New contributor




Iiridayn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Please -- as usual here -- can you show us a short compilable tex code we can copy and play with?

    – Kurt
    1 min ago
















0















I'd like to document example requests/replies in our protocol per How to write narrative documentation. We're using the texlive-latex-base on Ubuntu for our documentation, and I'm linting with lacheck and chktex - I've managed to fix all warnings.



From questions such as this one I've managed to get runs of hex in my paragraphs flowing well, with the seqsplit package (might have to accept an extra dependency for it).



I need to document JSON with 32 byte hex encoded values. I've tried wrapping verb|| with seqsplit{} and with begin{lstlisting}...end{lstlisting} without success. I've tried putting verb only around the { "key": " and " } parts, and using texttt and seqsplit on the inner part without success - the line still merrily flows right off the page. Ah, these are in items of a begin{description}...end{description} block if relevant.



How can I get these verbatim long lines to wrap? The common answer appears to be lstlisting, but it has not worked for me, and additionally causes the linter to complain about "s from the JSON.










share|improve this question







New contributor




Iiridayn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





















  • Please -- as usual here -- can you show us a short compilable tex code we can copy and play with?

    – Kurt
    1 min ago














0












0








0








I'd like to document example requests/replies in our protocol per How to write narrative documentation. We're using the texlive-latex-base on Ubuntu for our documentation, and I'm linting with lacheck and chktex - I've managed to fix all warnings.



From questions such as this one I've managed to get runs of hex in my paragraphs flowing well, with the seqsplit package (might have to accept an extra dependency for it).



I need to document JSON with 32 byte hex encoded values. I've tried wrapping verb|| with seqsplit{} and with begin{lstlisting}...end{lstlisting} without success. I've tried putting verb only around the { "key": " and " } parts, and using texttt and seqsplit on the inner part without success - the line still merrily flows right off the page. Ah, these are in items of a begin{description}...end{description} block if relevant.



How can I get these verbatim long lines to wrap? The common answer appears to be lstlisting, but it has not worked for me, and additionally causes the linter to complain about "s from the JSON.










share|improve this question







New contributor




Iiridayn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.












I'd like to document example requests/replies in our protocol per How to write narrative documentation. We're using the texlive-latex-base on Ubuntu for our documentation, and I'm linting with lacheck and chktex - I've managed to fix all warnings.



From questions such as this one I've managed to get runs of hex in my paragraphs flowing well, with the seqsplit package (might have to accept an extra dependency for it).



I need to document JSON with 32 byte hex encoded values. I've tried wrapping verb|| with seqsplit{} and with begin{lstlisting}...end{lstlisting} without success. I've tried putting verb only around the { "key": " and " } parts, and using texttt and seqsplit on the inner part without success - the line still merrily flows right off the page. Ah, these are in items of a begin{description}...end{description} block if relevant.



How can I get these verbatim long lines to wrap? The common answer appears to be lstlisting, but it has not worked for me, and additionally causes the linter to complain about "s from the JSON.







line-breaking texlive documentation json






share|improve this question







New contributor




Iiridayn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.











share|improve this question







New contributor




Iiridayn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









share|improve this question




share|improve this question






New contributor




Iiridayn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.









asked 13 mins ago









IiridaynIiridayn

1013




1013




New contributor




Iiridayn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.





New contributor





Iiridayn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.






Iiridayn is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.













  • Please -- as usual here -- can you show us a short compilable tex code we can copy and play with?

    – Kurt
    1 min ago



















  • Please -- as usual here -- can you show us a short compilable tex code we can copy and play with?

    – Kurt
    1 min ago

















Please -- as usual here -- can you show us a short compilable tex code we can copy and play with?

– Kurt
1 min ago





Please -- as usual here -- can you show us a short compilable tex code we can copy and play with?

– Kurt
1 min ago










0






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',
autoActivateHeartbeat: false,
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
});


}
});






Iiridayn is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f473856%2fword-wrap-64-character-hexadecimal-strings-in-verbatim-json%23new-answer', 'question_page');
}
);

Post as a guest















Required, but never shown

























0






active

oldest

votes








0






active

oldest

votes









active

oldest

votes






active

oldest

votes








Iiridayn is a new contributor. Be nice, and check out our Code of Conduct.










draft saved

draft discarded


















Iiridayn is a new contributor. Be nice, and check out our Code of Conduct.













Iiridayn is a new contributor. Be nice, and check out our Code of Conduct.












Iiridayn is a new contributor. Be nice, and check out our Code of Conduct.
















Thanks for contributing an answer to TeX - LaTeX Stack Exchange!


  • Please be sure to answer the question. Provide details and share your research!

But avoid



  • Asking for help, clarification, or responding to other answers.

  • Making statements based on opinion; back them up with references or personal experience.


To learn more, see our tips on writing great answers.




draft saved


draft discarded














StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f473856%2fword-wrap-64-character-hexadecimal-strings-in-verbatim-json%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

Lallio

Unable to find Lightning Node

Futebolista