You can run applications right from IntelliJ IDEA if you have an SDK set up for your project/ module.
Quick way
If you are not going to pass any parameters to your program, and your program does not require any specific actions to be performed before start, you can run it right from the editor.
The class that you are going to execute must contain a main() method with a valid signature, for example: public static void main(String[] args).
Click in the gutter near the class declaration and select Run.
To run a script, open it in the editor or select it in the Project tool window, and then select Run </span> from the context menu.</p><p>IntelliJ IDEA creates a temporary run/debug configuration of the type <span>Node.js</span>.</p></li></ul><p>My Windows console application is having its output truncated at a width 120 characters and is not wrapping properly. Using the 'soft wrap' button does nothing. If the text is really long it wraps at 120 characters but characters in the middle are missing. For example, if I printf a constant string with just digits and letters repeated. To use Bazel in CLion, you must install a plugin supplied by Google. To install the plugin, open Settings (either Welcome Configure Settings or File Settings), select Plugins, and press the Browse repositories button. Locate and install the Bazel plugin. You will be prompted to restart CLion. You can define third-party applications as external tools and run them from IntelliJ IDEA. IntelliJ IDEA allows you to pass contextual information from your project to the external tool as command-line arguments (for example, the currently selected file or the project source path), view the output produced by the tool, configure to launch the tool before a run/debug. That said, there are some major caveats. You'll find several frameworks have C, but not C APIs, but embedding C in C requires zero effort, so that's a non-issue. Qt Creator is just IDE, it's incapable of doing any magic. Hence simple answer is: You can't. I don't have enough insight into your console application, but most of cases it's utter nonsense in attempt to turn command line tool into GUI applicatio.</p><h3>Customizable way</h3><p>If you are going to pass parameters to your program, add VM options (for example, to allow remote debugging), or otherwise customize the startup of your program, use a run/debug configuration.</p><ol><li><p>Click in the gutter near the class declaration and select <span>Modify Run Configuration</span>.</p></li><li><p>Modify the run/debug configuration as needed. For example, if you need to run your program with arguments, add the arguments to the <span>Program arguments</span> field.</p><p>To access additional parameters, click <span>Modify options</span> and select the required option from the menu.</p><p>To quickly access the fields only using a keyboard, hold <kbd>Alt</kbd> and use the shortcut according to the hints that appear.</p><p>Click <span>OK</span> to apply the changes.</p></li><li><p>Click or press <kbd>Shift+F10</kbd>.</p></li></ol><p>When the application starts, you can view its output in the <span>Run</span> tool window. Every run/debug configuration creates a separate tab when you run it.</p><p>To learn more about tool windows and how to manage them, see the Tool windows topic.</p><h2>Re-run applications</h2><ul><li><p>On the toolbar of the <span>Run</span> tool window, click or press <kbd>Shift+F10</kbd></p></li></ul>
If you re-run an application, the output of the previous run is lost. To preserve the output of an application, click the Pin Tab button on the toolbar of the Run tool window. When a tab is pinned, new sessions are opened in another tab.
Stop and pause applications
When you stop a program, its process is interrupted and exits immediately. When you pause a program, it continues running in the background, but its output is suspended.
Stop a program
In the Run tool window, click on the toolbar. Alternatively, press Ctrl+F2 and select the process to stop.
Pause a program
Right-click in the Run tool window and select Pause Output from the context menu. Use the same toggle to resume the program.
Only the output is suspended. Pausing the output does not affect the execution of the program.
Shebang scripts
Shell Script plugin (bundled) is required.
Starting with version 11, Java provides a way to run self-contained scripts without the need to compile them (https://openjdk.java.net/jeps/330 ). Furthermore, on Linux and macOS, you can make a Java script executable by specifying the JDK in the first line of the script.
This is called the shebang mechanism. Shebang support in Java comes in handy when you need to write an executable script, but cannot use a scripting language like bash or Python.
Write a script
Create a file without the
.javaextension.Start the first line with
#!followed by the path to the JDK that will be used to run the script. Usesourceto specify the language level of the script. Language level 11+ is required.Example:
#!/usr/lib/jvm/openjdk-14.0.1/bin/java --source 11Write the body of the script. The script can contain multiple classes and use imports from the standard library. The entry point has to be defined as
public static void main(String[] args)in the first declared class.Below is an example of a valid shebang script:
#!/usr/lib/jvm/openjdk-14.0.1/bin/java --source 11 import java.util.Locale; class Hello { public static void main(String[] args) { String lang = Locale.getDefault().getLanguage(); System.out.println(Greetings.getGreeting(lang)); } } class Greetings { static String getGreeting(String lang) { switch (lang) { case 'fr': return 'Bonjour'; case 'es': return 'Hola'; case 'zh': return 'Nǐn hǎo'; case 'de': return 'Guten Tag'; case 'pl': return 'Dzień dobry'; case 'el': return 'Yassas'; case 'sv': return 'God dag'; default: return 'Hi'; } } }Make sure that the script file is executable using the
chmod +xcommand.
Run a script
Click the Run icon in the gutter or press Ctrl+Shift+F10.
Create a run/debug configuration. This can be useful if you want to pass parameters to your script, debug it, or run it as part of a compound workflow.
Debug a script
Create a run/debug configuration for the script and add a VM option to load the debug agent.
Attach to the process using the Remote JVM debug run/debug configuration.
Show running processes
You can view the list of all active run or debug sessions and navigate between them.
From the main menu, select Run | Show Running List. In the top-right corner of the editor, IntelliJ IDEA shows a list with all active applications.
Rider comes with a great debugger which allows attaching to a new or existing process and lets us place breakpoints to pause the application at a breakpoint and see what is going on while executing our code.
In this three-post series, we'll look deeper at what we can do with Rider's debugger and how it can help us debug our code as efficient as possible. In this series:
The table of contents will be updated as we progress. Keyboard shortcuts described in this post are based on the Visual Studio keymap.
In our previous post about debugging, we've seen how we can run and debug a .NET project and set a breakpoint to inspect the call stack and variables that are currently in scope and how we can step through code. All of this is possible thanks to the concept of run/debug configurations — for both normal applications as well as unit tests. A perfect topic for a blog post in our debugger series!
What are run/debug configurations?
If you re-run an application, the output of the previous run is lost. To preserve the output of an application, click the Pin Tab button on the toolbar of the Run tool window. When a tab is pinned, new sessions are opened in another tab.
Stop and pause applications
When you stop a program, its process is interrupted and exits immediately. When you pause a program, it continues running in the background, but its output is suspended.
Stop a program
In the Run tool window, click on the toolbar. Alternatively, press Ctrl+F2 and select the process to stop.
Pause a program
Right-click in the Run tool window and select Pause Output from the context menu. Use the same toggle to resume the program.
Only the output is suspended. Pausing the output does not affect the execution of the program.
Shebang scripts
Shell Script plugin (bundled) is required.
Starting with version 11, Java provides a way to run self-contained scripts without the need to compile them (https://openjdk.java.net/jeps/330 ). Furthermore, on Linux and macOS, you can make a Java script executable by specifying the JDK in the first line of the script.
This is called the shebang mechanism. Shebang support in Java comes in handy when you need to write an executable script, but cannot use a scripting language like bash or Python.
Write a script
Create a file without the
.javaextension.Start the first line with
#!followed by the path to the JDK that will be used to run the script. Usesourceto specify the language level of the script. Language level 11+ is required.Example:
#!/usr/lib/jvm/openjdk-14.0.1/bin/java --source 11Write the body of the script. The script can contain multiple classes and use imports from the standard library. The entry point has to be defined as
public static void main(String[] args)in the first declared class.Below is an example of a valid shebang script:
#!/usr/lib/jvm/openjdk-14.0.1/bin/java --source 11 import java.util.Locale; class Hello { public static void main(String[] args) { String lang = Locale.getDefault().getLanguage(); System.out.println(Greetings.getGreeting(lang)); } } class Greetings { static String getGreeting(String lang) { switch (lang) { case 'fr': return 'Bonjour'; case 'es': return 'Hola'; case 'zh': return 'Nǐn hǎo'; case 'de': return 'Guten Tag'; case 'pl': return 'Dzień dobry'; case 'el': return 'Yassas'; case 'sv': return 'God dag'; default: return 'Hi'; } } }Make sure that the script file is executable using the
chmod +xcommand.
Run a script
Click the Run icon in the gutter or press Ctrl+Shift+F10.
Create a run/debug configuration. This can be useful if you want to pass parameters to your script, debug it, or run it as part of a compound workflow.
Debug a script
Create a run/debug configuration for the script and add a VM option to load the debug agent.
Attach to the process using the Remote JVM debug run/debug configuration.
Show running processes
You can view the list of all active run or debug sessions and navigate between them.
From the main menu, select Run | Show Running List. In the top-right corner of the editor, IntelliJ IDEA shows a list with all active applications.
Rider comes with a great debugger which allows attaching to a new or existing process and lets us place breakpoints to pause the application at a breakpoint and see what is going on while executing our code.
In this three-post series, we'll look deeper at what we can do with Rider's debugger and how it can help us debug our code as efficient as possible. In this series:
The table of contents will be updated as we progress. Keyboard shortcuts described in this post are based on the Visual Studio keymap.
In our previous post about debugging, we've seen how we can run and debug a .NET project and set a breakpoint to inspect the call stack and variables that are currently in scope and how we can step through code. All of this is possible thanks to the concept of run/debug configurations — for both normal applications as well as unit tests. A perfect topic for a blog post in our debugger series!
What are run/debug configurations?
Rider uses the concept of Run/Debug configurations to define how one or multiple projects should be run and debugged. When first creating or loading a project in Rider, a default run configuration is created based on the project type, which should provide 'F5' support – run/debug the application – with minimal configuration required.
It's useful to look at run/debug configurations in a little more detail as there are a few things that can help during debugging. Let's start with the basics and look at the Default run/debug configuration from the Run | Edit Configurations… menu, or from the toolbar.
The window that opens lists all configured run/debug configurations. We can see the default configuration tells Rider to:
- Launch a project from our solution (in this case
Nancy.Demo.Authentication.Forms) - Target a specific framework (in this case .NET 4.5)
- Launch the project using IIS Express, with a series of arguments
Optionally, we can set environment variables for the process that is launched, or add a 'before launch' step which lets us run a given task before running or debugging our project. This task could be running an external tool, starting another run/debug configuration, running Grunt or Gulp, compiling TypeScript and more.
From the toolbar, we can add new run/debug configurations. Rider comes with many different types, depending on the project or task to perform when debugging. Obviously, running a .NET project or application is supported but other run/debug configuration types are available too, e.g. for running a JavaScript application, npm, Xamarin app, … Have a look at them, there are a couple of nice ones (like Spy-JS for JavaScript-based applications, which gives great performance and runtime insights) or performing a Docker deployment.
For .NET and .NET Core, there are a few specific run/debug configuration types that can be added:
- .NET Executable – runs a .NET executable based on path, working directory and optional command line arguments.
- .NET Project – runs a .NET executable project using a specified target framework. Rider figures out the project output directory from where the project should be started. Optionally, command line arguments can be specified. For .NET Core projects, Rider will automatically call the dotnet executable from the .NET Core SDK (configured in Rider's settings).
- Compound – a run/debug configuration that can start two or more other run/debug configurations.
Clion Console Application Download
The Compound run configuration is very useful to run/debug e.g. a front end web application and a backend REST service at the same time. With the debugger attached, this lets us set a breakpoint in any of the projects and we can debug the entire flow of our application:
Once a configuration has been created, it is added to the toolbar at the top of the main window, and can be started from there. Either using the Run menu, the toolbar buttons, or by pressing Ctrl+F5 (Run) or F5 (Debug).
When our application is running, the Run tool window will display process output. When debugging, the Debug tool window is shown where we can inspect what our application is doing, what the values of variables in scope are, and so on.
Debugging unit tests
We don't always want to start and debug our entire application. Sometimes, being able to run/debug a simple unit test is sufficient. Rider's unit test runner supports debugging as well. For any unit test (or unit test class), the left gutter will display a little icon from where we can run or debug our test.
In our application and unit test code, we can add breakpoints just like when doing regular debugging. Rider will pause execution whenever needed by a breakpoint, and provides us with insights into call stack, variables and all that.
A nice touch is that when we launch tests, a run/debug configuration is also created for them. This lets us use the dropdown from the toolbar to quickly run or debug tests we've launched before:
Attach to process
Clion Console Application
Another way to start the debugger is attaching it to an already running process. From the Run | Attach to Local Process… menu, we can attach to any running (.NET) process on our machine. If the process has PDB's and we have the sources on our system, we can break the process at any point in time and look at what is happening at the current point of execution.
In this post, we've seen run/debug configurations and how they can help in starting to debug our applications. We've seen how we can debug our unit tests and how we can attach to an already running .NET process.
In our next post, we'll go deeper into the various types of breakpoints: there are many interesting things we can do with them, beyond just pausing our application! Stay tuned to learn about exception breakpoints, hit counters and automatic enabling/disabling of breakpoints based on conditions!
Download JetBrains Rider and give it a try! We'd love to hear your feedback.
