Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
C
cas741
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Requirements
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Locked files
Build
Pipelines
Jobs
Pipeline schedules
Test cases
Artifacts
Deploy
Releases
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD analytics
Repository analytics
Code review analytics
Issue analytics
Insights
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
W. Spencer Smith
cas741
Commits
9feedc6f
Commit
9feedc6f
authored
4 years ago
by
W. Spencer Smith
Browse files
Options
Downloads
Patches
Plain Diff
Additional notes on 80 column width and possible ways to do it
parent
8fed4a06
No related branches found
Branches containing commit
No related tags found
No related merge requests found
Changes
2
Hide whitespace changes
Inline
Side-by-side
Showing
2 changed files
BlankProjectTemplate/docs/Writing-Checklist.pdf
+0
-0
0 additions, 0 deletions
BlankProjectTemplate/docs/Writing-Checklist.pdf
BlankProjectTemplate/docs/Writing-Checklist.tex
+19
-1
19 additions, 1 deletion
BlankProjectTemplate/docs/Writing-Checklist.tex
with
19 additions
and
1 deletion
BlankProjectTemplate/docs/Writing-Checklist.pdf
+
0
−
0
View file @
9feedc6f
No preview for this file type
This diff is collapsed.
Click to expand it.
BlankProjectTemplate/docs/Writing-Checklist.tex
+
19
−
1
View file @
9feedc6f
...
...
@@ -51,7 +51,8 @@
tex files. Please be sure to include the
\texttt
{
Comments.tex
}
file in your repo and
in your tex files.
\item
Text lines should be 80 characters wide. That is, the text has a hard-wrap at
80 characters. This is done to facilitate meaingful diffs between different commits.
80 characters. This is done to facilitate meaingful diffs between different
commits. (Some ideas on how to do this are given below.)
\item
Template comments (plt) do not show in the pdf version, either by
removing them, or by turning them off.
\item
References and labels are used so that maintenance is feasible
...
...
@@ -112,4 +113,21 @@
\end{itemize}
\subsubsection*
{
Fixed Width
\LaTeX
{}
Text
}
Having the
\LaTeX
{}
text at a fixed width (hard-wrap) is useful when the source
is under version control. The fixed line lengths help with isolating the
changes between diffs.
Although the checklist mentions an 80 column width, any reasonable fixed width
is fine.
The hard-wrap shouldn't be done manually. Most editors will have some facility
for fixed width. In emacs it is called auto-fill. Some advice from previous
and current students:
\begin{itemize}
\item
In TEXMaker, you can do: User
$
>
$
Run script
$
>
$
hardwordwrap
\item
Wrapping is easy in VSCode, Emacs, and Vim
\end{itemize}
\end{document}
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment