How to have code both word-wrapped and flush with an example number?
1
Using verb| | in an example fails to give word-wrapping.
Using:
%! TEX = xelatex
documentclass[a4paper, titlepage]{book}
usepackage{listings}
lstset{
breaklines=true
}
newcommand{inlineCode}{lstinline[basicstyle=normalsizettfamily]}
usepackage{hyperref}
usepackage{memhfixc}
usepackage[nameinlink,noabbrev,capitalise]{cleveref}
usepackage{cgloss4e}
usepackage{enumerate}
usepackage{gb4e}
sloppy
begin{document}
begin{exe}
ex begin{lstlisting}
some code here
end{lstlisting}
end{exe}
% or
begin{enumerate}
item begin{lstlisting}
some code here
end{lstlisting}
end{enumerate}
% fails to produce the text flush with the example number, in exactly the same way beyond the different numbering style (I would prefer to be using the gb4e package for consistency).
% Using:
begin{exe}
ex inlineCode{some code}\
inlineCode{some more code}\
end{exe}
% works, but makes telling lines apart very difficult, unless I input indentation manually.
% Likewise, using:
begin{exe}
ex begin{xlistn}
ex some code
ex some code continued
end{xlistn}
end{exe}
% spaces them too far apart (or it did in my other document... I'm unsure of why there is a difference, perhaps it is to do with my fonts: Gentium Plus for the body; Noto Sans Mono as for the ttfamily - mono DOES = ttfamily? - though this might change if I can find a tt font to fit Gentium better.)
% Thank you.
end{document}
listings examples
asked Jan 3 at 22:51
KartöfluvofanKartöfluvofan
62
add a comment |
1
Using verb| | in an example fails to give word-wrapping.
Using:
%! TEX = xelatex
documentclass[a4paper, titlepage]{book}
usepackage{listings}
lstset{
breaklines=true
}
newcommand{inlineCode}{lstinline[basicstyle=normalsizettfamily]}
usepackage{hyperref}
usepackage{memhfixc}
usepackage[nameinlink,noabbrev,capitalise]{cleveref}
usepackage{cgloss4e}
usepackage{enumerate}
usepackage{gb4e}
sloppy
begin{document}
begin{exe}
ex begin{lstlisting}
some code here
end{lstlisting}
end{exe}
% or
begin{enumerate}
item begin{lstlisting}
some code here
end{lstlisting}
end{enumerate}
% fails to produce the text flush with the example number, in exactly the same way beyond the different numbering style (I would prefer to be using the gb4e package for consistency).
% Using:
begin{exe}
ex inlineCode{some code}\
inlineCode{some more code}\
end{exe}
% works, but makes telling lines apart very difficult, unless I input indentation manually.
% Likewise, using:
begin{exe}
ex begin{xlistn}
ex some code
ex some code continued
end{xlistn}
end{exe}
% spaces them too far apart (or it did in my other document... I'm unsure of why there is a difference, perhaps it is to do with my fonts: Gentium Plus for the body; Noto Sans Mono as for the ttfamily - mono DOES = ttfamily? - though this might change if I can find a tt font to fit Gentium better.)
% Thank you.
end{document}
listings examples
asked Jan 3 at 22:51
KartöfluvofanKartöfluvofan
62
3
Welcome to TeX.SE! Can you please make your code snippets compilable? Then we do not have to guess your used class, called packages related to the issue ...
– Kurt
Jan 3 at 22:58
Edited the original so that it should be executable. Thank you.
– Kartöfluvofan
Jan 3 at 23:34
add a comment |
1
1
1
1
Using verb| | in an example fails to give word-wrapping.
Using:
%! TEX = xelatex
documentclass[a4paper, titlepage]{book}
usepackage{listings}
lstset{
breaklines=true
}
newcommand{inlineCode}{lstinline[basicstyle=normalsizettfamily]}
usepackage{hyperref}
usepackage{memhfixc}
usepackage[nameinlink,noabbrev,capitalise]{cleveref}
usepackage{cgloss4e}
usepackage{enumerate}
usepackage{gb4e}
sloppy
begin{document}
begin{exe}
ex begin{lstlisting}
some code here
end{lstlisting}
end{exe}
% or
begin{enumerate}
item begin{lstlisting}
some code here
end{lstlisting}
end{enumerate}
% fails to produce the text flush with the example number, in exactly the same way beyond the different numbering style (I would prefer to be using the gb4e package for consistency).
% Using:
begin{exe}
ex inlineCode{some code}\
inlineCode{some more code}\
end{exe}
% works, but makes telling lines apart very difficult, unless I input indentation manually.
% Likewise, using:
begin{exe}
ex begin{xlistn}
ex some code
ex some code continued
end{xlistn}
end{exe}
% spaces them too far apart (or it did in my other document... I'm unsure of why there is a difference, perhaps it is to do with my fonts: Gentium Plus for the body; Noto Sans Mono as for the ttfamily - mono DOES = ttfamily? - though this might change if I can find a tt font to fit Gentium better.)
% Thank you.
end{document}
listings examples
asked Jan 3 at 22:51
KartöfluvofanKartöfluvofan
62
Using verb| | in an example fails to give word-wrapping.
Using:
%! TEX = xelatex
documentclass[a4paper, titlepage]{book}
usepackage{listings}
lstset{
breaklines=true
}
newcommand{inlineCode}{lstinline[basicstyle=normalsizettfamily]}
usepackage{hyperref}
usepackage{memhfixc}
usepackage[nameinlink,noabbrev,capitalise]{cleveref}
usepackage{cgloss4e}
usepackage{enumerate}
usepackage{gb4e}
sloppy
begin{document}
begin{exe}
ex begin{lstlisting}
some code here
end{lstlisting}
end{exe}
% or
begin{enumerate}
item begin{lstlisting}
some code here
end{lstlisting}
end{enumerate}
% fails to produce the text flush with the example number, in exactly the same way beyond the different numbering style (I would prefer to be using the gb4e package for consistency).
% Using:
begin{exe}
ex inlineCode{some code}\
inlineCode{some more code}\
end{exe}
% works, but makes telling lines apart very difficult, unless I input indentation manually.
% Likewise, using:
begin{exe}
ex begin{xlistn}
ex some code
ex some code continued
end{xlistn}
end{exe}
% spaces them too far apart (or it did in my other document... I'm unsure of why there is a difference, perhaps it is to do with my fonts: Gentium Plus for the body; Noto Sans Mono as for the ttfamily - mono DOES = ttfamily? - though this might change if I can find a tt font to fit Gentium better.)
% Thank you.
end{document}
listings examples
listings examples
asked Jan 3 at 22:51
KartöfluvofanKartöfluvofan
62
asked Jan 3 at 22:51
KartöfluvofanKartöfluvofan
62
edited Jan 3 at 23:34
Kartöfluvofan
asked Jan 3 at 22:51
KartöfluvofanKartöfluvofan
62
asked Jan 3 at 22:51
KartöfluvofanKartöfluvofan
62
asked Jan 3 at 22:51
KartöfluvofanKartöfluvofan
62
62
3
Welcome to TeX.SE! Can you please make your code snippets compilable? Then we do not have to guess your used class, called packages related to the issue ...
– Kurt
Jan 3 at 22:58
Edited the original so that it should be executable. Thank you.
– Kartöfluvofan
Jan 3 at 23:34
add a comment |
3
Welcome to TeX.SE! Can you please make your code snippets compilable? Then we do not have to guess your used class, called packages related to the issue ...
– Kurt
Jan 3 at 22:58
Edited the original so that it should be executable. Thank you.
– Kartöfluvofan
Jan 3 at 23:34
3
3
Welcome to TeX.SE! Can you please make your code snippets compilable? Then we do not have to guess your used class, called packages related to the issue ...
– Kurt
Jan 3 at 22:58
Welcome to TeX.SE! Can you please make your code snippets compilable? Then we do not have to guess your used class, called packages related to the issue ...
– Kurt
Jan 3 at 22:58
Edited the original so that it should be executable. Thank you.
– Kartöfluvofan
Jan 3 at 23:34
Edited the original so that it should be executable. Thank you.
– Kartöfluvofan
Jan 3 at 23:34
add a comment |
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
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f468473%2fhow-to-have-code-both-word-wrapped-and-flush-with-an-example-number%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
draft saved
draft discarded
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
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2ftex.stackexchange.com%2fquestions%2f468473%2fhow-to-have-code-both-word-wrapped-and-flush-with-an-example-number%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
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
3
Welcome to TeX.SE! Can you please make your code snippets compilable? Then we do not have to guess your used class, called packages related to the issue ...
– Kurt
Jan 3 at 22:58
Edited the original so that it should be executable. Thank you.
– Kartöfluvofan
Jan 3 at 23:34