I've just created a console application. If I run it from the command line, no problem - I can see my output. But if I run from within MonoDevelop, no application output window appears.
I restarted MonoDevelop and that had no effect.
Any suggestions?
And the answer is somewhat illogical (hence why multiple people have this question).
In the Options for the project, on the Run tab, there is a checkbox for "Run on external console." If this option is cleared, the Application Output window will come back when you run the project, and will the become available from the View -> Pads submenu.
Related
TLDR:
I want to use something like -new_console:t:tabname to open a new named tab in cmder and then transfer focus/control to that tab so that the rest of the commands I'm sending from a Python script run in that console instead. Or, I want to rename a cmder tab from a script running in the console.
DETAILS:
I often have to execute a series of commands in cmder in order to test the latest code from our continuous integration environment. Because there are several applications I often have to have running at a time, it would be helpful for me to have the cmder tabs named according to which application they are running.
The only way I've found to set a tab name from within cmder (apart from manually with mouse clicks) is to do so with the -new_console:t:tab_name command. But that only runs the next command in the newly opened tab, and not all the things that come after it.
I kick off all my commands with a Python script that accepts parameters to let me control which application opens and how things behave. I'd like to do something like this:
os.system('pwd "-new-console:t:' + args.app + '"')
so that a new tab opens with the name of the app I'm about to invoke in it, starting with an indication of the present working directory. But then I'd like all the commands that follow from the Python script to be run in this new tab instead of in the tab used to kick off the Python script. This includes printing some flowerboxed comments, but also invoking a local application server that will continue running.
Is there any way to, as you create a new (named) tab in cmder, transfer focus to that tab so that all future commands run in that tab instead of the initiating tab? Alternately, is there any way from within a cmder console to rename the cmder tab it's running in? That would be just as good.
Thanks!
Thanks for looking, but I found the answer.
In the bottom right corner is a hamburger stack. Click on that and select Settings. In General --> Tab bar, change the Console setting from the default %n to %s. Then the "title" command will change the tab name.
I decided to try Windows 10, but having problem to make terminal works inside WebStorm/PhpStorm.
When I open terminal, sometimes it's completely black, sometimes it loads the project folder but I cannot type there. There is a way to run it in the external window, but I just got accustomed to work with console like internal window inside WebStorm/PhpStorm...
I tried cmd, Power Shell - same results.
Any ideas?
Workaround: Terminal works fine in Windows 10 if you use legacy console.
To do so, open a command prompt window, right click on the title, then select Properties. At the bottom, check "Use legacy console". Confirm the dialog window and go back to WebStorm to launch a new terminal. It should work.
In any case, this is the ticket to watch after:
https://youtrack.jetbrains.com/issue/IDEA-143300 -- star/vote/comment to get notified on progress.
UPDATE:
This issue has now been resolved -- the fix will arrive in next major version -- PhpStorm v10/WebStorm v11 (or whatever that version will be as long as it's based on 142.xx branch or newer).
UPDATE:
For those who have problems with right clicking and finding "Properties" menu entry:
Just for the record: I have confirmation from JetBrains that it will be fixed (i.e. work with non-legacy mode) in WebStorm 11 which is scheduled for the beginning of November. In the EAP version it should already work.
I've set up a FlexUnit test on my Adobe Air project and want to test some functionality that uses NativeProcess. When I run the test it gives this error:
Error: Error #3219: The NativeProcess could not be started. 'Not supported in current profile.'
This is because the FlexUnitApplication-app.xml doesn't have this line enabling NativeProcess:
<supportedProfiles>extendedDesktop</supportedProfiles>
The problem is that FlexUnitApplication-app.xml gets auto generated each time it builds without that line.
I've been able to get it to work by running the test using "Run all tests" from the FlexUnit Results window and letting it fail. Then I add the line to FlexUnitApplication-app.xml in bin-debug and running the tests again. If anything in the project changes I need to repeat these steps so this isn't ideal.
You need to add it to your launch profile: click on the little arrow next to the bug icon and select Debug Configurations (or select the project properties > run/debug settings)
Choose the launch configuration you want to edit on the left of the new dialog. In the "main" tab of this config, the last option is "Profile", you can switch between "desktop" and "extendedDesktop" there.
I am trying to run the Playn example projects. I followed every step in this guide to setup new Playn development environment and then this guide to run sample projects.
it seem to work fine but when I try to run the HTML5 version by right click and then going to Google-> GWT compile, nothing happens. I don't see the development mode view poping up to copy the address and paste it to web browser as the guide says. I just get the following in the console window:
Compiling module playn.showcase.Showcase
Compiling 1 permutation
Compiling permutation 0...
Compile of permutations succeeded
Linking into L:\playn-samples\showcase\html\war\showcase
Link succeeded
Compilation succeeded -- 35.187s
Beyond that nothing happens. If I right click and select run as-> web application, I get the pop out saying
Could not find any hosting pages in the project playn-showcase-html
Anybody know what am I doing wrong ?
What you got from the compilation was all good.
"Beyond that nothing happens." is okay.
When you right click on the "playn-showcase-html" project, select "Run As - (g) Web Application", you should get an output to the "Development Mode" tab as "http://127.0.0.1:8888/Showcase.html?gwt.codesvr=127.0.0.1:9997".
If not, check if you have got the following folder structures under the "playn-showcase-html" project:
playn-showcase-html
|...
|--war
|--Showcase.html
|--WEB-INF
|--web.xml
As far as I know, you can't simply compile (GWT) and run the HTML version. This is because, the HTML version requires a local web server (such as jetty/tomcat) to host the files in order for the project to be 'run'. However, a simpler way around this would be to try using ant via Eclipse.
Window > Show View > Ant
Once the window appears (probably on a sidebar), right-click and select:
Add Buildfiles...
When the list of projects appear, expand the project by clicking the small arrow to the left of the project name in the list. Then select the ant build file:
build.xml
That will add the ant build file to your list of active build files.
Expand similarly to look at the ant tasks provided by the build file.
Double click on the appropriate task; in your case:
run-html
OR
Run ant directly on the command-line to get the same results.
In the current version of PlayN a jetty server is being started automatically. Right click on the xx-html project "Run As"->"maven install". This starts the GWT compiler, and starts a jetty server (default port is 8080), then you can run the HTML5 version by typing "localhost:8080" in yout browser.
I've also wrote a more detailed description about this on my blog getting started with eclipse and PlayN , maybe this could be interesting.
I am getting R6034 error, but can't see the related library/executable since it's name is shortened (see the picture below). Is there any way I can see the full name?
Start task manager and go to the "Applications" tab. The popup should be in that list.
Right-click the window and choose "go to process". Task manager now jumps to the "processes" tab and shows the process that gives this message.
If you want to find out which DLL is causing the problem, open your executable in Dependency Walker. If the static analysis of Dependency Walker does not reveal the problem, profile the application in Dependency Walker and look at the profiling output.