For some reason the Goland console has started adding a line wrap well before the end of the screen when I run a debug configuration:
This is not happening when run the same command in another terminal or IDE, and I can't find any docs on settings I might have tweaked to make this happen. How do I get it to stop wrapping the lines like this?
It is a known issue in GoLand. Feel free to follow GO-12814.
As a workaround, you can invoke Help | Find Action | Registry, find go.run.processes.with.pty and disable it.
Related
I installed live sass compiler in vs code. No matter what I write inside scss file, the terminal keeps opening (watch the attached video for better understanding of the problem) Please suggest a way of running the compiler in background "SILENTLY".. Ah looks like I cannot add video here so I'm adding an image
settings > extensions > live sass compiler > show output window on
Set setting to warning or error. You can also use none if you want.
In the case of Sass live compiler vscode extension
Open Preferences -> Settings
Search Sass live compiler extension from the left column under Extensions category.
Then search Settings: Show Output Window On setting and set it to none from the dropdown.
It will fix your problem.
if you meant to say that your terminal is frequently opening while your coding in your vs code because of live server
install nodejs and npm install -g live-server
then open the windows terminal and cd into the directory of your project files
and then type live-server and hit enter
ik this is not the best answer and there might be a setting on vscode that can help you but this should work too
That is not the terminal, that is the output window, it displays all the extensions and their live logs. See picture. You cannot disable the outputs of the extensions unless you uninstall that specific extension.
If you don't want constant parsing results select a different window like problems or the actual terminal
Actually this was output window which kept opening to log the errors. My problem was solved by unchecking an option which (I am not sure) was under SAAS settings (dont remember exactly and also cant find again but somehow it got solved >>> Sorry I have low memory :)
You can use this instruction:
"liveSassCompile.settings.showOutputWindowOn": "None"
Just copy it to settings.json file of your Extension Live SASS compiler
I've been trying to build a CordApp and I downloaded the template from GitHub. The code that I've written is available on the following link:
https://github.com/shanmukhipriya99/taskcordapp
When I'm trying to run gradlew.bat deployNodes in the cmd terminal, this is what I got:
[gradlew.bat deployNodes]
Then when I run build\nodes\runnodes in the cmd terminal, this is what I got:
[build\nodes\runnodes]
Then I have three other terminal windows opening-up, they load the Corda part, show some red text that says something about the developer mode and all the node terminals get closed automatically before I'm able to read the entire text.
Can someone please help me in figuring out where I'm wrong!?
Thanks in advance!
It looks like you have had successfully started the nodes all in one terminal. I am not entirely sure, if this is the only issue, but I have seen this issue before. This is caused by lack of permission of the Terminal.
I have seen it happened for both Windows and Unix/Macos users. To resolve it you might need to grant the permission to Terminal manually.
If it still does not work out, I would actually suggest the alternative quick fix that Ashutosh mentioned in comment. Open a new tab and go to the root folder of each nodecd /build/nodes/XXX, and start the node manually via java -jar corda.jar
Using atom-editor 1.13 with the love-ide package installed to run LOVE2d 10.2 games (windows 7)
Apparently if you create a conf.lua file in the same folder as your main.lua file you can add some configuations to main.lua. So, I've got these lines of code in my conf.lua to show console.
function love.conf(t)
t.console = true
end
But when I go back to my main.lua and type print("ballz"), all I see is a blank LOVE2d game screen with no extra console window. Not really sure if this is because I'm using atom editor or not. Everything seems to be PATH'ed correctly.
On a side note, whenever I run atom using the love-ide package it always tries to install some "dependecy files" like the hyperclick-love package, and the auto-complete-love package. These fail to install because I don't have git installed.. honestly I really don't know what git is, but neither it, hyperclick, or auto-complete seemed like requirements to run my game, so in the spirit of not installing unnecessary things onto my computer I never installed these things... annoying as it is to see this notification always pop up when I start atom. Anyone know if this is contributing to the issue, or know a way to remove these notifications or auto-download-attempts? My LOVE2d code still seems to run without these packages.
Have you set up the terminal emulator in your configuration?
(Windows only) Try using the lovec.exe executable instead of the normal love.exe. The first one attaches to the console that executed the game, the second one ignores it.
Lua has a buffered output, try adding io.stdout:setvbuf('no') to the top of main.lua
Maybe I got simple questions so I googled it but I can't find answer.
I am using Pydev/Eclipse and I want to run the script within Console.
First I want to modify the startup of the session - it means some modules are loaded during start (math, numpy, scipy, etc...).
Where/how can I modify Pydev Console startup?
Secondly, I execute the script using righ-click on script file and "Run as -> Python Run" then it's executed within console and terminated. So I want to stay within Console and to be interactive and not be terminated.
How can I get such feature?
Thank you!
Best regards,
Peter
The startup configuration can be found in the PyDev preferences menu. The preferences can be found in the upper menubar under 'Window'.
Window -> Preferences -> PyDev -> Interactive Console
There you will find a big text input field with a label 'Initial interpreter commands'. Often it is allready in use and imports sys only to print the name and version number of the starting console.
The only solution I am aware of for staying connected with your script is to set a breakpoint at the end and start your script in debug mode. But maybe there is another way. To do so just double click at the left corner of the editor window with your script opened. A green dot will appear marking a breakpoint. Now right click an choose 'Debug As'. Your script will run till the line is reached where you have set the breakpoint.
Hope I could help.
I think that what you want is the interactive console. See: http://pydev.org/manual_adv_interactive_console.html
You can configure the initial commands in the preferences page.
There's a lot of examples for ActionScript over the web using trace() to print results.
I'd tryied it using Flash Builder 4, but it don't print to the console. Where can I see the output?
Are you in debug mode ?
Put a breakpoint on the line where the trace() is wrote (ctrl+shift+b), debug and see if the trace is reached.
Are you printing the right string? try to use also a static text in front when doing trace like trace("Loading file: ", _myFile.url);
If you do not want to use Flash Player debugger, but you want to log messages without annoying Alert popups, you can easily
log to the Firebug console.
Are you sure that you are running the debug build and not the release build?
I had the same problem even with the debug player. I could step right past a trace call in the debugger with no console output. I was pulling my hair out checking mm.cfg, flex-config.xml, .actionScriptProperties and all the options I could find in FlexBuilder. Nothing worked...
..until I rebooted my machine (Windows XP 64-bit). No other changes necessary!