DonutVeteran

joined 3 years ago
[–] [email protected] 2 points 3 years ago

I find personally that my current distro takes up barely any space compared to Windows and a few games only, so there's minimal overhead to having two operating systems on the same disk. On my current setup I have a single SSD dualbooting both operating systems; Windows is ~ 180 GB while my daily driver distro is a 20 GB partition, of which it currently takes up 10 GB of space. There's not going to be a lot of overlap in applications that you install on both systems, and it even helps you develop better habits. No more gaming when there's work to be done; you have to restart and boot into Windows to do that πŸ˜‰

Another thing to consider is that for all of the distros I've tried (not a lot), you can easily access files stored on your NTFS Windows partition. You can just mount it and access files there when you need them.

[–] [email protected] 4 points 3 years ago (3 children)

MicroG is an implementation of gapps, or a collection of Google-provided applications, frameworks, and services. Without it, it will be hard to run apps that depend on that support (most apps present in the Play Store); even if an APK of that app is downloaded it will not be able to work properly.

A free-as-in-freedom re-implementation of Google’s proprietary Android user space apps and libraries.

https://microg.org/

[–] [email protected] 1 points 3 years ago

No problem. Best of luck!

[–] [email protected] 1 points 3 years ago (2 children)

Did you run p10k configure after you changed the font? You should run it after you change the font. Afterwards, try updating GNOME terminal if the problem persists. You mentioned that you couldn't update it last time, was there a specific reason? I could help with that.

You could also try filing an issue on their Github and see if that gets you anywhere.

[–] [email protected] 1 points 3 years ago (4 children)

Try restarting the terminal application and zsh, if you haven't already, after changing the font.

I thought of something else too to try. Perhaps GNOME Terminal isn't rendering Unicode properly. Try setting the character encoding to UTF-8. Terminal -> Set Character Encoding -> UTF-8. If UTF-8 is already set, set it to a different encoding and then back to UTF-8.

[–] [email protected] 1 points 3 years ago (6 children)

I think it should be alright? It is compatible, maybe try updating GNOME Terminal though. The stable version should be at 3.x.x for most systems.

Try doing the below after you update, or if you can't update try it anyways, I guess πŸ˜‰.

GNOME Terminal (the default Ubuntu terminal): Open Terminal β†’ Preferences and click on the selected profile under Profiles. Check Custom font under Text Appearance and select MesloLGS NF Regular.1

And finally try running p10k configure if possible on your system.

[–] [email protected] 1 points 3 years ago (8 children)

No problem, glad it worked! For the symbols, try installing this font ("Meslo Nerd Font patched for Powerlevel10k") and see if it helps.

[–] [email protected] 1 points 3 years ago (10 children)

This thread provides a "manual installation method" you could try before attempting to manually download (as things could go wrong):

git -C ~/.oh-my-zsh/custom/themes/powerlevel10k pull
~/.oh-my-zsh/custom/themes/powerlevel10k/gitstatus/install -f

So in your case, you could modify this to update your powerlevel10k and then run the install script:

$ git -C zsh_dir/custom/themes/powerlevel10k pull
$ zsh_dir/custom/themes/powerlevel10k/gitstatus/install -f

The install script can be found here on Github, which also provides clues to how gitstatusd is fetched: it's actually a binary executable that is placed in a cache directory by the install script. This cache folder is referenced as "${GITSTATUS_CACHE_DIR:-${XDG_CACHE_HOME:-$HOME/.cache}/gitstatus}". So, probably your Cygwin home folder/.cache/gitstatus should be where you should try to extract gitstatusd manually.

[–] [email protected] 1 points 3 years ago (12 children)

Ok, sorry for the late response. Looking through the logs, it seems that the problem may be curl somehow failing to fetch gitstatusd. The script tries fetching gitstatusd-linux-x86_64.tar.gz at several mirrors, from what I can gather, and all of them fail.

This might be because curl itself is not working. I recall that there were reports of curl not working on Cygwin which I read about somewhere, and Cygwin seems to be what you're on. I'd check if you can run the curl commands used in the logs manually to fetch the resources at those URLs. So try running:

curl -q -kfsSL -- https://gitee.com/romkatv/gitstatus/raw/release-v1.3.1/release/gitstatusd-linux-x86_64.tar.gz

Or:

curl -q -kfsSL -- https://github.com/romkatv/gitstatus/releases/download/v1.3.1/gitstatusd-linux-x86_64.tar.gz

Or any one of those mirror links in the logs, and see what happens.

[–] [email protected] 2 points 3 years ago (14 children)

Hmm, you might have to edit the config file ~/.zshrc and add the GITSTATUS_LOG_LEVEL=DEBUG parameter for further output about the specific part of "initialization" that failed. Otherwise, it's hard to determine what exactly happened.

[–] [email protected] 5 points 3 years ago (2 children)

I tried it and it works great πŸ˜„

However, for others trying the script, if youtube-dl throws an error when searching for videos suggesting to update it, update it! Yes, I figured that out...

Debian/debian variant users can use backports if their stable version is already fully updated: apt -t buster-backports install youtube-dl fixed the error for me. Of course, this is a youtube-dl issue, not a problem with the script.

[–] [email protected] 7 points 3 years ago (3 children)

Looks cool! I'll be sure to check this one out

view more: β€Ή prev next β€Ί