GoogleCodeArchives / editra

Automatically exported from code.google.com/p/editra
Other
0 stars 0 forks source link

Add local file opening support from the command line #435

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
While editra is already opening, start the program from the terminal, e.g.
Editra.app/Contents/MacOS/editra, and pass it a relative filename.

What is the expected output? What do you see instead?
Editra should open the file I specified. Instead it opens a new file inside
Editra.app/Contents/... with that name.

IMPORTANT!!! Please answer these questions for any and ALL bug reports

What version of the product are you using? On what operating system?
0.5.15, Mac OS 10.5.8

Original issue reported on code.google.com by revcompg...@gmail.com on 3 Dec 2009 at 5:24

GoogleCodeExporter commented 9 years ago
Hi,

I think I may have fixed this already last week sometime will double check 
later.

For this kind of usage I suggest copying this script from the applet to 
someplace on
your path to launch editra from the command line

/Applications/Editra.app/Contents/Resources/editramac.sh

(It can be renamed to whatever you like)

Cody

Original comment by CodyPrec...@gmail.com on 3 Dec 2009 at 5:55

GoogleCodeExporter commented 9 years ago
Fixed

* resolve absolute path prior to sending ipc call to other running instance

Original comment by CodyPrec...@gmail.com on 10 Dec 2009 at 2:50