I encountered a weird setting problem of vscode with python.
I am now using vscode and python to develop apps that can run both in Win 10 and macOS.
Yesterday I copied all code from win10 in a PC to macOS in a macbook.
Then I made some changes in macOS and copied everything back to win10 since I need to trouble-shooting some bugs by my win10 users.
I am sure that I only copied the source code of my modules without copying the vscode setting.
But I found now in vscode in win10, print statement to the vscode console automatically adds two newlines between each object in the print statement argument list.
I found that I can use option sep="" to avoid one newline. But one newline persists between every two arguments.
This problem does not occur when I run the python program in win10 console.
I will appreciate it someone can let me know what has happened and how to correct this anomaly of vscode.
Thank you very much.
Related
This is the same problem discussed in
Cannot connect to X server using docker on OS X - Part II
but never resolved.
In MacOS El Capitan, I'm running the OpenFOAM binary under Docker as there is no native version. I want to use paraView to view results. Cannot run the paraView supplied inside OpenFOAM since I get
paraview: cannot connect to X server
The advice here
Cannot connect to X server using docker on OSX
is to install paraView separately and run it from a normal terminal. This did not work as a normal terminal cannot "see" Docker files. And I cannot run the suggested
open -a paraview foam.foam
inside the docker terminal, as for some reason it does not recognize the "open" command.
Perhaps some Docker expert can help?
The team at OpenFOAM.org worked a lot on the issue recently to release a good solution to the MacOS users (http://openfoam.org/download/4-1-macos/).
Unfortunately, they reached the conclusion that going through X in Docker although working was not a solution because it freezes most of the time and it is really not convenient.
I understand from the question that the files cannot be seen from the MacOS terminal (that would require to know which version has been used). In the release of OpenFOAM 4.1 (see link above) in Docker this is done by the script and therefore it is directly possible to access the file by opening them with ParaView in a regular terminal.
I am posting this question because I stumbled upon the solution, despite not being able to find anything online which helped my specific problem. I am posting the accidental fix as an answer.
Problem: I am using adt.jar via cmd and an ANT script to package the air tablet application. Everything works fine on my workstation, but ipa builds fail on the build machine. The build machine is just a re-purposed workstation with more memory, larger hdd, and runs tomcat/hudson. Both environments are Win7 SP1. By 'everything' I mean apk builds in various configurations, and ipa builds with testing and production provisions files.
Error messages varied a little bit, but here are the common two messages:
Compilation failed while executing : compile-abc
Error #1042: Not an ABC file.
The stack dump was just a bunch of parameters passed into adt -- application specific.
Things I tried based on many internet searches:
Update to latest air 17 beta (17.115) Did not work. I did not expect this to fix my problem, because the PC which successfully builds the ipa does not have this version of the sdk
Hunted down empty case blocks in the code. There were a couple, but again this did not fix the problem. Still works on my machine and not the build machine. I actually made sure the empty blocks existed on the functional environment to disprove this attempt. I am not using "-useLegacyAOT no", so this should not have helped.
Compared all relevant environment vars between the two systems, and matched the ones that were different. This did not fix the issue.
Checked the version of jdk pointed to by JAVA_HOME. Both were already "64-Bit Server VM (build 20.45-b01, mixed mode)" aka: jdk-6u45-windows-x64.exe
Out of desperation, I ran Windows Update on the environment which failed to produce ipa files. There was a recommended update to the .NET framework which something in my tool chain must depend on. This fixed the problem.
Microsoft .NET Framework 4.5.2 for Windows 7 x64-based Systems (KB2901983)
My personal workstation is always up to date, and I restart often. This was not the case for the build workstation.
EDIT: A second update was also installed at the same time. This could be what fixed things, but I'm not going to question it.
Update for Windows 7 for x64-based Systems (KB3021917)
I am trying to build a dissector for Wireshark on Windows platform. But, I am getting an error.
I followed this link to install Wireshark from the source on windows, and I was able to build and run the software successfully.
Then using the README.plugins, I added a plugin, and did all the changes, mentioned in the file.
With the plugin, it built successfully, but whenever I tried running it, a dialog box appears stating The plugin 'ABC.dll' has neither a register routine, a register_tap_listener or a register_wtap_module or a register_codec_module routine.. Though wireshark is running fine, but my plugin is not included in it.
Linux Environment: I tried compiling and running on linux platform, and it worked fine, with the plugin included.Can anybody tell me, where I might be going wrong on the windows platform. Thanks.
There's a bit of magic which happens when building plugins on Windows so that certain symbols in the DLL are declared as exported so they can be found in the DLL at run-time. (I haven't recently dug into all the details, but the mechanism is different on *nix and so the results on each platform might be different).
What version of Wireshark are you building ? (How are you getting the Wireshark sources ?).
The specific error message you re getting suggests you might be building a version of WWireshark 1.10. (The message has changed in the Wireshark development version (1.11)).
In any case, something is not quite right (obviously) as to how the DLL is being built on Windows.
My suggestion as a starting point:
You might be able get an idea as to what's wrong by
comparing the plugin.c file (which is generated at build time) in your plugin directory on Windows with a plugin.c from one of the other Wireshark Windows plugin directories.
The magic occurs in that file.
Things like:
WS_DLL_PUBLIC_NOEXTERN void
plugin_reg_handoff(void)
{
{extern void proto_reg_handoff_unistim (void); proto_reg_handoff_unistim ();}
}
Hello,
I'm using bash or cmd for Rails console.
I get this weird symbols like <-[1m.
In my tutorial I see the output fine (With spaces and color), and it's difficult to read it in my cmd...
Can you help me to display those special characters right?
Thanks!
Instead of using cmd, run rails and ruby through cygwin, it works better than cmd as cygwin is supposed to bring you a linux environnement on windows. When i tried to do rails on windows it was the most complete tool.
I insist on the fact that you should use a Linux VM to do rails on windows. If you install VMWare player on your windows, you will have a virtual machine running in vmware on your windows desktop. This machine will be connected to you network. I strongly advise you to use this solution, as you will encounter many problems using rails on windows.
I work on windows, and i have a Virtual Ubuntu always launched. My VM share the code via samba and i edit it with sublim text executed in windows. On my second screen i have my VM full screen that display multiple terminals.
Ok, I found this wonderful software https://code.google.com/p/conemu-maximus5/ and it did solve my problem :)
cmd.exe doesn't understand those color codes.
There is a project to make cmd understand them (and add other useful feaures) here. I do not use windows, so I cannot vouch for the quality of it.
I installed WinDDK 7600 in my Windows XP operating system.Now,when I double click the devcon.exe(Location- D:\WinDDK\7600.16385.1\tools\devcon\i386),the command prompt is just showing up and suddenly disappears.Can anyone resolve this issue.
As far as I'm aware devcon is a command-line only program. You have to run it from a command window (cmd.exe) with the appropriate parameters. Once you know the parameters you want to use, you can write a batch file to easily recreate the command you want.
I ran across this post because Win7 has a similar problem even when running in cmd.exe.
There is a solution found on Microsofts website here:
http://answers.microsoft.com/en-us/windows/forum/windows_7-hardware/devcon-not-working-correctly-in-windows-7/9abcc12c-d7db-4249-aec4-fc4ff0ea6ee8
I have not been able to verify it yet.
The same (a windows open and automatically close) happens even if using a normal command prompt. However opening the command prompt with administrator rights and then run devcon works.