[pstricks] Including Private Header Files Stopped Working

[Hensh, Richard]

Dear Herbert,

Thanks. Your last suggestion works, but I want to be clear. 

For the past 9 years the following lines added (or uncommented) from my local copy of pstricks.con allowed automatic inclusion of private header files. (I believe the included comments are by tvz or dg, but that's just a guess.)

\pstricks.con:
...
%%%%%%%%%%%%%%%%%%% !! CUSTOMIZATION STUFF GOES HERE: !! %%%%%%%%%%%%%%%%%%
%% If you want to include your own customizations to pstricks.tex, then
%% uncomment the \pstcustomize command, and include your modifications
%% after \pstcustomize. These will be read in after pstricks.tex.
\pstcustomize
\pstheader{mypstrix.pro}
\endinput
...

The above code worked with versions of pstricks.tex < 2.44. I am not saying that it should have worked, but it did.

Since version 2.45 the above code no longer works. So, per your suggestions, I've made the following changes.

\pstricks.con:
...
%%%%%%%%%%%%%%%%%%% !! CUSTOMIZATION STUFF GOES HERE: !! %%%%%%%%%%%%%%%%%%
%% If you want to include your own customizations to pstricks.tex, then
%% uncomment the \pstcustomize command, and include your modifications
%% after \pstcustomize. These will be read in after pstricks.tex.
\def\pstcustomize{}
\pstheader{mypstrix.pro}
\endinput
...

Now my private header files are imported in the final postscript document, as desired.

Perhaps the comments in the file dvips.cfg (dvips.con) that ships with most TeX distributions should be modified to reflect this change.

thanks again,
rick


________________________________________
From: PSTricks [pstricks-bounces at tug.org] on behalf of Herbert Voss [Herbert.Voss at FU-Berlin.DE]
Sent: Tuesday, August 20, 2013 7:40 AM
To: pstricks at tug.org
Subject: Re: [pstricks] Including Private Header Files Stopped Working

Am 20.08.2013 12:29, schrieb Hensh, Richard:

> I believe that I have confirmed that pstricks.tex (ver 2.45 - 2013/07/09) is somehow causing the problem. The versions posted on the pstricks web site and the version distributed with MikTeX match exactly. Here are a few more details.
>
> 1. If I comment out the pst macro \pstcustomize in pstricks.con, then everything works as it did before using pstricks.tex (v2.45).
>
> pstricks.con:
>    %\pstcustomize
>    \pstheader{mypstrix.pro}

Rich,
\pstcustomize is set to \endinput if it is not defined by the user
_before_ loading pstricks. If you uncomment it then \pstheader will not
be read.

> So perhaps \pstcustomize has somehow been modified in a recent version of pstrick.tex. To confirm this I tried
> the following.
>
> 2. If I replace pstricks.tex (ver 2.45 - 2013/07/09) with version 2.43 (2013/05/12) then the following works as it did before.
>
> pstricks.con:
>    \pstcustomize
>    \pstheader{mypstrix.pro}

this will work if you have something like

\def\pstcustomize{}
\usepackage{pstricks}
...

Herbert
_______________________________________________
PSTricks mailing list
PSTricks at tug.org
http://tug.org/mailman/listinfo/pstricks
archive: http://www.tug.org/pipermail/pstricks/