public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Paul <Paul.Domaskis@gmail.com>
To: cygwin@cygwin.com
Subject: pdfnup ignores ~/.pdfjam.conf
Date: Wed, 03 Dec 2014 23:01:00 -0000	[thread overview]
Message-ID: <loom.20141204T000104-319@post.gmane.org> (raw)

I'm using pdfjam that comes with 64-bit cygwin's
texlive-collection-binextra package, dated 29 May 2013.  I have the
following in my ~/.pdfjam.conf: 

   paper='letterpaper' 
   nup='1x2' 
   landscape='landscape' 
   frame='true' 

I invoke pdfjam using 

   pdfnup filename.pdf 

and the messages show that the ~/.pdfjam.conf is being read, as are 
the switches therein. 

  pdfjam: This is pdfjam version 2.08. 
  pdfjam: Reading any site-wide or user-specific defaults... 
              ## 
              ## From /home/User.Name/.pdfjam.conf: 
              ## 
              paper='letterpaper' 
              nup='1x2' 
              landscape='landscape' 
              frame='true' 
  pdfjam: Effective call for this run of pdfjam: 
          /bin/pdfjam --suffix nup --nup '2x1'
             --landscape -- filename.pdf - 
  pdfjam: Calling pdflatex... 
  pdfjam: Finished.  Output was to
             '/home/User.Name/tmp/filename-nup.pdf'. 

The "Effective call" above shows that ~/.pdfjam.conf is being ignored, 
even though the switch settings are being read.  The output confirms 
this.  However, if I specify the switch settings in the pdfnup 
statement itself, they are accepted. 

What am I doing wrong in setting up ~/.pdfjam.conf? 

If all is correct, does anyone else see this problem? 

P.S. In a corporate environment, updating packages is problematic. 


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

             reply	other threads:[~2014-12-03 23:01 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-03 23:01 Paul [this message]
2014-12-04 12:31 ` Ken Brown
2014-12-04 16:05   ` Paul
2014-12-04 16:15     ` Paul

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=loom.20141204T000104-319@post.gmane.org \
    --to=paul.domaskis@gmail.com \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).