Activity for Henri Menke
-
Henri Menke posted a comment on merge request #12
Sorry for the late reply. SourceForge decided to not send me notifications anymore, even though I have turned them on in the settings. :-/ There is actually a large number of applications that follow the XDG standard. The Arch Linux wiki has an exhaustive list (https://wiki.archlinux.org/index.php/XDG_Base_Directory). I'm not proposing to remove the file in the home directory. This patch is merely an addition to the already present configuration options. The environment variable $XDG_DATA_HOME and...
-
As you can see from the diff, support for Windows could in principle be added, but I think the XDG base directories are a bit more meaningless in that case. It might still be worthwhile though.
-
Support XDG base directory for gnuplotrc
-
I was too hasty. This is actually a problem in PGF. However, I can't seem to close the issue, there is no button. Please close this for me.
-
ConTeXt: \AtBeginDocument is defined as {#1}
-
I was rendering plots for a paper where at 300 dpi I got artifacts, so I thought it would be a good idea to make this a user-adjustable variable.
-
Configurable resolution for cairolatex png backend
-
Still broken. $ xelatex --version XeTeX 3.14159265-2.6-0.999991 (TeX Live 2019)
-
$ xelatex --version XeTeX 3.14159265-2.6-0.999991 (TeX Live 2019)
-
I have some more little improvements to gnuplot-lua-tikz-common.tex. You can merge them in the same way as mentioned above if the SourceForge Git server decides to accept my push at some point in the future. Right now it just hangs. So glad I moved PGF/TikZ to GitHub... Just in case, the patch is attached as well.
-
The patch was supposed to fix it and it definitely does for the latest release of PGF. Beyond that, I can't reproduce. I am using the example that OP has posted to the PGF bugtracker (https://github.com/pgf-tikz/pgf/files/3269675/example.zip) and it works with TeX Live 2016, 2017, 2018, and 2019.
-
I have a fix and wanted to submit a merge request but unfortunately SourceForge is complete and utter garbage and decided to entirely screw my forked gnuplot repo. Please merge my fix using these commands: git fetch https://git.code.sf.net/u/hmenke/gnuplot pgfsysdriver git merge FETCH_HEAD In case that doesn't work, I have attached the patch.
-
Merged on GitHub: https://github.com/hmenke/pgf/commit/09ae1df590423be57740fc1cddc9fba75823bdb8
-
Correct bug #523 of pic text displacement in right angle
-
Renamed perspective library macros
-
Added perspective library.
-
This does not touch any internal code and is unlikely to break anything else.
-
Undeclared conditional breaks \pgfmath@@declarefunction
-
Fixed in https://sourceforge.net/p/pgf/git/ci/fd9258d8273d46387438ae9ad442e8d24dcd0e71/ The MWE could have been much shorter: \input pgf.tex \pgfmathdeclarefunction{func}{1}{\ifwhatever\fi} \bye
-
Your reported 15% performance loss is not reproducilbe for me. I tested the following MWE on my machine with LuaTeX 1.10.0 \documentclass[tikz]{standalone} \usetikzlibrary{calc,spy} \begin{document} \foreach \i in {1,...,1000} { \begin{tikzpicture}[x=2cm,y=2cm, spy using outlines={circle, magnification=10, size=2cm, connect spies}] \path (0,0) coordinate (A) (1,2.5) coordinate (B) (4,0) coordinate (C); \draw (A) -- (B) -- (C) -- cycle; \draw [blue, opacity=0.5, very thin] (A) -- ($(B)!(A)!(C)$) (B)...
-
Need a redefinition for \pgfpointnormalised to improve calculation accuracy
-
Fixed in https://sourceforge.net/p/pgf/git/ci/65b8261c63c6f4adfca60106528e2d1bf1e2cb60/
-
[turn] breaks alignment
-
Orthogonal precision
-
[turn] breaks alignment
-
Duplicate of https://sourceforge.net/p/pgf/feature-requests/96/
-
Orthogonal precision
-
Duplicate of https://sourceforge.net/p/pgf/feature-requests/96/
-
Incorrect shading angle
-
tikzmath needs to know about fpu. A simple workaround is to add \usetikzlibrary{fpu} Fixed in https://sourceforge.net/p/pgf/git/ci/f1c7cb0902f4e5bd5cf1ba63b954bd0371bed67b/
-
tikzmath: undefined control sequence \ifpgfmathfloatparseactive
-
That is because Sourceforge is total garbage. For example I don't receive emails anymore from Sourceforge since I messed around with the default settings. I want to migrate PGF to GitHub or GitLab but currently I am waiting for feedback from Till on that. I don't want to be too hasty with that and disregard his opinion (if he ever replies). There is no fixed deadline from my side yet.
-
Fixed in https://sourceforge.net/p/pgf/git/ci/273ae3f82cfeddcff1e2c66798471badfb1acd02/ Thank you for contributing patches, but could you please always put only one statement per line?
-
pgf 3.0.: current page node is disturbed when `\hoffset` is changed
-
name prefix is sort of broken anyway, see https://sourceforge.net/p/pgf/bugs/312/
-
[manual] nondeterministic/deterministic/
-
I decided that I don't care.
-
Typo on user guide
-
Fixed in https://sourceforge.net/p/pgf/git/ci/c58f3e9fdfaa81d8d27ef5be19ec9d48060645e6/
-
[manual] >> is wrongly turned into » (guillemet)
-
Fixed in https://sourceforge.net/p/pgf/git/ci/0075a5e748b5c2b186ebd9578c10702b5d3f1149/ (I hope)
-
Interaction between unbounded coord, stack plot and nan in data
-
I have opened a bug on pgfplots because it's not clear where it belongs. https://sourceforge.net/p/pgfplots/bugs/219/
-
\pgfplots@stacked@diff undefined
-
It was another fuckup of mine. The patch should work now.
-
\graph{(1) -> {(2), (3) -> (2)}}; does not connect nodes 1 and 2
-
Nevermind, it was my mistake. Thank you very much for your efforts!
-
shadings with parameters cannot be redefined
-
Nevermind, it was my mistake.
-
Your patch also broke dvisvgm https://travis-ci.com/pgf-tikz/pgf/jobs/175012402. Can you please fix it?
-
shadings with parameters cannot be redefined
-
Minimal example fails to compile in plain TeX
-
After recieving more complaints from users of ancient technology, I fixed this in https://sourceforge.net/p/pgf/git/ci/4abefd1fbdcbae6b93afd6e1409097787ad189f1/. Keep in mind that everything that relies on \scantokens is bound to fail, such as the babel and quotes libraries.
-
Do I understand it correctly that reverting the “fix” for #362 fixed this bug? Can we close it again?
-
Fixed in https://sourceforge.net/p/pgf/git/ci/350971220aa5f364db825f38060beaaf65a30854/
-
shadings with parameters cannot be redefined
-
As far as I can see this is actually a feature. Shadings are expensive to compute, so when requesting a myshading with the color red, it is cached to avoid reevaluation when using it again later. It seems like redeclaring myshading fails to clear the cache. The issue is kind of exotic though. Not too many users will reuse the same name for different shadings.
-
[manual] issue in pgfpathcircle documentation
-
Fixed in https://sourceforge.net/p/pgf/git/ci/8f94b574b5e61c2ee022bf880a7ac92bd6b5779b/
-
spurious spaces in \pgfmathdeclarefunction
-
Fixed in https://sourceforge.net/p/pgf/git/ci/00f4e8d4154dcb3133ed4a106b6254b8faf874e2/ but it broke gcd. I hope it won't break too much else. As a little gimmick you can get a spaces inside the definition using ~ like in expl3.
-
Minimal example fails to compile in plain TeX
-
What is the error? Where is the link to the Debian bug? For me it works without problems on pdftex, luatex, and xetex. Keep in mind that PGF requires e-TeX.
-
Regression in pgffor
-
Regression in pgffor
-
The offending commit is this one: https://sourceforge.net/p/pgf/git/ci/acdfa1450bd2beda4d6865bb2717e4d6f628c875/
-
Other workaround: Restore the old \foreach behaviour. \def\pgffor@dots@value@process#1{% \expandafter\pgffor@dots@stripcontext#1\pgffor@@stop% \expandafter\pgffor@dots@charcheck\pgffor@dotsvalue\pgffor@@stop% \let#1=\pgffor@dotsvalue% }
-
Regression in pgffor
-
@cfeuersaenger or @tantau would have to do this. I have insufficient privileges. On the other hand I don't see why this is necessary except for aesthetics.
-
Refactor the tags
-
TikZ matrix: most styles do not work with "row sep".
-
tikzpicture and xcolor throw PS errors
-
[graphs] dashes in node names causes weird error message
-
Missing anchor node names for rectangle split horizontal
-
These anchors are not documented. If you need them, feel free to add them and submit a merge request.
-
[intersections] \tikz@intersect@namedpaths persists outside scopes
-
[intersections] \tikz@intersect@namedpaths persists outside scopes
-
Correct bug #285
-
opaque (transparent) PDF pictures with xelatex
-
`on grid' not working proberly for coordinates as reference
-
div/null error by `(270:length)` and a fading line
-
Could you please submit a merge request with the required changes?
-
Option passing in pgfextra
-
This issue does not seems so relevant to me, especially because there is a simple workaround: Just repeat the outside color inside \pgfextra. \documentclass[tikz]{standalone} \begin{document} \begin{tikzpicture} \draw [red] (0,0) -- (1,1) \pgfextra{\pgfinterruptpath \node at (.5,.5) {o}; \endpgfinterruptpath}; \draw [red] (0,.5) -- (1,.5) \pgfextra{\pgfinterruptpath \draw[red] (0,1) -- (1,0); \endpgfinterruptpath}; \end{tikzpicture} \end{document} I'm closing this.
-
tikz transparency problem with background package
-
Nested tikzpictures are not supported. TikZ will now generate a warning if this is detected.
-
[manual] Code snippets (as well as regular text) don't copy properly
-
That is unfixable because different PDF viewer use different heuristics for selecting text. For example with the Evince viewer I can almost perfectly copy-paste the example you quoted, except for color(100bp)=(black)} which the viewer decided is in another column. The Okular viewer copies perfectly, both with rectangle and text selection tool. MuPDF also copies okay but inserts some random newlines. Foxit Reader also copies perfectly. Quintessence: Use a different viewer.
-
If the seed is zero it will be replaced by one. https://sourceforge.net/p/pgf/git/ci/2e264ac824ed77c2439c95f3943289ba5db1247f/
-
[random] can be seeded with 0
-
The background package uses a tikzpicture internally to place the background, so you are effectively nesting tikzpictures which is known to cause problems. Honestly, my solution would be to disallow nesting altogether, which would make your code throw a hard error.
-
[random] can be seeded with 0
-
\graph{(1) -> {(2), (3) -> (2)}}; does not connect nodes 1 and 2
-
Shade does not respect color space
-
Error when loading the library datavisualization when using ConTeXt mkiv (current version from TeXLive 2014 and beta)
-
tikz overlay combined with baseline doesn't work as expected
-
`node contents` key for nodes on a path
-
name prefix is incorrectly set with subpics of pics
-
[graphs] dashes in node names causes weird error message
-
PGF can cause extra space at the end of a document (\pgfutil@everybye)
1 >