We Keep Coding

Turn off VSCode "Convert to named function" hint

I personally prefer arrow funtion than JS named funtion. but that light bulb keep annoying me, it even hide my code sometimes ( yes, it in row 1 of editor ).
All I want is disable it. I tried some setting in settings.json but not found it.

There's currently no way of disabling this specific feature as of v1.71.2
You can however turn suggestions from showing up by adding this to your settings.json:
"editor.lightbulb.enabled": false,
However - it's still accessable through ⌘ + . on Mac OS X or ctrl + . on Windows. It just doesn't show up and block anything.

Is it possible to get to the method definition in visual studio code for AngularJS project?

I want to find the method definition in my AngularJS project but I am not able to find any shortcut to this. I've tried Ctrl + Click but it did take me to the first occurrence of the variable where it was defined in that particular file not to the method definition.

Go to Definition
If a language supports it, you can go to the definition of a symbol by pressing F12.
If you press Ctrl and hover over a symbol, a preview of the declaration will appear:
Tip: You can jump to the definition with Ctrl+Click or open the definition to the side with Ctrl+Alt+Click.
Read the full documentation here. Visual Studio Code

How to set a new keybinding in Atom on osx

I've started using Atom with a Macbook and I wanted to create a keybinding so that alt-up arrow would be page up and alt-down arrow for page down, I've tried a bunch of options and I'm not having much luck.
I'm not sure what the difference between
'atom-text-editor':
and
'atom-text-editor:not([mini])':
is and which one to use. I also have a package called emmet installed which is using alt-up and it always overrides what I'm trying, however I thought the keymap.cson file should override all 3rd party packages.

The mini scope
The mini scope is for single-line inputs. For example, the "Find" or "Find in Project" panels use mini editors to accept input. The not([mini]) selector excludes those, so that your binding is only used in code editor windows/panes.
In this specific case, in practice it probably doesn't matter a lot, as the mini editors won't do anything with page-up or page-down anyway. But in general, I think it is better to scope the key bindings correctly instead of just making it global. It's a good habit.
Selectors
You already have a good selector (atom-text-editor:not([mini])). In the comments you asked what other selectors are (in particular, atom-workspace and ::shadow). I don't have a great explanation of ::shadow but you might read a bit including here.
atom-text-editor is scoped to, as you'd expect, text editor panes. Whereas atom-workspace is a bit wider scope: it is scoped to the entire window, which might include things like the tree view, tabs, status bars, etc.
The ingredients of a key binding
In order to make a key binding, you need three things:
A selector to apply the binding to a certain scope. You already have that, as it was in your question text. atom-text-editor:not([mini])
The key binding to use. You can find those in Atom's documentation. In this case, we need to use alt-up and alt-down.
The Atom command to point each key binding to.
How to find Atom commands
Using the Command Palette
Every Atom command should be available in the Command Palette (CmdShiftP). In your case, you can trigger the palette and search for something like "page".
You can see two matching commands, "Core: Page Up" and "Core: Page Down". To turn these into usable commands, you reformat them like so:
Remove the space after the colon
Replace spaces with hyphens
Lowercase everything
That leaves you with core:page-up and core:page-down.
Using the Key Binding Resolver
In some cases, you want to take a command already mapped to a key, and map it to another key. In those cases you can locate the command using Atom's Key Binding Resolver.
Activate the resolver by pressing Cmd.. This will open a panel at the bottom of your window and tell you what command each keypress is tied to. Pressing PageUp or PageDown will point you to the core:page-up and core:page-down commands.
Press Cmd. again to deactivate the Key Binding Resolver.
Adding your keymap
In Atom's preferences, you can click "Open Config Folder" to open a new editor window with the config folder loaded. Open the keymap.cson file to add your new keymap.
'atom-text-editor:not([mini])':
'alt-up': 'core:page-up'
'alt-down': 'core:page-down'
Save the file and your keymap should go into effect immediately.

To add new keybindings open the your ~/.atom/config.cson, and your own binding using example
'atom-text-editor':
'ctrl-alt-b': 'atom-beautify:beautify-editor'

How to enable code assist for the DOM for JavaScript projects in Eclipse

How can I simply get in this little popup (code completion) all possible methods/functions given when I type window.(blablabla).
Because if I type window. there is no "event" method for example.
In NuSphere there are all methods been listed.

Please differentiate between JavaScript and DOM code assist. There are many questions/answers here about this but it's ambiguous which of these two they refer to. None, I've seen, particularly claims to have found a solution for DOM and most mentions Aptana as standalone IDE or Eclipse plugin for solution.
For reasons outside the scope of this question I use Eclipse Indigo (3.7.2) and got this working w/o Aptana. This solution probably depends on the JavaScript Development Tools plugin.
First in the Navigator pane right click the project and hover the Configure option. Select Convert to JavaScript project or Add JavaScript Support.
Open project properties and a JavaScript item should appear in the left hand side list of configuration options. Expand and select Include Path. In the Libraries tab on the right you will see ECMA Script and ECMA 3 Browser Support. Switch to the Global Supertype tab and tick the ECAM 3 Browser Support checkbox. Restart Eclipse.
--
However in my case this last option didn't seem to work (when selected 'window' as global supertype, below the list got 'Window() null') and window. didn't bring results but document. and all other JS globals did. (So I could say for e.g. var w = document.defaultVeiw; and w. did bring up desired list.)

Disabling tip in Aptana Studio 3

I'm using Aptana 3. I'm selecting some fragment of code (innerHTML) and I want search for it in files using shortcut Ctrl+H. But then some tooltip is showing, and I have to press 2 key to get search dialog. How turn it off? I want seach dialog just after Ctrl + H.

It's because a javascript ruble command 'Documentation for Word' is bound to Ctrl+H and so is the Eclipse 'Open Search Dialog'. You can try changing one of the two bindings:
For Open Search Dialog, go to Preferences > General > Keys and change the binding.
For the ruble command, you'd need to pull down a copy of the bundle and edit the command's binding. Commands > Javascript > Edit this Bundle, then open commands/documentation_for_word.rb and edit it.

There are a number of key bindings Aptana 3 users don't have control over in our preferences gui. One other is 'Delete Line' command mapped to ctrl+shift+k. i truly wish the Aptana folks would fix this key mapping issue.

And if editing the command file does not help, here's what worked for me with Aptana Studio 3.0.1.201104291443:
Download the bundle with "Edit this bundle"
Chuck it out of the workspace (aka delete project)
Quit Aptana
Fix the problematic commands/...rb in some editor
Restart Aptana, retry the command and rejoice:-)