I want to open the system property window to change environment variable in Windows7. I know how to open that window, and used to use that window sometimes before, but today I opened the window as usual, It does not appear. How can I open it?
You should check why that command stopped to work in your environment, meanwhile try with this (from command line or from Run):
rundll32 sysdm.cpl,EditEnvironmentVariables
Also check this: https://msdn.microsoft.com/en-us/library/windows/desktop/cc144191%28v=vs.85%29.aspx
Related
I know this question looks like dozen of others: but, I am trying to get insight into why this script acts the way it does and if there is any draw back to it like memory leak or other.
The script its simple:
cd "C:\me\python\.venv" && start C:\me\python\.venv\env\Scripts\activate
There is a windows that opens briefly then closes then another command window opens with the virtual environment open as I need. This question is not about the virtual environment in any way. I am trying to understand the command window.
It seems buggy that a command window opens to change directories then closes and then another opens the virtual environment in another window. I can live with this I guess until I run across a seemless way to do this; but, isn't there a better way to do this?
Is the window opening then closing the behavior of the command prompt when changing directories? No! The script could be written simply as:
start C:\me\python\.venv\env\Scripts\activate
and there is still an occurence of a window opening prior to the window with the virtual environment started.
Is there any after affects from doing it this way, like background process open or memory leak or what have you?
Anyone know where to read the "readme" on this behavior?
Thank you much!
Use this code:
cd "C:\me\python\.venv" && C:\me\python\.venv\env\Scripts\activate
the start command is not necessary and that's what opens one more window and lets the previous one close.
This command create a new windows asynchronously.
I created a macro in Excel and i am running it from a .vbs file. It's working fine on my laptop. I copied the same work on a new laptop and each time i am running the vbs file this window appears on the screen.
I have made some research and read that the situation i mentioned is happening when loading CheckNDISPort service on the startup. But i don't believe it's the reason because when i go to task manager and check in the startUp tab i don't find this service. Also when i restart my laptop i don't get this window, only when i am running my vbs file. I am sure there is any problem with my vbs file too because on the other laptops it's working fine.
Any suggestion please how to get ride of this pop up ? For now i am closing the window each time or ending the task from task manager but everytime i run it again so it pops up again.
Thank you very much.
Windows Scripting Host has two interpreter front-ends, wscript.exe and cscript.exe. cscript.exe is a console application and if cscript.exe is set as the default a console window will open every time you execute a script.
Run cmd.exe elevated as administrator and run wscript.exe //h:wscript.
Depending on the Windows version, you might also be able to right-click a .vbs file, select "Open with...", choose %windir%\system32\wscript.exe and check the "default" checkbox.
I want to set a global shortcut that will open a certain file. When there already is a gvim window that has that file open, I want it to focus on that window, and select the tab with that file. If there isn't, I want it to be opened in a new gvim window, regardless of whether there already are other gvim windows.
I can do part of this with --remote and --servername, but I can't find a way to detect whether there already is a remote server running with the name I use, so I can't quite get everything to work together to come to what I described above.
OK, turns out most can be done using the default behavior of --remote-silent. The whole setup is a matter of making an AutoHotkey script like this:
#!^+1::
Run "c:\Program Files (x86)\vim\vim74\gvim.exe" --servername org --remote-silent %DROPBOX%\org\TODO.org
WinActivate, TODO.org
Return
AHK is needed for the global hotkey as well as activating the window; vim (using --servername and --remote-silent) will start a new session called 'org' if there isn't one yet, and start it otherwise. It even gets the tab activation right when there already is a server called 'org' but if that server has another tab active.
I have no idea where to start about creating the solution for this, as I am only experienced in JS/HTML/Java/Lua/C++. What I'm trying to do is, from the command prompt, click at any place in an already opened window. For example, the already opened window could be a program called "Gorg" with the title/name "Gorgiant", and it would just need to simulate a click anywhere in that window if that's possible.
Perhaps you can try AutoHotKey . It has commands to check if a window exists .
I recently installed RubyMine v7.1.4 on my Windows 10 machine. I loaded up an existing project and tried to open a terminal window inside RubyMine. When I first open the terminal it is blank and after a few minutes the standard prompt appears. But after the prompt has appeared, I cannot type anything into the terminal. The cursor blinks like it is waiting for input but I cannot type anything.
I am able to use a normal command prompt to run the commands I need to but I would like to get the terminal within RubyMine working. The settings for the terminal appear to be correct, it is pointing at "cmd.exe". I am not sure if it is relevant but my RubyMine installation is on my C: drive but the code repository is on my E: drive.
If you have any suggestions, they would be greatly appreciated. Thanks!
I had the same issue, and discovered that it is also affecting IntelliJ, another JetBrains family IDE; the bug has been reported, but fortunately, you can force your Windows 10 console (full of new features, but perhaps buggy? https://wpdev.uservoice.com/forums/266908) to operate in 'legacy mode' while we wait for a formal fix, which will allow you to get your RubyMine terminals up and running again:
Terminal works 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. Go back to the IDE
and launch a new Terminal. It should work.
All credit to: IntelliJ Idea Terminal broken with Windows 10. | JetBrains Bug Report.