Powerful Macros plugin for PhpStorm - plugins

I want plugin for PhpStorm which can record my actions like this: opening files, changing active window with file content, finding contents etc.
Default Macro doesn't support this actions.
Or I want sources of simple macro plugin. Thanx.

Such plug-in doesn't exist. Sources for the Macro subsystem are available in the IntelliJ IDEA Community git repository.

Related

Open Files in Eclipse?

I'm using Eclipse Mars with the TFS plugin. I work with many files that don't have a file extension. Is there a setting to have those files open in Eclipse? Currently, I always get Windows "what do you want to do with this file" selection displays.
All of these non-extension files are plain text that would properly render in Eclipse.
We have a fix in TEE/Eclipse TFS plugin to handle opening files without any extensions from Source Control Explorer in Eclipse. It will be available with our next update.
Thanks,
Madhuri
Jacob:
Unfortunately, the way our Eclipse TFS plugin (i.e. TEE) is written today, you will not be able to do what you are asking (meaning, you will not be able to configure the system so that when you click on a file with no file extension in the source control explorer and have it open in Eclipse – you will always be promoted by Windows to choose the application). We will keep this use case in mind as we continue to support the plug-in and will add it to the backlog of options to be considered in the next release. We are sorry for any inconvenience this is causing you. Thank you for your question.

How to configure nodeclipse for auto completion?

I have just installed this eclipse plugin. But I found it can neither show a list of functions when typing '.', nor use templates like 'if...else...'.
Read http://www.nodeclipse.org/ carefully
Features Creating default structure for New Node
Project and New Node Source File Generating Express project
with Wizard JavaScript Syntax highlighting Bracket
matching and marking selection occurences with background color
Content Assistant within one file Go to definition with
Ctrl+click when JSDoc is
used Refactoring within one file
(Alt+Shift+R) JSON files highlight and
validation NPM support Debugging - Breakpoint,
Trace, Variables, Expressions, etc... via Eclipse debugger plugin for
V8 Setting project properties for JSHint-Eclipse
automatically; JSHint
settings template
Passing arguments to Node application and Node.js,
specifying environment variables values to use Running
CoffeeScript *.coffee files Running *.js files with
PhantomJS, MongoDB Shell or Java 8 Nashorn jjs util
Bundled together with Markdown Editor, GitHub Flavored Markdown,
StartExplorer (for system explorer and shell), RegEx, Icon Editor,
MongoDB, RestClient Tool and other plugins (20+ in total, check
update site and Nodeclispe Plugin
List) Support for Eclipse Juno, Kepler, Luna M3
As of 0.7 completion work as standard JSDT functionality, that is
for objects defined in the same class,
for objects annotated with with JSDoc
If you want more, do it yourself with help from the other people.
I suggest you that you install tern.java which uses the powerful JavaScript inference engine tern.js. You have a node.js module which provides node.js completion. As Nodeclipse editor is based on JSDT, you can use it with tern.

Eclipse CDT, stop auto find

I've recently been trying to setup a little toolchain for something with Eclipse CDT but I'm being driven insane by the default behaviors of Eclipse. It's just so against the grain of other IDEs for C/C++.
Is there anyway to disable the automatic searching of folders in the project directory for the source files? I want to manually add the files for it to compile instead of having to manually exclude all the files I don't want it to compile between multiple configurations.
you can use your own makefile instead on relying on the eclipse auto generated makefile

jade templating syntax support for eclipse?

I have just starting using the nodejs templating engine jade. Unfortunately my IDE eclipse doesn't seem to have support for this syntax and is not highlighting correctly.
Is it possible to add support for .jade files to eclipse?
As current lead of Nodeclipse effort www.nodeclipse.org I announce that Nodeclipse v0.12 has added Minimalist Jade Editor, see http://www.nodeclipse.org/history. Added just before release as I got sick of .jade to be opened outside of Eclipse.
#134 - Minimalist Jade Editor
idea is to define HTML tags and JavaScript keywords as words for highlight in Word.java
and then use it together with EditBox
Nodeclipse scope is growing, now it has Gradle for Android and JavaScript in general that I want to work on for next iteration. Also looking for developers and company willing to support the project. Raise an issue on GitHub/Nodeclipse to continue.
check if this helps
Jade-syntax-highlight
Follow the pattern used for adding HAML support to an Eclipse install, and find a lexer and colorizer for Jade.

Pydev: Go to arbitrary module source?

In Pydev, is there a convenient way to open arbitrary (external, globally installed) module? Say, I want to see the source of markdown.blockprocessors module. How can I do that without typing an import directive (import markdown.blockparser), using "Go To Definition" (F3) and removing the directive? It would be nice to see the hierarchy of the whole markdown package in the Package Explorer, but I don't know how.
There are 2 main ways of finding something without using F3:
Open Resource action (Ctrl+Shift+R): allows you to find any file in your workspace (so, it's useful not only for python modules, but any file, but those need to be in your workspace).
The PyDev tokens browser (Ctrl+Shift+T): allows you to find any token (class/method/attributes/globals -- but currently not module name) for modules in the PYTHONPATH (either source folder or external libraries under the project properties > pydev pythonpath). You can filter things as 'myproject.*something' (the dialog that opens provides instructions on how to filter tokens).
Add Markdown source code folder here::
Project properties -> PyDev PYTHONPATH -> Source folders.