Listing filenames #2276
Closed
Listing filenames #2276
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Took this for a quick drive on top of #2272. I'd rather see some visual/typographical separation between the filename and the caption. What do you think of placing it in parentheses, after the caption concludes, and style it with a monospace font? Perhaps LaTeX needs to pass this as an argument to the environment, so style writers can have some control over placment and look? |
ascholerChemeketa
force-pushed
the
listing-filenames
branch
from
64f49ab to
f7ffc3c
Compare
|
How about monospace bold with parens but before the caption? In a quick tour of programming texts, if the filename is listed, it tends to look like part of the title of the block. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Basic implementation of filenames for listings. No fancy download links, but I'm not convinced they are needed as anywhere a link would be active the reader can copy/paste into an editor.
It is quite likely there is a more ideal LaTeX implementation.
Built off of #2272 - suggest resolving it first.