-
Notifications
You must be signed in to change notification settings - Fork 329
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ Printing ]: Snippet for link list #3308
Comments
I don't know about processing it, but we could add a snippet that looked through all the code, got the links, then output them and their page of reference plus their name, so the output was something like this:
it will need some work, but we can make that work. This is, until we get brew to pdf to work with links, if we can. |
Consider also the reflink system, which is almost built for this purpose (coming at it from the other direction)
Immediate problem is that Marked does not render the reflink definition as html (only uses of the reflink). We could change that to render an element with an extra class on it, a class we use to hide it by default. Second problem is that this only works where it is used — that is, an author must use a reflink if they want that link to appear in this way. This might be too tedious. Third problem is that this doesn't work if the author wants multiple links with the same text but different hrefs (e.g. "click here" [a bad eample]). So .. a snippet that inserts calculated text would be better. The snippet code should
|
Does the current version of the Table of Contents code not solve this problem? |
OP wants a snippet that inputs all the hyperlinks' text as text, so links are not lost on print, on paper. Table of contents has nothing to do with this. |
Your idea:
Currently, If you link anything in homebrewery using markdown the link is masked by the text in the []. My request is that similar to the table of contents that auto generates links to all the headers, this feature would auto generate a page that contains the raw links so that if a user was to print out their doc, they would not lose access to the links. Either a generated page at the end of the document or perhaps an annotated footer with links would suffice.
The text was updated successfully, but these errors were encountered: