| bio | website | |
|---|---|---|
| location | ||
| age | ||
| visits | member for | 1 year, 4 months |
| seen | 53 mins ago | |
| stats | profile views | 89 |
|
2d |
comment |
Calculate prices In this case, most or all of the packages besides pythontex could be removed, depending on what is wanted. The packages at the beginning are engine-specific, in case a document needs to work under multiple engines while supporting UTF-8, while the others are document-specific. This would be a good problem for Python's decimal module, or perhaps a currency-specific library. |
|
May 17 |
comment |
PythonTeX texing problem Is this the newfloat you downloaded? There are some other files called newfloat.sty out there, but the one on CTAN is the one you want. |
|
May 15 |
comment |
Pythontex workflow with LyX The three-step compile process is very similar to that of SageTeX, so you might use the LyX SageTeX module as a starting point. I imagine it might require only a few modifications. |
|
May 8 |
answered | Non-raised tildes in a minted environment |
|
May 7 |
comment |
How to print the permutation of {s,u,v,a,t} with LaTeX? This could also be done with pythontex, if the calculations were ever slow enough that caching would be useful. |
|
May 7 |
comment |
Error when using minted package and -output-directory option Related: tex.stackexchange.com/questions/102308/… |
|
May 3 |
awarded | Nice Answer |
|
May 2 |
comment |
How can I define a new minted environment with optional arguments? I like this approach, but it's giving me errors when no optional argument is supplied. |
|
May 2 |
answered | How can I define a new minted environment with optional arguments? |
|
Apr 30 |
awarded | Necromancer |
|
Apr 14 |
comment |
Error using Minted for syntax highlighting in custom document classminted loads xcolor, so it may be a conflict between the two color packages. |
|
Apr 10 |
answered | \newcommand with PythonTeX PyCode |
|
Apr 8 |
revised |
minted vs. texments vs. verbments Added note on maintenance of minted |
|
Apr 8 |
comment |
Highlighting a Chunk of Code within a lstlisting by specifying the line number It will be at github.com/gpoore/minted. The issue tracking is still at code.google.com/p/minted for the moment, but I'll probably transition that to GitHub as well. |
|
Apr 4 |
comment |
PythonTeX rendering problem DJP is correct; PythonTeX's operation uses the same principle as SageTeX. You have to run LaTeX (this saves all the Python code in an auxiliary file), then run the PythonTeX script (pythontex2.py or pythontex3.py, depending on your Python version), and finally run LaTeX again (which brings in the output of the script). There are question marks/placeholders for any code output that is expected but not yet available, with corresponding warnings. |
|
Mar 31 |
revised |
Naming conventions for macro names that include the package name Clarified interest in user macros |
|
Mar 31 |
revised |
Naming conventions for macro names that include the package name Improved clarity |
|
Mar 31 |
asked | Naming conventions for macro names that include the package name |
|
Mar 31 |
comment |
Highlighting a Chunk of Code within a lstlisting by specifying the line number Maybe we can get several people working on minted. |
|
Mar 31 |
comment |
Highlighting a Chunk of Code within a lstlisting by specifying the line number Don't count minted out just yet. I've been communicating with Konrad Rudolph since learning that minted is no longer maintained, and am planning to maintain minted in the future. |