However, *every* time I try this in Galeon, I also get an error dialog as the file is opened:
"FATAL ERROR: [Errno 2] No such file or directory: '/tmp/<name_of_file>'"
Well, this means that the path to the temp file that Galeon is passing to ExternalEditor is bogus.
You would think so, but an appropriate temp file is indeed created in /tmp. This is why the error message is so perplexing.
This does not affect my ability to edit and save changes to the file,
Yeah, but it means External Editor has bailed, so changes won't get saved to Zope, unless perhaps EE is getting spawned twice or something... Don't know how that could happen.
Well, External Editor has NOT bailed. As I noted above, a temp file is created. AND my edits are indeed saved back into Zope. Everything works fine, but the error message appears nonetheless.
What is your helper app command line in Galeon?
I have the application/x-zope-edit MIME type mapped to /home/damon/bin/python/zopeedit.py. Same as in Mozilla and Opera.
How is it different from the Red Hat box?
It isn't. In fact, before launching Galeon on FreeBSD, I simply copied over the ~/.galeon directory from my Red Had drive, whole cloth, to ~ on my FreeBSD drive. Other than this one single glitch with External Editor and Zope, everything works on FreeBSD/Galeon as it used to under Red Hat/Galeon.
Is the Galeon version different or anything else of note?
Same version exactly. Grrr. --Damon On Fri, 2002-11-22 at 14:51, Casey Duncan wrote:
On Friday 22 November 2002 03:16 pm, Damon Butler wrote:
So, I'm running FreeBSD 4.7, connecting to the management interface of a Zope server through the Galeon 1.2.6, Mozilla 1.1, and Opera 6.1 browsers. I've installed the External Editor script on my system, and have no trouble clicking the External Editor icon next to the file in Zope I wish to edit and have it open in gvim.
However, *every* time I try this in Galeon, I also get an error dialog as the file is opened:
"FATAL ERROR: [Errno 2] No such file or directory: '/tmp/<name_of_file>'"
Well, this means that the path to the temp file that Galeon is passing to ExternalEditor is bogus.
This does not affect my ability to edit and save changes to the file,
Yeah, but it means External Editor has bailed, so changes won't get saved to Zope, unless perhaps EE is getting spawned twice or something... Don't know how that could happen.
but it happens Each And Every Time. Very annoying, especially since it DOESN'T happen with Mozilla or Opera. (I should also add that until this week I was using the exact same browsers on Red Hat 8.0, and never got this error message with any of them; not even Galeon.)
Yes, others have reported success with Galeon, and I know of no problem specific to it for EE.
Does anybody know what the heck is happening here? I would like this annoyance to go away, as Galeon is my favorite browser by a mile.
What is your helper app command line in Galeon? How is it different from the Red Hat box? Is the Galeon version different or anything else of note?
-Casey