The Eternal Eclipse Mac OS

Posted on  by

I was struggling for days getting it to work with Eclipse on Mac OS X 10.12.6. My first approach was to use Maven to install JInput. The excellent M2Eclipse plugin provides good support for Maven. Unfortunately, the pre-configured Maven Repository does not include JInput.

  1. Sometimes it happen that we have to change or add the JDK/JRE version used by eclipse and/or we want to access the correct source code of the JDK. Here the step by step procedure under OS X: Open File - Preferences; Search for the Installed JRE (currently the 1.8.073) and click ‘Add’ 3. Select the JRE Home.
  2. Using OpenCL with Eclipse on Mac OS Posted on December 7, 2012 by Bharath Kumar It’s very easy to execute an openCL code in Mac, by simply using the flag ‘-framework OpenCL’ during compilation.
  3. Eclipse Equinox is an implementation of the OSGi core framework specification. Eclipse Concierge is a small footprint implementation of the OSGi specification. Enabling modular business apps for desktop, browser and mobile.
Home » Eclipse Projects » Eclipse Platform » [MAC OS X] Unable to open external editor
Show:Today's Messages::Show Polls::Message Navigator
[MAC OS X] Unable to open external editor[message #277107]Sat, 04 December 2004 17:50
Eclipse User
Originally posted by: wd.zygno.org
Mac OS X 10.3.6 with Java 1.4.2 and Eclipse 3.0.
When I associate a file type with an external editor and attempt to
open a file with the external editor (right click->open with), I get
this error message:
Unable to open external editor /Applications/jEdit 4.2/jEdit.app
(/Applications/jEdit 4.2/jEdit.app).
Reason:
Error opening external editor (/Applications/jEdit 4.2/jEdit.app).
This occurs with both jEdit and TextEdit.
Is this a known problem on Mac?
Can anyone suggest a workaround or diagnostic?
thanks to all --
-- bill
Re: [MAC OS X] Unable to open external editor[message #277125 is a reply to message #277107]Sun, 05 December 2004 16:15
David Rocks
Messages: 23
Registered: July 2009
The runtime(exec) method used to call pgms from within eclipse
doesn't use the 'launch' interface and therefore can't call the
application bundle (..app) under OS X. You have to provide the full path
to the executable. In your case /Applications/jEdit
4.2/jEdit.app/Contents/MacOS/JavaApplicationStub.
This has consequences for some applications if they are already running
on your desktop. It will always try to start a new instance, which some
apps will refuse to do if they are already running. It may also cause
problems if you are passing parameters. Some apps, like IE, expect file
paths in 'classic' style: Volume:Path, which eclipse doesn't seem to
support. Good luck.
Bill Mulert wrote:
> Mac OS X 10.3.6 with Java 1.4.2 and Eclipse 3.0.
>
> When I associate a file type with an external editor and attempt to open
> a file with the external editor (right click->open with), I get this
> error message:
>
> Unable to open external editor /Applications/jEdit 4.2/jEdit.app
> (/Applications/jEdit 4.2/jEdit.app).
> Reason:
> Error opening external editor (/Applications/jEdit 4.2/jEdit.app).
>
> This occurs with both jEdit and TextEdit.
>
> Is this a known problem on Mac?
> Can anyone suggest a workaround or diagnostic?
>
> thanks to all --
> -- bill
>
>
Previous Topic:Float look for Forms Widgets
Next Topic:Variables not resolved when watched
Goto Forum:
[ Syndicate this forum (XML) ] [ ]

Powered by FUDForum. Page generated in 0.02663 seconds

Configuring Eclipse on a Mac

Posted by David Chandler on July 8, 2010

The Eternal Eclipse Mac Os Download

I’m attempting to make the switch from Windows to Mac courtesy of my new employer (I’m pleased to be working with the GWT team at Google). While I very much like my shiny new MacBook Pro, I simply don’t get all the Mac hype. The biggest problem has been that I’m a keyboard person, and Macs are for mouse people. Most Windows keyboard shortcuts have Mac equivalents, but they’re just different enough to make for a bit of a learning curve, like Ctrl+arrows instead of Home and End. Thankfully, many keys can be remapped via System Preferences, but I haven’t found a way to map the editing keys yet (anyone?). My biggest annoyance is that holding down the Alt key doesn’t bring up menu shortcuts as on Windows. That makes going to Run External Tools a real pain in Eclipse. Alt+R, E becomes Ctrl+F2,R,R,down arrow,E. Runner up annoyance is that there’s no way to use the keyboard to click “No” in a confirmation dialog.

At any rate, here are a few notes for other Eclipse users making the switch from Windows to Mac.

The first thing is to make the fonts readable. This is not necessarily a Mac thing, but the system font does seem especially small. In Eclipse preferences (Command+comma in most apps on the Mac–nice), I bumped up the font size (General Appearance Colors and Fonts Basic Text Font). This increases it for the Console window, but some plug-ins seem to use the system font instead, which leaves these “over the hill” eyes squinting at logs. Which, in turn, brings us to an almost-unbelievable discovery: you can’t change the system font on a latest, greatest Mac (OS X 10.6.3)! Problem still unsolved.

Eclipse

Now, time to move over my Eclipse external tools configurations from Windows. The external tools config to launch Finder in the selected project directory is very cool, but far from obvious. In the Run External Tools Configuration… dialog, enter the following information:

The Eternal Eclipse Mac Os Catalina

Location: /usr/bin/open
Working Directory: ${project_loc}
Arguments: .

This corresponds to typing “open .” in a Terminal window, which launches Finder in the current directory. Now if I could just configure a shortcut key to launch Terminal so I don’t have to click the icon in the dock every time… See Finder toolbar button to open Terminal to go the other way.

You can also create an external tool to launch Terminal in the selected project directory. Well, almost. To launch Terminal, you have to key into the Location field the full path /Applications/Utilities/Terminal.app/Contents/MacOS/Terminal; however, it always opens in your home directory, even if you set Working Directory to the ${project_loc} variable. That defeats the purpose of this particular tool launcher. Fortunately, xterm is a little smarter, so the following settings work:

Location: /usr/X11/bin/xterm
Working Directory: ${project_loc}
Arguments: (none)

Unfortunately, the default xterm font is miniscule.

The Eternal Eclipse Mac Os Update

Fortunately, you can put the following lines in ~/.Xdefaults to increase the default font size:

XTerm*font: *-fixed-*-*-*-20-*
XTerm*boldFont: *-fixed-*-*-*-20-*

Eclipse Download For Mac

Now we’ve replicated the command prompt external tool from Windows Eclipse, but unfortunately, it’s a pain to get to the Run External Tools menu via the keyboard. So we might as well punt and make it even easier with the mouse. thanks to this nifty open source plug-in for Eclipse. Once you’ve installed the plug-in, simply right-click on a project and select “Open in Terminal” to open a new xterm. Someone should contribute “Open in Finder” to that project, too.

Most keyboard shortcuts on Windows map directly to the map in the standard way; that is, you press the Command (Apple) key on the Mac instead of Ctrl on the PC. One notable exception is Ctrl+Space, which is identical on the Mac. Command+Space would be more consistent; however, this brings up the Spotlight search tool on the Mac. Since I’d rather have Ctrl+Space work in Eclipse where my muscle memory is expecting it, I swapped these keystrokes in Eclipse Preferences and Mac System Preferences. Another alternative is to disable Spotlight in favor of Google Quick Search Box.

Eclipse on Mac tricks welcome in the comments. No flames, please.