This happens until I right-click and open the file once by selecting "Open with > Text editor". Subsequent double-clicks on that PHP file will open in the same Aptana instance. Any ideas about how to fix this?
Which version of Aptana Studio are you using?
In Studio 2, there is no default PHP plugin installed, so there is no PHP editor, and until you install the PDT plugin, you will get the above behavior.
In Studio 3, there is a default PHP plugin, so a double-click on a file should open it in the PHP editor.
As pointed out above, once you explicitly pick an editor for a file, it will continue to open in that editor. You can set up file associations here:
http://wiki.appcelerator.org/display/tis/Changing+your+file+association+preferences
Since this is still seems to be a bug in Aptana, this thread:
https://aptanastudio.tenderapp.com/discussions/problems/3707-aptana-opens-a-new-instance-when-i-click-on-a-file
led me to here:
https://jira.appcelerator.org/browse/APSTUD-23?focusedCommentId=151446&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-151446
Which fixed the issue on multiple computers (with fresh installs) for me.
Related
I'm using this version of Eclipse
Version: Mars.2 Release (4.5.2)
Build id: 20160218-0600
on Mac Sierra. I just installed MacVim and now whenever I try and open a JSP file within Eclipse (using Shift ⇧+Command ⌘+R for example), the file is getting opened in MacVim instead of the Eclipse editor. I went to
General -> Editors -> File Assocations
and added "*.jsp", but even after restarting Eclipse, the JSP files still open in MacVim instead of the Eclipse editor.
How can I force my .jsp files to open in the Eclipse editor?
Generally, what you've done it's the right way.
You may have to select the right default to make it work:
Then you can check if the associated editors appear on file open submenu:
As you can see, JBoss Tools JSP Editor is highlighted to represent the default.
If these steps aren't working in your environment, there's probably a sort of settings corruption (experienced very often).
What you can try:
run eclipse -clean -refresh
create a brand new Workspace
make a new and clean eclipse installation
Make sure you have Eclipse WTP installed (or just install it):
P.S. use the update-site for your eclipse version (Mars), I'm on Neon.
I routinely download the latest 'Eclipse IDE for Java EE Developers' and add Aptana Studio to it. I recently did this with Juno 4.2.2 and Aptana Studio 3.4.0. Now, I find that in the html or css editors, the cmd-f key still brings up the find/replace bar once. But when I ESCape out of that find bar, the cmd-f command no longer works until I switch to another editor window and then return to the first one. Then, cmd-f works, but again only one more time. The 'Edit-->Find/Replace menu item works consistently', so I think it has something to do with key bindings.
I also tried downloading the standalone Aptana Studio 3.4.0 and it doesn't have this issue.
Never had this problem before. Any ideas?
Me too. Its super annoying since I use Aptana all day.
Workaround: You can work around it by disabling the Aptana Find Bar in Preferences and restart Eclipse (this means you have to use the default Eclipse search dialog). Just move it out of the way while you're searching. If you disable it and go back to the old Eclipse search, you also get the ability to use the keyboard shortcuts for the items under the "Commands" menu.
Here's an aptana ticket for this bug: https://jira.appcelerator.org/browse/APSTUD-7850
I just added JBoss tools and I like a lot of what I get from it. However, I noticed that my .xhtml files are loading a /lot/ slower (on the order of several seconds) than before I installed JBoss tools. I'm willing to accept some slowdown (there's always overhead from using tooling sitting ontop of Eclipse) but this is a pretty long wait. I suspect it has to do with the visual editor that JBoss has added for .xhtml. I am using windows 64 bit and I can't use this editor. I've also tried following the advice at this link
http://docs.jboss.org/tools/whatsnew/vpe/vpe-news-3.3.0.M2.html
and adding -Dorg.jboss.tools.vpe.loadxulrunner=false to the eclipse.ini but I didn't notice any speedups. I also uninstalled the plugin for the JBoss visual editor and didn't see any results. After uninstalling the plugin the visual/source, source, and preview tabs are still at the bottom of the .xhtml editor, so maybe I uninstalled the wrong one?
I'm using Eclipse for Java EE Juno service release 1 Build id: 20120920-0800. I have the CDI, dynamic web module, Java, javascript, JSF 2.1, JAX-RS 1.1 JBoss Maven Integration 1.0 and JPA 2.0 facets installed on this project.
It is hard to say what you just uninstalled.
If you want just uninstall visual editor you can do such thing:
Just install onece again Eclipse and when you install JBoss Tools just doesn't select visual editor
Try to unistall visual editor. I think (but I never tested it) you should remove from plugins and features directoris wich starts from org.jboss.tools.vpe
I don't know if there can be some problems with dependencies and so on - you should make backup of Eclipse directory before making any changes.
Maybe it will be sufficient just open the files with other editor:
You can just open single file using other editor, just click in Package explorer view on the file with right click and choose Open with... menu - then you can open the file with for example HTML editor:
You can change the default editor for all files by open Window->Preferences menu and find Find associations position. There should be *.xhtml extensions - choose it and change the default editor.
I have Eclipse PDT 3.0.2 All In Ones installed with Aptana Studio 3.2.0 plug-in. When I create a web project (Project Natures/Web is set to primary) with javascript file and try to use code completion (ctrl + space) this results in "No Default proposals" message. I can right-click on project and select "Configure/Convert to JavaScript Project" though but this is the feature of Eclipse not Aptana.
P.S. CSS and HTML code completion works fine.
That did it. I have changed an editor associated with .js files to JavaScript Source editor instead of JavaScript Editor which was set as default at installation. It would be nice if they added "Aptana" after the name of editor to distinguish it from other editors.
I am using Aptana 3 which is basically a modified version of eclipse, so i think this question is applicable to both
Before I commit code in I like to review my changes via the text compare. It allows me to double check things I have changed.
However although text has been highlighted for changes made it does not keep the php syntax highlights. Is there anyway I can keep the PHP or whatever syntax highlighting when viewing differences?
See screenshot.
This is something that a plugin author must implement, and, it seems that it's still not implemented for Aptana's PHP editor, so, the proper thing to have that would be reporting this as a bug to be fixed in a future Aptana Studio 3 version.
This is a feature of the Eclipse editor. Perhaps you can try opening the file in another editor. Right click on the file and go to open with and choose different PHP Editor.
I am not a PHP programmer but perhaps you can check these links to see if you can find and alternate plugin with the features you want.
http://eclipse.org/proposals/php-ide/
http://www.phpeclipse.com/
First of all, Aptana is not "a modified version of Eclipse". Aptana is based on the Eclipse Platform. I am using the Aptana Studio 3 plugin for Eclipse (3.7.1; because of PyDev and features like "Local Filesystem"). ISTM that this is a problem with the Aptana PHP Editor, which the Eclipse PDT editor takes preference over in Eclipse (that might be due to the fact that I had installed the PDT plugin first).
You can try to work around this if you install PDT in Aptana Studio 3 (if necessary and possible), and define the PDT editor as default for PHP files (in Eclipse, and perhaps Aptana as well, it is under Window → Preferences → General → Editors → File Associations). You can also report this as an Aptana bug. Or use Eclipse with the Aptana Studio 3 plugin in the first place; IMHO, most Aptana editors, including the Aptana PHP editor, are not much of an improvement over the "built-in" Eclipse editors.
The issue has been repotorted on aptana bug tracker (by me) and apparently it is going to be fixed with 3.1
the bug tracking number is APSTUD-3922 for anyone who is interested