Help talk:External editors: Difference between revisions

From Meta, a Wikimedia project coordination wiki
Content deleted Content added
No edit summary
m Protected "Help talk:External editors": Excessive spamming (‎[edit=autoconfirmed] (indefinite) ‎[move=autoconfirmed] (indefinite))
 
(134 intermediate revisions by 98 users not shown)
Line 1: Line 1:
{{MovedToMediaWiki|Manual talk:External editors}}
'''Bold text'''
----
[[Image:Example.jpg]][[Image:Example.jpg]][[Image:Example.jpg]]<math>Insert formula here</math>This seems so great. I wish there were simply a link like '''how to install this in windows xp + gimp or photoshop: download this file and run''' but this ain´t so much user friendly is it? --[[en:user:avsa|alexandre van de sande]]

: No - it's a reference implementation; I'm hoping someone from the Windows world writes a pretty, super-easy implementation at some point. To use this one, you'll have to follow the installation instructions [http://cvs.sourceforge.net/viewcvs.py/*checkout*/wikipedia/extensions/ee/INSTALL here].--[[User:Eloquence|Eloquence]] 02:14, 18 July 2005 (UTC)

Anyone gotten this working in OS X 10.4? If so, how? ;D --[[en:user:ericg|ericg]]

Until someone writes the nice easy to use Windows version, would a perlcc compilation work? I guess the resulting executable might be pretty large. [[en:user:Zeimusu|Zeimusu]]
<pre>
Xlib: unexpected async reply (sequence 0x4f)!
Xlib: unexpected async reply (sequence 0x50)!
Xlib: unexpected async reply (sequence 0xc7)!
Xlib: unexpected async reply (sequence 0xc8)!
Xlib: unexpected async reply (sequence 0xc9)!
Xlib: unexpected async reply (sequence 0xca)!
Xlib: unexpected async reply (sequence 0xcb)!
The program 'ee.pl' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadAtom (invalid Atom parameter)'.
(Details: serial 205 error_code 5 request_code 18 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)
</pre>

Latest revision as of 11:45, 7 April 2012