-
Notifications
You must be signed in to change notification settings - Fork 109
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
Pimp codeexamples (issue #640) #711
Conversation
…s in `extract.lua` - started adding libraries to the codeexamples
(so far not all needed styles and definitions were added using `pre` key)
…r files fail TeXing using the build bash script. ! `pre` stuff containing (double) hashes fail in automatic testing, because single hashes are needed there ! first `codeexample` in `pgfmanual-en-xxcolor.tex` isn't extracted (Is this a bug in `extract.lua`? Are there more `codeexamples` elsewhere that are not extracted?) ! second `codeexample` in pgfmanual-en-xxcolor.tex` shows spurious "-6pt-6pt" in the PDF in front of the `minipage` when TeXing the extracted file
- incorporated fixes from main PGF repository (provided by Henri) - changed `\documentclass` from `article` to `standalone` - reordered some stuff - started switching from `libraries/tikz={...}` to `preamble={\usetikzlibrary{...}}`
…kzlibrary{...}}` - continued with following files in the manual
- continued adding code to make extracted `codeexample`s work
(so they can be found more easily)
…unt for the manual files at `/tex/generic/pgf/graphdrawing/lua/pgf/` - accounted for some more `codeexample`s in `doc/generic/pgf/text-en/`
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great effort, but as it stands it still needs a bit of work before it is ready to merge.
tex/generic/pgf/graphdrawing/lua/pgf/gd/control/ComponentAlign.lua
Outdated
Show resolved
Hide resolved
tex/generic/pgf/graphdrawing/lua/pgf/gd/control/ComponentDistance.lua
Outdated
Show resolved
Hide resolved
You should also enable Travis CI for your repository so that the automated checks are run. Right now the manual fails to build. Go to https://travis-ci.com/Mo-Gul/pgf, sign in with GitHub and follow the instructions to enable it. |
Thank you for the Travis CI hint. It works fine. But after some more changes (as you can see) now I don't have a clue any more why my Travis CI checks don't succeed. Could you please have a look at them and give me a hint!? I also want to note that LuaLaTeXing the last commits on my (local) machine works perfectly fine. The last commit results in a 1302 pages PDF and the only "error" I get in my LOG is
|
https://travis-ci.com/Mo-Gul/pgf/jobs/217394242#L1952-L1968
|
Thank you for that but unfortunately that doesn't help me much. When I look at line in If you know what exactly causes the problem it would be nice if you could state me the solution. If I have to search for the problem myself this would mean that I have to do an unknown number of commits where I comment different parts until I maybe have found it in the Travis CI logs, because -- as I mentioned already -- I do not get any of these errors on my computer ... |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just noticed that you reverted several bugfixes as part of this PR. This has to be fixed.
Actually you reverted almost all the bugfixes from the 3.1.4 release. |
To the last 4 comments: And I hopefully did not revert all the bugfixes, but they are just not implemented yet, because I am x commits behind the master ... If I really should have created a mess it would be great if you could help me. But in principle everything should be fine when only the documentation files can -- later, when I am again through all the files -- accepted in the pull request. Maybe I can even just provide these files in the pull request. We'll see. Please advice if I can resolve the last two items or do it yourself when everything is fine with that (again), thanks. |
One more thing. Providing all the stuff not with |
Printing of the pgf/doc/generic/pgf/macros/pgfmanual-en-macros.tex Lines 1833 to 1837 in f5d0ffd
|
- started moving `setup code,hidden` to `preamble` of the `codeexample`s
…e `codeexample`s - minor stuff
@hmenke , ok, I am through again. This time only 10
Besides that there are some examples in
where a leading space seems to be added (see DiffPDF.pdf). I'll have a look at that later. |
- had a look at the `codeexample`s where a leading space was introduced (see #711 (comment)). Some of them could be removed but others are introduced because of code added to the `pre` key where I don't have a clue if/how this can be avoided
…fault) - therefore added loading `graphs` library in `graphs.standard` library - adjusted `preamble` code in `codeexample`s accordingly - there exist `graphdrawing` `codeexample`s in the manual that don't need the `graphs` library --> adjusted `codeexample`s accordingly
You have to fix that botched merge 4dd4ac8 before I can consider this. You reverted all of the fixes of the 3.1.4 release. |
… `pgfmanual-en-base-quick.tex` Co-Authored-By: Henri Menke <[email protected]>
As I have commented earlier in commit 2428348 I merged To avoid that I do some more bullshit regarding merges etc., I would appreciate it if you (@hmenke) could do the necessary work. To do so I (hopefully) invited you as collaborator to the fork. |
Closed in favour of #729 |
- had a look at the `codeexample`s where a leading space was introduced (see pgf-tikz#711 (comment)). Some of them could be removed but others are introduced because of code added to the `pre` key where I don't have a clue if/how this can be avoided
everything important is written in the comments to issue #640.