They make it easier and faster for you to use commands that you would otherwise have to access via the menus. You can use keyboard shortcuts to easily quit Skype, send a file, copy text and a lot more. Download mac os x lion viber for free. Communication downloads - Viber by Viber media Inc. And many more programs are available for instant and free download. 5 Ways to Get Help in the Command Line of Mac OS X Feb 24, 2007 - 3 Comments Whether you’re a unix novice or veteran to the terminal, if you’re using the command line you’ll often find yourself looking up exactly how to use a specific command for either its understanding the commands full functionality or just to discover the proper syntax. List of Chromium Command Line Switches. There are lots of command lines which can be used with the Google Chrome browser. Some change behavior of features, others are for debugging or experimenting. This page lists the available switches including their conditions and descriptions. Last automated update occurred on 2020-08-12.

1. Skype Command Line Switches
2. Skype Command Line Options
3. Skype Command Line Switches For Macos X

Contents

1. 5 Android

There are command line flags (or 'switches') that Chromium (and Chrome) accept in order to enable particular features or modify otherwise default functionality.

Here’s how it works. Then, start a second instance of Skype using the “/secondary” command line switch. Click this link to see how to create a secondary instance of Skype. You might want to create Skype accounts particularly for this application since the names and accounts can get confusing.

Current switches may be found at http://peter.sh/examples/?/chromium-switches.html

It is important to note that some switches are intended for temporary cases and may break in the future.

Note that if you look at chrome://flags to see if the command line option is active, the state might not be accurately reflected. Check chrome://version for the complete command line used in the current instance.

Windows

1. Exit any running-instance of Chrome.
2. Right click on your 'Chrome' shortcut.
3. Choose properties.
4. At the end of your 'Target:' line add the command line flags. For example:
   • --disable-gpu-vsync
5. With that example flag, it should look like below (replacing '--disable-gpu-vsync' with any other command line flags you want to use):
   chrome.exe --disable-gpu-vsync
6. Launch Chrome like normal with the shortcut.

macOS

1. Quit any running instance of Chrome.
2. Run your favorite Terminal application.
3. In the terminal, run commands like below (replacing '--remote-debugging-port=9222' with any other command line flags you want to use):
   
   /Applications/Chromium.app/Contents/MacOS/Chromium --remote-debugging-port=9222
# For Google Chrome you'll need to escape spaces like so:
/Applications/Google Chrome.app/Contents/MacOS/Google Chrome --remote-debugging-port=9222

Linux

1. Quit any running instance of Chrome.
2. Run your favorite terminal emulator.
3. In the terminal, run commands like below (replacing '--remote-debugging-port=9222' with any other command line flags you want to use):
   
   chromium-browser --remote-debugging-port=9222
google-chrome --foo --bar=2

V8 Flags

V8 can take a number of flags as well, via Chrome's js-flags flag. For example, this traces V8 optimizations:

To get a listing of all possible V8 flags:

Browse the V8 wiki for more flags for V8.

Android

Visit 'about:version' to review the flags that are effective in the app.

If you are running on a rooted device or using a debug build of Chromium, then you can set flags like so:

You can also install, set flags, and launch with a single command:

For production build on a non-rooted device, you need to enable 'Enable command line on non-rooted devices' in chrome://flags, then set command line in /data/local/tmp/chrome-command-line. When doing that, mind that the first command line item should be a '_' (underscore) followed by the ones you actually need. Finally, manually restart Chrome ('Relaunch' from chrome://flags page might no be enough to trigger reading this file). See https://crbug.com/784947.

ContentShell on Android

There's an alternative method for setting flags with ContentShell that doesn't require building yourself:

1. Download a LKGR build of Android.
2. This will include both ChromePublic.apk and ContentShell.apk
3. Install ContentShell APK to your device.
4. Run this magic incantation

This will launch contentshell with the supplied flags. You can apply whatever commandLineArgs you want in that syntax.

Android WebView

This is documented in the chromium tree.

Chrome OS

Skype Command Line Switches

1. Put the device into dev mode, disable rootfs verification, and bring up a command prompt.
2. Modify /etc/chrome_dev.conf (read the comments in the file for more details).
3. Restart the UI via:
   sudo restart ui

First install the latest Skype version and check if you are still blocked with it. Skype is updated very frequently. It is possible that the problem will disappear if you use the latest version.

Usually the block is triggered by UDP packets. There are various solutions for this problem, depending on the computer's operating system:

Windows 7, 8

Under Windows, two solutions have been successful:

1. Using the registry editor (also via the group policy), Skype can be kept from either being a supernode or from generating UDP traffic (see http://download.skype.com/share/security/network-admin-guide-version2.2.pdf). You will need to make the following entries to the registry:

   HKEY_CURRENT_USERSoftwarePoliciesSkypePhone, DisableUDP, REG_DWORD = 1
   HKEY_CURRENT_USERSoftwarePoliciesSkypePhone, DisableSupernode, REG_DWORD = 1

   This can be done either manually or by double clicking the file LRZ-skype.reg that was previously stored locally.

   The entries in

   HKEY_CURRENT_USERSoftwareSkypePhone

   had no effect in our tests.

2. We have blocked all UDP and almost all TCP packets that are sent by Skype with a personal firewall. TCP packets are also blocked because Skype simply switches to TCP after UDP is blocked. Skype functions in spite of this intervention, but your computer is no longer blocked, at least no longer because of Skype.
   We used the Windows 7 Professional operating system and the on-board Windows Firewall for our tests. We have compiled the main points of the necessary configuration steps for this operating system:

   
   

   Control Panel/Windows Firewall/Advanced Controls/Outbound Rules/New Rule

   Rule Type	Custom
   This program path	Path_to_SkypeSkype.exe
   Protocol and ports	Protocol type: UDP
   Local port: All Ports
   Remote port: All Ports
   Scope	For which local IP addresses does this rule apply? Any IP address
   For which remote IP addresses does this rule apply? Any IP address
   Action	Block the connection
   Profile	Domain
   Private
   Public
   Name	Skype-Bremse-UDP
   Description	Prevents Skype UDP traffic
   Finish

   New Rule

   Rule Type	Custom
   This program path	Path_to_SkypeSkype.exe
   Protocol and ports	Protocol type: TCP
   Local port: All Ports
   Remote port: Specific Ports
   1-79, 81-442, 444-65535
   Scope	For which local IP addresses does this rule apply? Any IP address
   For which remote IP addresses does this rule apply? Any IP address
   Action	Block the connection
   Profile	Domain
   Private
   Public
   Name	Skype-Bremse-TCP
   Description	Prevents Skype TCP traffic except for destination ports 80 and 443.
   Finish

   Unfortunately, the Windows Vista operating system does not allow you to configure port ranges (such as 1 - 79), so that the TCP rule has to be left out. It is possible that the UDP rule is sufficient. It is worth trying.

If both solutions don't seem to succeed try to remove and reinstall Skype.

Windows 10

Instruction follows.

Mac OS X (updated 2015-07)

Skype Command Line Options

1. There is a solution with a third-party application firewall (subject to a charge): 'Little Snitch'. You can download a demo version that runs for three hours from the vendor (external link: http://www.obdev.at/products/littlesnitch/index.html)

   For the Skype application you need to add the following rules:

   • Allow outgoing TCP connections to port 80 (http)
   • Allow outgoing TCP connections to port 443 (https)
   • Deny all other outbound connections (TCP/UDP)

2. Use the sandbox built into Mac OS X (experienced users only)

   The process was sucessfully tested with Mac OS X 10.7 (Lion), it should work with 10.6 (Snow Leopard) as well. Putting a program into a sandbox enables the user to control the program's access to system resources. In this case only UDP-network access will be blocked for Skype. You need a configuration file, where the rules for the sandbox will be defined. Copy this file to a local directory an name it e.g. skype-no-upd.sb:
   (version 1)
   (allow network-inbound
   (local tcp '*:*')
   (local udp '*:*')
   (local udp 'localhost:*')
   )
   (allow network-outbound
   (literal '/private/var/run/mDNSResponder')
   (remote tcp '*:*')
   (remote udp 'localhost:*'))
   (allow default)
   ; all|allow
   Now you have to locate the path of the Skype-executable. If installed into the default directory, the path will be:/Applications/Skype.app/Contents/MacOS/Skype
   Use the following command (in one line) to start the sandboxed Skype Application:
sandbox-exec -f skype-no-udp.sb /Applications/Skype.app/Contents/MacOS/Skype
More detailed information on the German Version of this page.


Linux

No systematic solution is available yet.

Workaround: Use iptables/netfilter to block all UDP connections except for those that are absolutely necessary, such as DHCP, DNS, NTP, etc.

Skype Command Line Switches For Macos X

We would like to pass on to you several solutions in the web that users pointed out. These solutions have not been tested by us and therefore come without warranty or support: