|
Use OmniSearch to open files |
||
|
Expand the current directory. |
||
or
|
|||
|
Collapse the current directory. |
||
or
|
|||
|
Move the selection to the very top of the Project Explorer’s File Tree. |
||
|
Move the selection to the very bottom of the Project Explorer’s File Tree. |
||
|
Opens the selected entry in the Project Explorer’s File Tree. If a directory is selected, then the directory is expanded. If a file is selected, then the file is opened in the main Editing Area. |
||
|
Remove a file or directory from the tree. You will be prompted first to avoid accidental mistakes. |
||
|
If a breakpoint is set, this will unset that breakpoint and vice-versa. |
||
|
Step over a piece of code. For example, if you are stopped at a method call, this will execute that method without stepping through it line-by-line. |
||
|
Step into a piece of code. For example, if you are stopped at a method call, this will go into the first line of that method. |
||
|
After stopping at a breakpoint, and possibly stepping through code, this will enable debugging to continue to the next breakpoint or end of the process. |
||
|
Move cursor to a previous position |
||
|
After breaking at a certain position or breakpoint, it will continue to cursor location. |
||
|
If you have stepped into a piece of code, this will step out to the point on which you entered that piece of code. For example, if you stepped into a method, this will step out back to the method call itself. |
||
|
Detach debugger. |
||
|
Shows the process attachment UI where you will choose the process on which you would like to debug (e.g., a Node process, etc.) |
||
|
Shows the process launch UI where you will choose the process on which you would like to debug (e.g., a Node process, etc.) |
||
|
This allows you to search for files based on patterns. |
||
|
Toggle between the Editing Area and the Project Explorer’s File Tree |
||
|
Toggles the Outline View for a supported file so you can easily navigate to class and function definitions. |
||
|
Copy the absolute path of the current file to the clipboard. |
||
|
Move cursor to a next position |
||
|
Toggle the Console pane. |
||
|
Collapse the entire Project Explorer’s File Tree to the root. |
||
|
Restart the current debugging session with the same configuration settings. |
||
|
Find files related to the current file. A file is related if they have the same basename, but a different extension, for example. |
||
|
Toggle Project Explorer |
||
|
Allows you to search for Hack function, classes and constants within you Hack project. |
||
|
Automatically tries to insert missing require statements to your Flow or JavaScript project. |
||
|
Toggles the Context View. |
||
|
Toggles the focus of the current active file. |
||
|
This lets you switch between files that are currently open in the editor. Useful for quickly accessing files if you have a bunch of files open. |
||
|
Toggle the developer tools UI. |
||
|
When using Hyperclick, this will confirm the Hyperclick action you want to take. |
||
|
Toggle the Nuclide Health tab, which show details about the Nuclide process itself (how much CPU, memory is being used, etc.). |
||
|
Use this for a global search of anything within your project, including all files, currently open files, etc. |
||
or
|
|||
|
Go to the previous diagnostic. |
||
|
Toggles whether the Project Explorer’s File Tree is shown. |
||
or
|
|||
|
Open the Code Diagnostics window |
||
|
Display the window showing you messages about your code. Possible messages include lint, compiler errors, etc. |
||
|
Nuclide can fix certain types of problems for you automatically, including various lint problems. This will allow all those to be fixed in the current file. |
||
|
Expand all the directories from the current to the final directory child. |
||
or
|
|||
|
Collapse all the directories to the top parent. |
||
or
|
|||
|
Copy the relative path of the current file starting at the root of the Mercurial repository. |
||
|
Go to the next diagnostic. |
||
|
This will show you files that you have recently opened and used in previous sessions of Nuclide. |
||
|
Moves the currently active file in the editor to a bottom pane. |
||
|
Moves the currently active file in the editor to a right pane. |
||
|
Moves the currently active file in the editor to a top pane. |
||
|
Moves the currently active file in the editor to a left pane. |
||
|
If a file is selected, it opens the file in the bottom pane. |
||
|
If a file is selected, it opens the file in the right pane. |
||
|
If a file is selected, it opens the file in the top pane. |
||
Advertisement |
|||
|
If a file is selected, it opens the file in the left pane. |
||
|
Shows the file that is currently active in the main workspace in the Project Explorer’s File Tree. |
||
|
Split the current file to the pane |
||
|
Go to the first diagnostic. |
||
|
Go to the last diagnostic. |
||
|
In projects such as Hack or Flow, this will allow you to find all the references to a selected, highlighted entity in your project. |
||
|
Copy the relative path of the current file to the clipboard. |
||
|
Executes the Build task for the currently selected Task Runner or the default one |
||
|
Executes the Debug task for the currently selected Task Runner or the default one |
||
|
Executes the Run task for the currently selected Task Runner or the default one |
||
|
Executes the Test task for the currently selected Task Runner or the default one |
||
|
Executes the currently selected Task |
Advertisement
Source: nuclide.io
|
What is your favorite Nuclide (Linux) hotkey? Do you have any useful tips for it? Let other users know below.
1108032
498772
411518
366987
307454
277921
11 hours ago
11 hours ago Updated!
2 days ago
3 days ago
3 days ago
3 days ago Updated!
Latest articles