Re: long options vs unix

From: Dave Page <dpage(at)pgadmin(dot)org>
To: Magnus Hagander <magnus(at)hagander(dot)net>
Cc: pgadmin-hackers <pgadmin-hackers(at)postgresql(dot)org>
Subject: Re: long options vs unix
Date: 2009-03-17 14:13:01
Message-ID: 937d27e10903170713m3feeacc0o4c93b6d6195f90e9@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgadmin-hackers

On Tue, Mar 17, 2009 at 1:10 PM, Magnus Hagander <magnus(at)hagander(dot)net> wrote:
> The change to using long options for pg_dump and friends seem to have
> broken it, at least on linux. But I assume it still worked on at least
> osx *or* windows, since that's where Dave would've tested it :-)
>
> It would more or less never work, since it tried to put a double-quote
> in the actual filename *before* the / specifying the root directory..
>
> Here's a patch that removes the = sign after the parameter names. That
> makes it work on linux again. I would appreciate it if somebody can test
> this patch on windows and/or osx as well to confirm it doesn't break
> things there.

thanks - applied. Tested on Windows & Mac.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com

In response to

Browse pgadmin-hackers by date

  From Date Subject
Next Message Raymond O'Donnell 2009-03-17 15:28:43 PgAdmin 1.10 beta 1 - scratch pad won't go away
Previous Message Guillaume Lelarge 2009-03-17 14:10:43 Re: pgAdminIII 1.10 Visual Tour