Open file from command line in linux

On 03/03/2010 11:49 AM, Thomas Lundgaard wrote:

Hi.

 

I'd like to get a list of what command line parameters

eagle can be run with on linux.

I'm looking for a way to open a (schematic) file from the

command line (so that i can create a .desktop file to

open eagle files).

Not sure about schematics specifically, but

    shell> eagle eagle.epf

works at the project level.  I have also added a file association in

Konqueror to associate .epf files with eagle.  So a single-click in

Konqueror (or any other file browser) will launch eagle.

Enjoy,

    - Chuck

Chuck Huber wrote:

Not sure about schematics specifically, but

 

    shell> eagle eagle.epf

 

works at the project level.  I have also added a file

association in

Konqueror to associate .epf files with eagle.  So a

single-click in

Konqueror (or any other file browser) will launch

eagle.

That doesn't works for schematics files. If I run

     sheel> eagle document.sch

eagle will start and first complain that the directory

document.sch doesn't exists (oviously, it's a file) and

then sets the library directory in Options >

Directories to /home/user/path/to/document.sch. I

really consider this weird behaviour, don't know if

it's a bug?

I'm using eagle 5.7.0 on Archlinux.

Cheers..

On 03/03/2010 06:00 PM, Thomas Lundgaard wrote:

Chuck Huber wrote:

Not sure about schematics specifically, but

 

    shell> eagle eagle.epf

 

works at the project level.  I have also added a file

association in

Konqueror to associate .epf files with eagle.  So a

single-click in

Konqueror (or any other file browser) will launch

eagle.

 

That doesn't works for schematics files. If I run

     sheel> eagle document.sch

eagle will start and first complain that the directory

document.sch doesn't exists (oviously, it's a file) and

then sets the library directory in Options >

Directories to /home/user/path/to/document.sch. I

really consider this weird behaviour, don't know if

it's a bug?

 

I'm using eagle 5.7.0 on Archlinux.

Good morning,

That is odd behavior.  I did a little experimenting this morning and

found that I could supply eagle with any .sch .epf .brd or .lbr, and it

starts without complaint.  The elements in Options->Directories did not

change.

Furthermore, I can:

    shell> eagle 513941.sch 513951.brd

and I get a control panel, a schematic editor, and a layout editor windows.

I, too, am using 5.7.0.  I'm running opensuse 11.1, KDE4 window manager.

"uname -a" shows

Linux lightning 2.6.27.45-0.1-default #1 SMP 2010-02-22 16:49:47 +0100

x86_64 x86_64 x86_64 GNU/Linux

This is a fairly new kernel - I installed it two days ago, but I doubt

that has anything to do with the behavior exhibited by your installation.

I'm not sure if this provides any useful information.

Enjoy,

    - Chuck

Thomas Lundgaard wrote on Wed, 03 March 2010 18:00

That doesn't works for schematics files. If I run

     sheel> eagle document.sch

eagle will start and first complain that the directory

document.sch doesn't exists (oviously, it's a file) and

then sets the library directory in Options >

Directories to /home/user/path/to/document.sch.

I just tried it on Windows 2000 and it seems to work correctly.  Of course

then it doesn't open Eagle thru the Windows menu shortcut, so it picks a

arbitrary window size and position for the control panel whereas it's

opened maximized when I run it from the menu or my special CTRL-ALT-C

hotkey for Eagle.

Personally I run eagle with by using the aforementioned hot key, then use

the TAB, arrows, and ENTER keys to navigate thru the control panel and open

the schematic, library, or board that I want to work with.

--

Browser access to CadSoft Support Forums at http://www.eaglecentral.ca

Hi All,

Thanks for your help so far.

I found the issue now. I'm running archlinux and for some reason the eagle

package in AUR installs an eagle executable in both /usr/bin/eagle and

/opt/eagle-5.7.0/bin/eagle. If i run

/usr/bin/eagle file.sch

it does the aforementioned weired behaviour, but if i run:

/opt/eagle-5.7.0/bin/eagle file.sch

it opens the schematic as it's supposed to.

I guess it's some sort of packaging issue, so I'll post it in the AUR

comments.

Cheers, Thomas

On Mon, 8 Mar 2010, Thomas Lundgaard wrote to us saying :

I found the issue now. I'm running archlinux and for some reason the eagle

package in AUR installs an eagle executable in both /usr/bin/eagle and

/opt/eagle-5.7.0/bin/eagle. If i run

/usr/bin/eagle file.sch

it does the aforementioned weired behaviour, but if i run:

/opt/eagle-5.7.0/bin/eagle file.sch

it opens the schematic as it's supposed to.

I guess it's some sort of packaging issue, so I'll post it in the AUR

comments.

Check exactly what /usr/bin/eagle is. On my Gentoo box with an official

CadSoft CD install of 4.15 there are also two executable paths. However,

/usr/bin/eagle is merely a symbolic link to /opt/eagle/bin/eagle. I

don't have the box with v5 running right now to see if that's the same.

--

Rob Pearce                       http://www.bdt-home.demon.co.uk

The contents of this | Windows NT crashed.

message are purely   | I am the Blue Screen of Death.

my opinion. Don't    | No one hears your screams.

believe a word.      |

On 03/09/2010 02:40 PM, Robert Pearce wrote:

On Mon, 8 Mar 2010, Thomas Lundgaard wrote to us saying :

I found the issue now. I'm running archlinux and for some reason the

eagle

package in AUR installs an eagle executable in both /usr/bin/eagle and

/opt/eagle-5.7.0/bin/eagle. If i run

/usr/bin/eagle file.sch

it does the aforementioned weired behaviour, but if i run:

/opt/eagle-5.7.0/bin/eagle file.sch

it opens the schematic as it's supposed to.

I guess it's some sort of packaging issue, so I'll post it in the AUR

comments.

 

Check exactly what /usr/bin/eagle is. On my Gentoo box with an official

CadSoft CD install of 4.15 there are also two executable paths. However,

/usr/bin/eagle is merely a symbolic link to /opt/eagle/bin/eagle. I

don't have the box with v5 running right now to see if that's the same.

If I remember correctly, in Arch, it's a script that sets up some

environment variables and creates your .eagle directory if it doesn't

exist.  It probably doesn't pass its own command-line parameters to the

final executable.

-Dave