I really hope I don't misremember it being cross-platform.
I really hope I don't misremember it being cross-platform.
Jmispaste sorry
AAh hehe. Sadly I am not sure anymore. May have mixed it up with PowerShell (their shell) which definitely went cross-platform. It's been 3 years since I last looked at Windows.
AYouTubeWindows Developer
Windows Terminal is an application for users of command-line tools and shells like Command Prompt, PowerShell, and Windows Subsystem for Linux (WSL). Learn about its main features, customized schemes and configurations, and more: https://docs.microsoft.com/en-us/windows/terminal/?WT.mc_id=onedevquestion-c9-niner.
Jthe UI and UX though, for sure I think it should look like that
ALook how sexy it is.
AI loved having that "+" menu with every shell/tool in one window.
Jlike, if it was just a direct clone and those were distroboxes, it'd be awesome. Of course, with our own ideas too and then it'd be perfect
1it's not cross-platform
Jif you know anyone that knows vala we could just do it in Blackbox
AThen the hunt is on to find something for Linux like this.
Jlike, blackbox is perfect default bling (for the GNOME people)
AAgreed, blackbox is a great project.
JGitHub
Terminal emulator for use with Toolbox. Contribute to allisonkarlitskaya/boxi development by creating an account on GitHub.
JActually, let me move Exo out of the gdoc and into proposals
AWoah! That's literally the idea. Had you seen that before? 
AAIt's using 1 launcher icon per container though, so no seamless tabbing sadly.
AAI got as far as
flatpak run dev.boxi.Boxi --help and seeing the -c <name> flag to enter a named container, which calls the toolbox binary as '['flatpak-spawn', '--host', 'toolbox', 'run', '--container', '<name>', 'env', '-0']'. I think we're supposed to figure that out and make our own .desktop files for each container. So not much better than manual Tilix profiles like I've done.
Ahow would you guys feel about adding pcsc-tools ?
AAit is debugging tools for smartcards (yubikeys and stuff)
AVery niche. Can they run in a distrobox by exporting the binaries to the host?
AMmm maybe, it needs to talk to the host pcscd
AI'll give that a try and probably just add it to my image
Bwindows terminal doesnt work on linux
A@bsherman Were you using dconf-editor too? I can't remember. I've fixed the Flatpak's bug now. It can now see all host schemas too. So my previous lamentation that we had to layer
https://github.com/flathub/ca.desrt.dconf-editor/pull/24
Relief.
Edit: Oh by the way, it's exactly 1 year on the day since the original bug report was filed about this by someone, lol.
dconf-editor natively is no longer gonna be the case after this is merged:https://github.com/flathub/ca.desrt.dconf-editor/pull/24
Relief.
Edit: Oh by the way, it's exactly 1 year on the day since the original bug report was filed about this by someone, lol.
B@j0rge what dp you think about using web tech(electron+xtermjs) for exo 
:). on my laptop i keep just essentially using vscodes embeded termional since its the only one that i tried that actually doesnt suck with touch
:). on my laptop i keep just essentially using vscodes embeded termional since its the only one that i tried that actually doesnt suck with touchB JI think people would dunk on it
Jbut me personally, I wouldn't care as long as it works well
Jso like, whoever shows up first?
Blets be clear i cant write that me and javascript dont go together all that well
Bhonestly people should get over all the disgust with electron it doesnt make all that much sense
Jyeah I'm not picky on implementation because I just want to see if the model works. if it's a great idea people will put it in terminals, if not then we have this, I'm just tired of doing like console profiles and stuff
Bme too
Aime all web-based terminals add more latency than they should tbh but I've been using code-server at work as my main shell and it is mostly ok
Abut vs code doesn't support ligatures and it is still a less responsive than iterm2 
AKonsole is the best all around terminal I've found
AI just found the exact mechanism: It's not on app launch. Instead,
So if you wanna be sure a user has it for Flatpaks before updates, you can ensure that your yafti first boot runs:
flatpak updateSo if you wanna be sure a user has it for Flatpaks before updates, you can ensure that your yafti first boot runs:
PYeah, it'll also install it when you install a gnome flatpak (which is how I discovered it) with the system theme set.
ASurprisingly not.
ASo it seems to behave the same as nvidia/amd drivers: Installed on
flatpak updateOh maybe it's because you're installing things as system flatpaks? I definitely had it auto install the theme flatpak when I installed another flatpak
AExact same result if I do --user instead. No theme.
AActually, wow, even though I said "no" to installing it during
So I can't test the thing you're saying. ^^ It's glued in there now. So there's a good chance that you're right that it installs itself during
flatpak updateSo I can't test the thing you're saying. ^^ It's glued in there now. So there's a good chance that you're right that it installs itself during
flatpak install <something else> too.AYikes, dconf-editor as Flatpak was totally unusable. It was showing the wrong data (Flatpak environment's rather than the host's) and was unable to see the host environment at all. RIP to anyone who was using it:
https://github.com/flathub/ca.desrt.dconf-editor/pull/24
https://github.com/flathub/ca.desrt.dconf-editor/pull/26
Pretty amazing how those bugs escaped notice for 2111 days (first Flatpak release was on Aug 4, 2017).
https://github.com/flathub/ca.desrt.dconf-editor/pull/24
https://github.com/flathub/ca.desrt.dconf-editor/pull/26
Pretty amazing how those bugs escaped notice for 2111 days (first Flatpak release was on Aug 4, 2017).
AKind of an important tool for everyone building new defaults for immutable distros! 
A@hermmm and I are trying to figure out an appropriate name for a special branch on the
The layout will be:
-
-
We need a name for
Names that have been considered and rejected:
-
-
-
-
Uncertain names:
-
Leading names (clearest names so far):
-
-
startingpoint repo:The layout will be:
-
template-
<something>: The ONLY branch that gets deployed (published) to GHCR. All other branches will merely build but won't deploy. This ensures total control over GHCR publishing.We need a name for
<something>.Names that have been considered and rejected:
-
deploy or deployment: Very accurate names but also very ugly word.-
public-
release-
production: Strange name.Uncertain names:
-
customLeading names (clearest names so far):
-
publish: The only branch that is published to GHCR.-
live: The branch that goes live (deploys).
XI like live, it's a noun but implies the same thing
