918 reputation
793256
bio website pstricks.net/pstricks/…
location sandwiched in your smelly armpit
age 13
visits member for 2 years, 10 months
seen 5 mins ago

Stop visiting except for voting!

here

I'm just a single point on a complex plane. I'm not the strongest species that survives, nor the most intelligent, but the one most responsive to change. I always feel restless despite being in the safe zone. You can't teach me anything, but you can stimulate me to think! I am a detail-oriented analyst and interested in almost everything. Consistency, optimization, best-practice, & perfection are always my first priority in mind! Therefore by my questions & answers you'll fully recognize me. I can tell you more but then I have to kill you.

I distribute my rep in bounties as spending money for my & your pleasure is more meaningful than saving money in a bank & abandoning it unused.

"If you're an underdog, mentally disabled, physically disabled, if you don't fit in, if you're not as pretty as the others, you can still be a hero, read TEXBook!"

"Motivation isn't enough. If you've an idiot & you motivate him, now you've a motivated idiot."

Learning (La)TeX, PSTricks, & PGF/TikZ is similar to learning how to swim or drive a car. You don’t get the full benefit by watching someone else do it. Your own fingers must get involved.

Don't be lukewarm! If you cannot be the best, be the worst!

Beauty without intelligence is a masterpiece painted on a toilet paper.

For every problem, there is always a solution that is simple, neat, but wrong.

Best practices

  1. Use pdflatex \input{filename} instead of pdflatex filename.
  2. Don't specify the file extension in \includegraphics.
  3. Divide your project into a main & smaller input files & compile the main with pdflatex.
  4. Put each code snippet 4 either drawing a diagram or making a table into a standalone input file & compile it to produce a PDF.
  5. Define global macros 4 often-used materials, put them into a separate package thereby changing the macros in one place will effect the whole document.
  6. Remove unnecessary packages.
  7. Don't mix different series, families, font size, & shapes, ESPECIALLY IN ONE SENTENCE.
  8. Obey.

Clipboard


Feb
13
suggested suggested edit on Rationale to use \input{filename} on the pdflatex command line?
Feb
13
revised How to invoke \write18{pdflatex “\def\param{…}\input{filename}”}?
deleted 1182 characters in body; edited title
Feb
13
accepted How to invoke \write18{pdflatex “\def\param{…}\input{filename}”}?
Feb
13
revised How to invoke \write18{pdflatex “\def\param{…}\input{filename}”}?
added 1733 characters in body
Feb
13
asked How to invoke \write18{pdflatex “\def\param{…}\input{filename}”}?
Feb
12
revised How to overlay graphs using includegraphics or pstricks?
added 728 characters in body
Feb
12
revised How to overlay graphs using includegraphics or pstricks?
added 1248 characters in body
Feb
12
answered How to overlay graphs using includegraphics or pstricks?
Feb
12
comment Why does \psPrintValue not allow 2 \rput to work at the same time?
@Herbert: I have tested it and the problem disappeared.
Feb
12
revised Why does \psPrintValue not allow 2 \rput to work at the same time?
rolled back to a previous revision
Feb
12
answered Why does \psPrintValue not allow 2 \rput to work at the same time?
Feb
12
revised Why does \psPrintValue not allow 2 \rput to work at the same time?
added 6372 characters in body
Feb
12
revised How to randomly shuffle a sliced image?
Removing unnecessary \relax.
Feb
12
accepted What is lacking in my geometric calculation below?
Feb
12
comment What is lacking in my geometric calculation below?
@A.Ellett: The behaviour of \rput is mysteriously implemented.
Feb
12
comment What is lacking in my geometric calculation below?
@A.Ellett: There is no documentation. I got it by a trial and error approach.
Feb
12
asked What is lacking in my geometric calculation below?
Feb
12
comment How to mimic the behavior of \ncput* but without the unwanted opaque effect?
Oh my ghost! There are 14 revisions. :-)
Feb
11
comment How to mimic the behavior of \ncput* but without the unwanted opaque effect?
@A.Ellett: For a straight connecting curve, I have the solution here.
Feb
11
comment How to mimic the behavior of \ncput* but without the unwanted opaque effect?
@A.Ellett: But the opaque box is what I don't want to get. Converting the PDF to PNG produces a bad result.