Executing commands from the command line that contain spaces

On 08/16/11 15:13, Chuck Huber wrote:

After an exhaustive search through the manual and help files, I'm still

stumped.

 

I'm trying to execute a command that contains a space:

 

     >  eagle -C "run panelize;" myboard.brd

 

Eagle is interpreting the space inside the command as a separator

causing a list of ulp's to be presenting and opening the board

"panelize;.brd".

 

I even tried the example in Help->Command Line Options:

 

    eagle -C "window (1 1) (2 2);" myboard.brd

 

which doesn't work either.  In this case, it opens "(1.brd", again

interpreting the embedded space as a command line separator.  It's as if

eagle is concatenating all of the argv[]'s then parsing them as a single

string, disregarding what the shell has provided.

 

I have also tried single quotes, and backslashes preceding the spaces to

no avail.

 

Eagle 5.11.0

Linux kernel 2.6.37 on x86_64

Bash version: 4.1.10

Works just fine here (also on Linux).

Maybe your shell doesn't handle double quotes correctly?

What does

   echo "a         b"

(several blanks between a and b) give you? Is it

   a         b

or

   a b

Klaus Schmidinger

--

_______________________________________________________________

Klaus Schmidinger                       Phone: +49-8635-6989-10

CadSoft Computer GmbH                   Fax:   +49-8635-6989-40

Pleidolfweg 15                          Email:   kls@cadsoft.de

D-84568 Pleiskirchen, Germany           URL:     www.cadsoft.de

_______________________________________________________________

On 08/16/2011 10:39 AM, Klaus Schmidinger wrote:

On 08/16/11 15:13, Chuck Huber wrote:

>> After an exhaustive search through the manual and help files, I'm still

>> stumped.

>>

>> I'm trying to execute a command that contains a space:

>>

>>      >  eagle -C "run panelize;" myboard.brd

>>

>> Eagle is interpreting the space inside the command as a separator

>> causing a list of ulp's to be presenting and opening the board

>> "panelize;.brd".

>>

>> I even tried the example in Help->Command Line Options:

>>

>>     eagle -C "window (1 1) (2 2);" myboard.brd

>>

>> which doesn't work either.  In this case, it opens "(1.brd", again

>> interpreting the embedded space as a command line separator.  It's as if

>> eagle is concatenating all of the argv[]'s then parsing them as a single

>> string, disregarding what the shell has provided.

>>

>> I have also tried single quotes, and backslashes preceding the spaces to

>> no avail.

>>

>> Eagle 5.11.0

>> Linux kernel 2.6.37 on x86_64

>> Bash version: 4.1.10

 

Works just fine here (also on Linux).

 

Maybe your shell doesn't handle double quotes correctly?

 

What does

 

  echo "a         b"

 

(several blanks between a and b) give you? Is it

 

  a         b

 

or

 

  a b

I get the spaces.  It's the standard Bourne-again shell - "bash" - that

ships with most distributions.  Recall that it doesn't work with single

quotes, nor with escaped spaces.

...

I found it.  /usr/local/bin/eagle is a shell script that launches eagle

from it's installed tree.  It's the first "eagle" in $PATH and amounts to:

    exec /opt/eagle-5.11.0/bin/eagle $*

It should be:

    exec /opt/eagle-5.11.0/bin/eagle "$@"

Maybe this revelation, found buried deep within the man pages, will help

someone else.

Enjoy,

    - Chuck