When i run new terminal it show not understandable think
How stop this
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 got tmux installed, and I can run make and it builds in a pane down, and I can continue to look at code. I would also like to run scripts(tests) and they should run while I see the results of the tests in another pane, while I look at code. How can I do that?
Here I want to ask you to help to bring the console window top most with a shell command. Is it possible?
there was a script execution in my work environment, and will take about several minutes to complete, I will move to other work while running, it is better there are some tips to notify me when script completes run.
So I think bring the window top most is the most direct way.
Please tell me how to achieve this, I'm working on windows, new to MacOS.
Thanks,
Levi
I don't know how to bring the console window to the front, but if you're working in the terminal, you could do something like:
$ path/to/script ; tput bel
or
$ path/to/script ; say "script 1 is done"
Where path/to/script is whatever your usual method of loading the script is.
I recommend the first method, as it flashes the screen, makes a beeping noise, and causes the terminal icon to bounce up and down on my dock in OS X 10.10. The second might be better if you need to figure out which script is done from among a bunch of scripts. If you have coworkers who you don't want to disturb, you can change the preferences in terminal so that an alert only flashes the screen and doesn't also make a noise.
If you have access to the source code of the script, you can also add tput bel or say "command" to the last line of the script and you'll get the same behvaior.
I'm using a mac and I've got a automatic terminal window opening up at login, I would like to make this window execute a command, that will then open up another terminal window, with a layout that I've already made earlier and with full screen. I know that you can open another window with: open -a Terminal "pwd", but how do I add arguments for a custom layout? I haven't seen any way to solve this, have you got ideas?
I'm just starting to use Grunt on OSX. I initialise a folder watch with grunt watch. Every time I make a change and Grunt runs, the dock icon for terminal bounces and a red "1" indicator bubble appears. This is very annoying. Has anybody found a way around this issue?
It looks like grunt is appending the terminal bell character (\x07) to fail messages, see here: https://github.com/gruntjs/grunt/blob/25728e1744836b42927962a005fe1ce15f55640f/lib/grunt/fail.js#L31
Reading the code, it looks like you can disable this terminal bell by specifying the 'color' grunt option (which doesn't make sense to me). You can stick this in the top of your gruntfile:
grunt.option('color', false);
(I would love to know if there is a more elegant way of specifying grunt options.)
I have just successfully suppressed this EXTREMELY annoying behaviour with the following:
1: Open Terminal (given if you're reading this you came here as a result of a bouncing Terminal icon I shouldn't have to point out that it's in Applications->Utilities->Terminal
2: Type the following:
$ defaults write com.apple.dock no-bouncing -bool TRUE
$ kilall Dock
3: Thank the folks over at Switching to Mac who pointed this out.