mastodon.xyz is one of the many independent Mastodon servers you can use to participate in the fediverse.
A Mastodon instance, open to everyone, but mainly English and French speaking.

Administered by:

Server stats:

812
active users

#windowsterminal

0 posts0 participants0 posts today

[screenreader users, the following contains a lot of non-alphabet characters]

Fix/Workaround for me - still interested in info:
SendEnv LANG LC_* in my *local* .ssh/config

ls output is now 'Árstíðir - Hvel' etc etc

Update:
I am going to point towards #tmux and #WindowsTerminal here too, I can paste "Árstíðir - Hvel - 12 Unfold.flac" but touching a file with UTF-8 characters causes the same issues.

#PuTTY displays it correctly! The only difference I can see is that LANG="en_AU.UTF-8" is exported.

#Linux friends, what do I do with a filename like "''$'\303\201''rst'$'\303\255\303\260''ir - Hvel - 12 Unfold.flac'"? (arstidirsom.bandcamp.com/album if you're wondering)

The correct, or original filename from the zip file is "Árstíðir - Hvel - 12 Unfold.flac"

If I set LANG to something with UTF-8, I get _rst__ir - Hvel - 12 Unfold.flac, but ls *12\ Unfold.flac does not find it.

What's the equivalent of hexdump for filenames? This particular example is on ZFS but I have seen the same on ext4 and btrfs so I am sure it's not (entirely) filesystem specific.

If you search for this answer, what keywords did you use? I am having trouble here.

@DHowett Duuuuuuuude. I've been using a Mac for a bit, and one of the things that I have wished for in #WindowsTerminal

SINCE.
DAY.
ONE.

was the same "Broadcast Input to All *" feature that iTerm2 has.

And I completely missed that that feature has been in WT since 1.19!! 🤯

Two things to say on that:

First - THANK YOU!!!

Second - see media3.giphy.com/media/v1.Y2lk

Lilbits: Open Source PebbleOS progress and ARM doesn’t plan to terminate Qualcomm’s license agreement (for now)

Windows laptops powered by Qualcomm’s Snapdragon X chips began to hit the streets in 2024 and while they might not live up to all the promises from Qualcomm, Microsoft, and PC makers, they are the first ARM-powered Windows PCs with processors fast enough to rival chips from Intel, AMD, and Apple.

But the future of these chips has been in doubt for some time. The Oryon CPU cores at the heart […]

#android #arm #armVQualcomm #billetLabs #chips #EricMigicovsky #grf #lawsuit #lilbits #longevityGrf #nuvia #osUpdates #pebble #pebbleos #qualcomm #qualcommVArm #snapdragonX #steampunk #windowsTerminal

Read more: liliputing.com/lilbits-open-so

This week in the #WindowsTerminal:

Our team's been hard at work to get #Terminal Chat hooked up with #GitHub #Copilot. Now you can just use your existing copilot subscription to use it directly in the Terminal. No more needing to go through a contrived Azure OpenAI signup.

github.blog/changelog/2024-10-

(yall know I'm not a huge fan of #ai features these days, but I've got talented coworkers who worked hard to make this happen, and I'm gonna help support them because they deserve it)

The GitHub BlogGitHub Copilot is now available in Windows Terminal · GitHub ChangelogGitHub Copilot is now available in Windows Terminal
Replied in thread

@mcc If you install "Windows Terminal" github.com/microsoft/terminal and
1. set it to be the default terminal application (Settings > "Startup" > "Default Terminal Application")
2. edit the default profile to Never close automatically" (Settings > "Defaults" > "Advanced" > "Profile Termination Behavior")

I believe that should stop those pop-up terminals from disappearing.

Should. There are probably like 3000 ways for windows apps to pop up a terminal

Here's a demo