Bash 4 has some nice new features that are worth the effort of updating. Install bash. Bash version can be queried with the -version flag: $ bash -version 3.2.53(1)-release The actual installation is going to happen with HomeBrew, the OS X package manager, if you don’t have it, installed it with the following command. Get Opera for your operating system. The Opera browser for Windows, Mac, and Linux computers gives you the most from the Web with features that maximize your privacy, content enjoyment, and productivity. Jul 19, 2017 Trenta OS is a stylish, open source operating system that attempts to give a “premium” feel to the Linux ecosystem. We can’t say that Trenta OS is the first choice for Mac users, as a lot of other Linux distributions do what Trenta proposes to do, only better. I have a shell script that is used both on Windows/Cygwin and Mac and Linux. It needs slightly different variables for each versions. How can a shell/bash script detect whether it is running in C. Git comes with built-in GUI tools (git-gui, gitk), but there are several third-party tools for users looking for a platform-specific experience.View GUI Clients →.
About the App
Install the App
Done! You can now use
bash .
Similar Software for Mac
In Visual Studio Code, you can open an integrated terminal, initially starting at the root of your workspace. This can be convenient as you don't have to switch windows or alter the state of an existing terminal to perform a quick command-line task.
To open the terminal:
Note: You can still open an external shell with the ⇧⌘C (Windows, Linux Ctrl+Shift+C) keyboard shortcut if you prefer to work outside VS Code.
Managing multiple terminals
You can create multiple terminals open to different locations and easily navigate between them. Terminal instances can be added by clicking the plus icon on the top-right of the TERMINAL panel or by triggering the ⌃⇧` (Windows, Linux Ctrl+Shift+`) command. This action creates another entry in the drop-down list that can be used to switch between them.
Remove terminal instances by pressing the trash can button.
Tip: If you use multiple terminals extensively, you can add key bindings for the
focusNext , focusPrevious and kill commands outlined in the Key Bindings section to allow navigation between them using only the keyboard.
Terminal Splitting
You can also split the terminal by triggering the ⌘ (Windows, Linux Ctrl+Shift+5) command or via the right click context menu.
When focusing a split terminal pane, you can move focus and resize using one of the following commands:
Configuration
The shell used defaults to
$SHELL on Linux and macOS, PowerShell on Windows 10 and cmd.exe on earlier versions of Windows. These can be overridden manually by setting terminal.integrated.shell.* in user settings. Arguments can be passed to the terminal shell using the terminal.integrated.shellArgs.* user settings.
Note: For enhanced security, such settings can only be defined in user settings and not at workspace scope.
Windows
For Windows there is a convenient shell selector located inside the terminal dropdown that lets you choose between several detected shells including Command Prompt, PowerShell, PowerShell Core, Git Bash and WSL Bash. The Terminal: Select Default Shell command is also available through the Command Palette if you prefer to access it there.
Just like on other platforms you can fine tune the exact executable used in your settings file, for example:
Note: To be used as an integrated terminal, the shell executable must be a console application so that
stdin/stdout/stderr can be redirected.
Tip: The integrated terminal shell is running with the permissions of VS Code. If you need to run a shell command with elevated (administrator) or different permissions, you can use platform utilities such as
runas.exe within a terminal.
Shell arguments
You can pass arguments to the shell when it is launched.
For example, to enable running bash as a login shell (which runs
.bash_profile ), pass in the -l argument (with double quotes):
Using variables
The
shell , shellArgs , env and cwd terminal settings all support resolving variables:
Terminal display settings
You can customize the integrated terminal font and line height with the following settings:
Terminal keybindings
The View: Toggle Integrated Terminal command is bound to ⌃` (Windows, Linux Ctrl+`) to quickly toggle the integrated terminal panel in and out of view.
Below are the keyboard shortcuts to quickly navigate within the integrated terminal:
Other terminal commands are available and can be bound to your preferred keyboard shortcuts, such as:
Copy & Paste
The keybindings for copy and paste follow platform standards:
Right click behavior
The right click behavior differs based on the platform:
This can be configured using the
terminal.integrated.rightClickBehavior setting.
Forcing key bindings to pass through the terminal
While focus is in the integrated terminal, many key bindings will not work as the keystrokes are passed to and consumed by the terminal itself. There is a hardcoded list of commands, which skip being processed by the shell and instead get sent to the VS Code keybinding system. You can customize this list with the
terminal.integrated.commandsToSkipShell setting. Commands can be added to this list by adding the command name to the list, and removed by adding the command name to the list prefixed with a - .
Look at the setting details to see the complete list of default commands.
Find
The Integrated Terminal has basic find functionality which can be triggered with ⌘F (Windows, Linux Ctrl+F).
If you want Ctrl+F to go to the shell instead of launching the Find widget on Linux and Windows, you will need to remove the keybinding like so:
Run Selected Text
To use the
runSelectedText command, select text in an editor and run the command Terminal: Run Selected Text in Active Terminal via the Command Palette (⇧⌘P (Windows, Linux Ctrl+Shift+P)):
The terminal will attempt to run the selected text.
If no text is selected in the active editor, the line that the cursor is on is run in the terminal.
Send text from a keybindingBash For Mac Os
The
workbench.action.terminal.sendSequence command can be used to send a specific sequence of text to the terminal, including escape sequences. This enables things like sending arrow keys, enter, cursor moves, etc. The example below shows the sort of things you can achieve with this feature, it jumps over the word to the left of the cursor (Ctrl+Left arrow) and presses backspace:
This feature supports variable substitution.
Git Bash For Mac
Note that the command only works with the
u0000 format for using characters via their character code (not x00 ). You can read more about these hex code and the sequences terminals work with on the following resources:
Rename terminal sessions
Integrated Terminal sessions can now be renamed using the Terminal: Rename (
workbench.action.terminal.rename ) command. The new name will be displayed in the terminal selection drop-down.
Open at a specific folder
By default, the terminal will open at the folder that is opened in the Explorer. The
terminal.integrated.cwd setting allows specifying a custom path to open instead:
Split terminals on Windows will start in the directory that the parent terminal started with. On macOS and Linux, split terminals will inherit the current working directory of the parent terminal. This behavior can be changed using the
terminal.integrated.splitCwd setting:
There are also extensions available that give more options such as Terminal Here.
Changing shell for tasks and debug
You can set
terminal.integrated.automationShell.<platform> to override the shell and shell args used by tasks and debug: Print screen for mac.
Changing how the terminal is rendered
By default, the integrated terminal will render using multiple
<canvas> elements which are better tuned than the DOM for rendering interactive text that changes often. However, Electron/Chromium are slower at rendering to canvas on some environments so VS Code also provides a fallback DOM-renderer experience. VS Code will try to detect slow performance and give you the option to change via a notification. You can also change the rendering directly by setting terminal.integrated.rendererType in your user or workspace settings.
Something else that might improve performance is to ignore Chromium's GPU disallow list by launching VS Code with
code --ignore-gpu-blacklist .
Next steps
The basics of the terminal have been covered in this document, read on to find out more about:
Common questionsCan I use the integrated terminal with the Windows Subsystem for Linux?
Yes, you can select the Windows Subsystem for Linux (WSL) bash shell as your terminal default. If you have WSL enabled (through Windows Features), you can select WSL Bash from the terminal Select Default Shell drop down. See Developing in WSL for details on working in WSL and the Remote - WSL extension.
Why is VS Code shortcut X not working when the terminal has focus?
Currently the terminal consumes many key bindings, preventing Visual Studio Code from reacting to them. Some examples are F1 to open the Command Palette and Ctrl+P for Quick Open on Linux and Windows. This is necessary as various terminal programs and/or shells may respond to these key bindings themselves. You can use the
terminal.integrated.commandsToSkipShell setting to prevent specific key bindings from being handled by the terminal.
Integrated terminal exited with code 1 on Windows 10
This can happen if you run VS Code in compatibility mode which may be turned on automatically if you have upgraded Windows. You can change this by right-clicking the executable and selecting properties, then uncheck 'Run this program in compatibility mode' in the compatibility tab.
Can I use Cmder's shell with the terminal on Windows?
Yes, to use the Cmder shell in VS Code, you need to add the following settings to your
settings.json file:
You may refer to Cmder's wiki for more information.
PowerShell on macOS is complaining about a '-l' argument, how do I fix it?
When configuring the integrated terminal to use PowerShell on macOS you may hit this error complaining about a
'-l' argument. To fix this you will need to override the shell args setting as it defaults to ['-l'] to run login shells by default (for bash/zsh/etc.).
How can I change my default Windows terminal back to PowerShell?
If you want to put the default Integrated Terminal shell back to the default (PowerShell on Windows), you can remove the shell override from your User Settings (⌘, (Windows, Linux Ctrl+,)).
For example, if you have set your default terminal to bash, you will find
terminal.integrated.shell.windows in your settings.json pointing to your bash location.
Remove the entry to use the built-in VS Code default or set it to another shell executable path.
Why is the terminal not working when running the 32-bit Windows client on 64-bit Windows?
The easy fix for this is to use the 64-bit version. If you must use the 32-bit version you need to use the
sysnative path when configuring your paths instead of System32 :
Why is Cmd+k/Ctrl+k not clearing the terminal?
Normally Cmd+k/Ctrl+k clears the terminal on macOS/Windows, but this can stop working when chord keybindings are added either by the user or extensions. The Cmd+k/Ctrl+k keybindings rely on the VS Code keybinding priority system which defines which keybinding is active at any given time (user > extension > default). In order to fix this, you need to redefine your user keybinding which will have priority, preferably at the bottom of your user
keybindings.json file:
macOS:
Windows:
Why is nvm complaining about a prefix option when the Integrated Terminal is launched?
nvm (Node Version Manager) users often see this error for the first time inside VS Code's Integrated Terminal:
This is mostly a macOS problem and does not happen in external terminals. The typical reasons for this are the following:
To resolve this issue, you need to track down where the old
npm is installed and remove both it and its out of date node_modules. You can do this by finding the nvm initialization script and running which npm before it runs, which should print the path when you launch a new terminal.
Once you have the path to npm, you can find the old node_modules by resolving the symlink by running a command something like this:
This will give you the resolved path at the end:
From there, removing the files and relaunching VS Code should fix the issue:
Can I use Powerline fonts in the Integrated Terminal?
Yes, you can specify Powerline fonts with the
terminal.integrated.fontFamily setting.
Note that you want to specify the font family, not an individual font like Meslo LG M DZ Regular for Powerline where Regular is the specific font name.
How do I configure zsh on macOS to jump words with Ctrl+Left/Right arrow?
By default, Ctrl+Left/Right arrow will jump words in bash. You can configure the same for zsh by adding these keybindings:
How do I fix the error 'ConnectNamedPipe failed: Windows error 232'
This error can occur due to anti-virus software intercepting winpty from creating a pty. To workaround this error, you can exclude the following file from your anti-virus scanning:
How do I fix when a terminal exits with error code 3221225786 on Windows?
This happens when you have legacy console mode enabled in conhost's properties. To change this, open
cmd.exe , right click the title bar, go to Properties and under the Options tab, uncheck Use legacy console.
Why is my terminal showing a multi-colored triangle or a completely black rectangle?
The terminal can have problems rendering in some environments, for example you might see a big multi-colored triangle instead of text. This is typically caused by driver/VM graphics issues and the same also happens in Chromium. You can work around these issues by launching
code with the --disable-gpu flag or by using the setting 'terminal.integrated.rendererType': 'dom' to avoid using the canvas in the terminal.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |