Where is Gulp log file? - gulp

Running Gulp on a Mac under Docker using Visual Studio Code - the error messages slide into view in a tiny window, and then slide away in about 2 seconds.
It trims off the useful info. I only see about 15 words.
How do I either display the entire message and get it to stay on screen longer, OR where do I find a log of Gulp errors?
Is VSC the culprit?

Right - full error text is shown in terminal window where Gulp was started. The little sliding "now you see me, now you don't" box is very annoying - a perfect misdirection device.

Related

Octave pop up message

I am running Octave 4.4.1 on MacOs Catalina 10.15.7. For some weeks I have been having this message poping up when a code is running: "
It seems that [name of script] has been modified by another application. DO you want to reload it?
I click Yes each time it pops up, but when the code is running, it just keeps coming back, and sometimes Octave becomes unresponsive although the script has finished running
All I could find on the internet were either some old posts with answers about outdated Octave versions, or very complicated stuff that I would not be able to implement.
Any one knows why this happens, and what to do about it?
thanks a lot
This message is exclusive to the GUI version of Octave, and it comes up if you have a file open for editing in the Octave GUI Editor window, and the file's contents change due to a process unrelated to the Octave Editor.
E.g. you may also be editing the file on an external text editor at the same time? Or your script may be copying / generating a new file under the same name as a file that you've got open in the editor, effectively overwriting the now-out-of-date version that's still being displayed in the Octave Editor?
Octave gives you this warning to prevent you from 'saving' in your editor, and therefore undoing any changes that had been made by the external process in the meantime.

WebStorm/PhpStorm, issue with terminal on Windows 10

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.

How to set the height of the Sublime Text 2 status bar, or get its history?

I'm currently using the Sublime Code Intel plugin with ST2. Trying to add additional python paths but it's not working. So I'm trying to do a little debug and notice that the plugin prints the paths being searched in the ST2 status bar as it's building the index. The problem is, a lot of the messages go by too fast. I've just started using this editor and so far I can't find out how to either expand the height of the status bar - so I could scroll up a few commands - or view some sort of status bar history. As it is, I can only see the last thing logged in the status bar and that's not very useful for debugging my problem.
The console provides useful debug info. You can also use it to enter Python commands.
To open: ctrl + `
or
View>Show Console

Playn HTML5 won't run from Eclipse

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.

How to make Flashdevelop errors appear in Results Panel?

I am using Flashdevelop to build an Actionscript 3.0 game. It was originally a FlashIDE project but I decided to migrate the project to FlashDevelop. I also changed some asset and property names, as a result there were a lot of syntax error. The errors keep coming out in the Output Panel instead of Results Panel (is that normal) when compiled. I know that when I click errors in the Results Panel it will open and point the error in the Code Panel. I can't do that with errors in the Output Panel (I assume its normal). Is there something I can do to make the errors clickable ?
Even a simple error like this doesnt come out in the Results panel:
Loading configuration file H:\04 Noveline\03 GD\GD03\Folder (aaaa)\TEST\obj\MeccatomedinaConfig.xml
H:\FD(1)\TEST\src\Game.as(75): col: 3 Error: Access of undefined property sssss.
sssss
^
Build halted with errors (fcsh).
(fcsh)
afaik it's impossible to make output panel clickable. but you can press F10 to open program settings dialog and check if your results panel is disabled. and also disable output panel if it's really annoying)
The errors should appear in the results panel and the output panel. Make sure the results panel is open.
Remove parentheses from project path to workaround the issue.
(As Stucko & Markus von Broady wrote in comments.)
This issue is still around for FlashDevelop 5.1.1.1.
I have logged the issue here for ref:
https://github.com/fdorg/flashdevelop/issues/1676