If I remember right those are like vr helmets that allow them to see themselves in third person or something like that
Sorry if it comes out robotic, since I don't use stow myself I just opened the manual and parsed it for you.
You manually create the repo of packages ONCE and then use stow to deploy them without having to link stuff manually every time.
As for "what's it doing for me", stow is just a generic deployment script that somebody else has written for you. You can just as well create your own and do it your way.
I personally used to have a bash script with one custom function "symlink" that error checked the linking process and a list of target/destination under the function.
Now I'm trying to code a python script similar to stow that works with packages of configs but instead of recreating paths inside the package you just provide a json file with target/destination for each file in the package.
Both of my ways have same shortcoming as stow: you have to do some manual work before the script can kick in.
Hopefully my messages have been helpful.
Recreating a path to original locations is a way to configure stow.
You can utilize bash to automate it. Mkdir can create entire trees in a single command.
After links were created you start using your configured software.
It's a link farm built using a packaging system. You put your configs into a "package" and then link said package where it belongs.
Git is useful not as a combination for stow, but a standalone way to version control your configs.
For nonidentical devices you create additional packages prefixed with specific device name. You don't need to link all packages at once with stow, pass a name of a package to link it alone.
Idk I'm so used to working in terminal I don't really notice that. For my eyes, it's smooth enough
There are gpu accelerated terminal emulators... Not sure what you mean by remote development though.
Usually people prefer seeing beautiful things.
However deviant things like this, in my opinion, are like breather of fresh air once in awhile.
Would certainly like to see more.
Unfortunately I'm afraid they're lost (I think). UPD: see kolorafa's comment
There's some alternatives if you're willing to continue with that:
Aves Gallery on android (is on fdroid) can embed comments into image long term metadata. But I have not tested it after transfer.
Creating a directory Gallery with markdown files and a subdir for all images and then writing comments inside those markdown files with a link to the local image. Very simple to do with Obsidian or similar markdown-powered software.
Out of the top of my head I can think of two structures for that:
-
/Year/month/day/ dirs, hoursminutesecond.png and hourminutesecond.txt with the comment per photo.
-
/Gallery/images/datetime.png and /Gallery/yearmonth_gallery.md with comments and links to multiple images for that month.
And probably more that I'm not aware of myself.
If that comment is true and you don't have the database anymore then there's no hope.
If you were writing comments to understand which file is which then consider a directory scheme for sorting your files and add readme.md files in a narrow category of files to describe them. I do something like: All coding projects go into home/code, each project has a readme. Etc.
If you were just logging for history purposes ie good memories in photos I'd suggest just making a markdown gallery. Or something similar.
Because windows is inconvenient for me.
Nothing works as I expect it, terminal takes ages to open, everything lags like shit, annoying popups everywhere, every setting is hidden behind ten thousand menus, subpar packaging system, explorer crashes every so often, PATH is hard to access and modify, takes a PHD to install a raw compiler without visual studio, you can forget about shortcut system cus even with autohotkey it's a pain.
(Talking about permissions) Why do I have to write names of users from the ground and then click button "check if it actually exists" in a fucking gui? Couldn't there be a drop down list?
If you ever want to modify the windows iso image or make an automated script without using online services you're just done mate. There's nifty surprises like special software which name I so conveniently forgot (God bless) that can open the file image contained inside the iso image, but if that inner image has wrong format you have to spend time converting it. Then you'll see some fucking insane shit in front of you, where you need to drag objects from a drop down list into different categories that have random ass names and not at all simple to understand even after reading official documentation. Oh you think that's all? You can drop same objects into different categories and they will do different shit. I took TWO WEEKS WORTH OF CLASSES to work with that software and I ALREADY DONT REMEMBER JACK.
Then there's utterly long startup times even on ssds, colemak dh mod basically doesn't exist... And that's all I could remember out the top of my head.
The only redeeming quality I'd say, is having a very simple setup for Japanese and Chinese IME. On arch KDE it took me awhile to set up fcitx with mozc the first time around.
You can install any app anywhere by hand. Download binaries, put them anywhere you want for example home/.local/bin and add that location to your PATH. Most package managers install apps system-wide ie somewhere in root.
Don't give her pointers, she will delete them and leave you with a core dump