FeatureSwitch and aboutflags don't play nice. Feature switch expects either -enable- or -=1, but aboutflags expects the command line argument to enable it (or a selection). Hack this in, so enabling it in aboutflags enables the feature. Use the dynamic build of the stable Skype client (4.3.37), is the only one that works (the interactive installer automatically download and install the correct Skype client, see below). Don't use the build for your distro. Supported Platforms and Distros. Skypopen runs well on Linux and Windows. Does not work on Mac OSX. Most supported Linux.
List of command line parameters in the new Skype
Parameter | Description |
---|---|
--datapath='path' | Changes the folder where the user data is stored (by default, Skype stores them in %APPDATA%MicrosoftSkype for Desktop ). If path does not exist, Skype creates all the necessary folders. |
--lang=ISO-639 | Force Skype to use the specified locale. For example, use --lang=en-GB for British English, even if the OS has a different language or datetime format. |
--secondary | Launches several instances of Skype at the same time. To run multiple accounts, you must specify the parameter --datapath |
--shutdown | Closes Skype processes, started without the parameter --secondary |
--_='URI scheme' | Launches Skype using parameters of the URI scheme skype: (for example, if you pass --_='skype:echo123?call&video=true' , Skype will make a video call to the echo123 service). |
In addition to these, there are several other parameters, but I am not sure yet what they are intended for. Some of these parameters are given below:
--application-name
--auto-start
--migration

Since the new Skype is developed on the basis of the Electron framework, users can use more than 1200 parameters that are available for Chromium. A complete list of these parameters can be found here: https://peter.sh/experiments/chromium-command-line-switches/

How to run more than one account at a time?
For example, create a new shortcut for each account and specify the following path:C:Program Files (x86)MicrosoftSkype for DesktopSkype.exe --secondary --datapath='F:SkypeNewLogin_1'
For a more convenient way, read How to run multiple Skype programs simultaneously or How to create a portable Skype for Windows.
Skype Command Line Switches
Skype Command Line Switches For Macos Update
The article clearly does not contain all the information about the parameters in the new Skype, so I will periodically update the material. Also, I will be grateful for any comments and additions.To totally unlock this section you need to Log-in
Login
Well this is most of the time easy but useful when need and you can't remind the command you have to use to add a static route in a Mac OS X installation.
Open fist the terminal session. Use the following command:
sudo route -n add x.x.x.x/24 x.x.x.x |

You have to enter your password.
To delete a route you have to use the following command:
sudo route -n delete x.x.x.x/24 x.x.x.x |
To view you route table on you Mac you use the following command:
netstat -nr |
Add a startup item (to avoid doing the above command every reboot):
cd /System/Library/StartupItems mkdir AddRoutes cd AddRoutes |
Create a file called AddRoutes (Note: same as the folder name).
:max_bytes(150000):strip_icc()/SkypeUninstalling-3778b4d700f84f5f8b561baf4d42a8fe.jpg)
Skype Command Line Switches For Macos X
vi AddRoutes ------------------------- #!/bin/sh # Set static routing tables . /etc/rc.common StartService () { if [ '${ADDROUTES:=-NO-}' = '-YES-' ]; then ConsoleMessage 'Adding Static Routing Table' sudo route -nv add 10.0.0.0/8 10.16.3.254 fi } StopService () { return 0 } StopService () { return 0 } RestartService () { return 0 } RunService “$1″ |
Skype Command Line Switches For Macos 7

Skype Command Line Switches For Macos Catalina
Then create a file StartupParameters.plist:
{ Description = “Add static routing tables”; Provides = (”AddRoutes”); Requires = (”Network”); OrderPreference = “None”; } |
Then change permissions:
chmod 755 AddRoutes StartupParameters.plist |
Skype Command Line Options
Reboot your computer. Verify with netstat -nr.
