boomzilla

Thanks. I somehow straight-up ignored gitattributes and can't recall to have seen them in projects. Glad that's past tense now and I will add presets from your link where appropriate (If I remember it). Never had conflicts with windows users on linux based repos but I suspect thats VSCodes merit in keeping the files as-is.

The two commands in your post are not mentioned in the linked repo-readme but instead in the github docs (see [1]).

I know git reset only from dealing with a detached HEAD. I did not understand the situation as well as the git reset command. Both is explained very good in [2].

So here's the gist of my research (possibly wrong).

Before you even add the .gitattributes file you should add all unstaged changes, commit & push them. To quickly revert back when things go wrong: zip the whole project.

git rm --cached -r: Normally git rm would remove a file from the filesystem in addition to the repo but the --cached says to only remove/untrack the file from the repo (what's inside the .git dir). Recursively removes every file. Cleans the current staging area too. So at this point you'd have to do git add again for every file but you wouldn't have lost any uncommitted changes in the working dir.

Now for the dangerous part:

git reset --hard This resets the HEAD to the most recent commit (and cleans the staging-area/index which was already done in the in git rm) and in addition possibly overwrites many unstaged/uncommitted changes with the files contents from the last commit.

So to end this novel. If you havent commited everything before executing the commands your in for a bad time. As far as I see it.

[1].

[2]

Rejoice folks. I think I found a retoot on Mastodon. Direct image-links should work as it's all within the fediverse, right?

This helps for sure. And this. Those pesky coyotes seem get along also too well. Time for some harvesting (sic!) and then get out those ARs and gatlings we still have some boar families to massacre.

Yes there are singular cases where wolves can change a whole ecosystem for the good, but what about muh crops and livestock.

It's been nearly 4 years since I last used Manjaro and I had that error quite often around ever ½-¼ a year in my 2 years of Manjaro. iirc to resolve it I had to uninstall the current nvidia driver > restart without driver > install supported kernel > install driver. Don't know what I did wrong tho.

Manjaro did otherwise a good job to keep the sys together.

What bugged me a bit was the painfully long retention of the big KDE updates. At that time KDE was making big QOL leaps and quite a few distros had those updates already. But I could also live with that.

In the last month of my time with Manjaro a few Proton games dropped frames heavily and that's the end of the story. Made the switch to Arch and never had probs with nvidia again, apart from when new Steam UI came out.

Ah thanks for letting me know. Scrambled sounds dire. Spreadsheets or documents?

Thought the devs nailed it pretty good. At least I never saw differences in my not overly complicated letter layouts when I opened them in MS Office.

Though I had your use-case just with a few rather simple spreadsheets I got from colleagues for me to modify and send back, they never complained.

Anyways I'm glad I don't have to do with office products very often but I'll look into OpenOffice as well. Looks indeed very good. Like a streamlined and modern MS Office without ribbons.

OnlyOffice is mentioned so rarely but it has an UI much more resembling the ribbon based MS Office and in my experience a good compatibility with docx and xlsx files. Don't know what's happening when confronted with macro-monsters though.

Downgrading seemed really easy to me with the mentioned downgrade script. With the IgnorePkg option in pacman.conf it won't get updated. I did it with nvidia drivers when Steam pushed their new UI and nvidia drivers weren't ready for that.

What's dissapointing about the fix? Does its job or not?

yay SEARCHTERM

It spits out all the packages with SEARCHTERM in its name or description. The packages are listed like "REPO/PACKAGE" , where REPO tells you if it's from the official repos (core/extra/multilib) or from the AUR.

Then pick the number of the package from the list and that's it.

If you want to update all your packages, even the AUR ones just enter yay and press enter on the follow-up questions. If you update with pacman -Syu then AUR packages won't get updated.

Also Octopi is a nice frontend for yay and pacman. Not as fancy as Discover or Pamac but it does its job well.

I just installed Nextcloud on Arch and the official packages caused the most headaches I ever had within my 3 years of arch. In contrast I installed the official Jellyfin and Prometheus Server packages and they ran OOTB.

I ended up with not using the official packages but extracting the tar.bz2 into /var/www/nextcloud and slightly modifying the nginx config from their site. I had to move the inclusion of the MIME-Types file to a different block for nextcloud to deliver its CSS, SVGs and images. It wasn't exactly straight-forward too considering permissions. I found it a beast compared to many other server software.

From my experience (2 years Manjaro, 3 years Arch) it's the other way round. Manjaro presented me with a terminal way to often after Nvidia updates. Never had that on Arch. Especially the Nvidia updates are very reliable. I don't know what people do with their Arch installations. Mines rock-solid for the 3 years now. Possibly the most stable distro I ever used.

But I understand that you just can't advise newbies to install Arch, even when archinstall is relatively easy to use. Maybe EndeavourOS which brings a lot of convenience features and a graphical installer to the table. A fellow linux newb is running it without problems for a year now.

That's not just YT. A lot of services and apps (e.g. amazon or xitter) you're logged into and share links from add parameters (stuff behind the questionmark) to the link that identify in the end who has shared it.

Try to shave off as much as possible from a shared link and test if it still works. To get a feel for what you can delete from the link, try to navigate to the destination (e.g. YT-video) inside a browser with which you're not logged into that service and which has preferrably cleared its history, cache etc. Then compare the link from that browser with the one from the browser you're logged in with.