19
I experimented quite a bit with emoji in cmd, and these are the conclusions that I came to:
??
.netsh wlan show profile
(which lists all the network profiles) command shows me:netsh wlan show profile 12346??
.But... CONFLICT! What if there are two identical SSIDs, just with different emoji?
To test this out I created a second hotspot with the SSID 12346
. CMD obviously couldn't differentiate.
But the output of netsh wlan show profile 12346??
had something interesting:
Profile 12346?? on interface Wi-Fi:
=======================================================================
Applied: All User Profile
Profile information
-------------------
Version : 1
Type : Wireless LAN
Name : 12346??
Connectivity settings
---------------------
Number of SSIDs : 1
SSID name : "12346dY~?"
[[REDACTED IRRELEVANT INFO]]
Profile 12346?? on interface Wi-Fi:
=======================================================================
Applied: All User Profile
Profile information
-------------------
Version : 1
Type : Wireless LAN
Name : 12346??
Connectivity settings
---------------------
Number of SSIDs : 1
SSID name : "12346dY?·"
First we notice that cmd (very smartly) runs the command for both SSIDs. But we only want to run it for one SSID...
Secondly, we see that one has been assigned the SSID 12346dY~?
, and the other 12346dY?·
. However, using either of these in the command just gives us an error... Bummer!
So what do we do?? Pretty simple, you use the Touch Keyboard (on Windows 10) to insert the emoji into the console, or you can copy-paste the emoji from elsewhere, both work perfectly, even though the emoji isn't displayed properly.
What about Files and Folders?
I created two folders, and
. This is what
tree
shows:
Luckily for us though, we can simply use tab to circle through the folder names at the prompt, but again, we have no way of actually viewing the folder names. In this case, one option is to rename the folders by using the ren
command. Another option is to use the dir
command to inspect the properties of the files/folders and determine which one you need.
Just use ConEmu!
ConEmu apparently has better unicode support:
3
Interesting read (and source for the last image): Abusing Emoji in Windows
– rahuldottech – 2017-04-09T12:09:43.670The Windows 10 Creators Update appears to be pushing you to use powershell over cmd
, is unicode supported there? – Mokubai – 2017-04-09T12:35:41.893
1
UPDATE! This screenshot shows the command necessary to enable unicode in powershell. Thanks @Bob!
– rahuldottech – 2017-04-09T15:19:46.753To clarify further, the screenshot in @Rahul2001's last comment is from the PowerShell ISE program (included with PS), not the basic console. The chcp 65001
is meaningless, but there must be some kind of external command called first to force the ISE to allocate a console and allow [Console]::OutputEncoding
to work; a plain chcp
works too.
Just use the new Windows Terminal. – Richie Bendall – 2020-01-16T13:01:01.493
@RichieBendall Obviously that wasn't an option when this question was asked, and still isn't and will continue not being one on several legacy systems. – rahuldottech – 2020-01-16T13:02:00.230
Correct. I added the comment to give this question a better future prevalence. – Richie Bendall – 2020-01-16T13:06:50.387