 | Mike Verhagen on geerlingguy/my-backup-plan: Ho… |
 | Attila Kovacs on docs.embarcadero.com unreachab… |
 | David Blue on MacOS: converting a man page t… |
 | jpluimers on How do I pretty-print JSON in… |
| jpluimers on Delphi 10.2 Tokyo Godzilla ISO… |
Posted by jpluimers on 2023/03/21
Will need this one day to gain better insight on how git works under the hood: [Wayback/Archive] git add a revision before first commit – Google Search
–jeroen
Posted in Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2023/03/08
This revealed so much pain: [Wayback] gist include image in markdown in current directory – Google Search
I wished that – like in the past – it would work just like in a normal github hosted git repository: [Wayback/Archive] How do I display local image in markdown? – Stack Overflow.
The core problem is that though a gist underneath is a git repository, it is rendered in a way that is different than a github repository is rendered, and that way of rendering has changed over the years effectively making it difficult to embed a picture. When you do embed an image requires the uuid/guid of the raw image URL to be included in the markdown, unlike with a regular repository hosted on github.
That is so much pain that I decided to not host documentation in gists any more.
A bit of the pain:
This is an example gist where I tried to host an image: [Wayback/Archive] Windows 7 with PowerShell v2 fails to upgrade to PowerShell v3 through chocolatey: You must provide a value expression on the right-hand side of the '-' operator.
That gist was prelude to my post Chocolatey on Windows 7: “You must provide a value expression on the right-hand side of the ‘-‘ operator.”.
–jeroen
Posted in Development, DVCS - Distributed Version Control, gist, git, GitHub, Lightweight markup language, MarkDown, Software Development, Source Code Management | Leave a Comment »
Posted by jpluimers on 2023/01/23
README.md with Markdown describing your profileREADME.md, add begin/end HTML comment markers <!-- and --> for various types of dynamic contentYou can spice this up with all kinds of badges to make it look pretty.
Yes, it is indeed odd to have HTML comments in Markdown where you could just as easy use Markdown comments, but hey: I didn’t define the way this works.
A Markdown comment looks like this:
(empty line) [comment]: # (This actually is the most platform independent comment)
For explanation on why/how this works, see the below two great StackOverflow answers in this order:
The below two videos (also embedded below the signature) show how to do this. Thanks [Archive] Jesse Hall 🦸♂️ #vsCodeHero (@codeSTACKr) | Twitter for creating them!
The description of the videos contain all sorts of links to sites and underlying repositories for:
You can see the effects at [Wayback/Archive] codeSTACKr/codeSTACKr in the [Wayback/Archive] raw README.md sources.
Enough to get you some experimentation (:
One of the drawbacks of mixing manual and automated changes to a repository, is that the automated changes can cause a lot of commits.
This is OK as long as the automated changes add value to the changed content.
In this regard, having stable RSS feeds is important, and YouTube is kind of bad at this when you look at [Wayback/Archive] History for README.md – codeSTACKr/codeSTACKr: videos changing order or popping in/out of the last 5 is kind of annoying.
–jeroen
Posted in Development, DVCS - Distributed Version Control, git, GitHub, GitHub Actions, Lightweight markup language, MarkDown, Power User, Source Code Management | Leave a Comment »
Posted by jpluimers on 2022/12/01
With [Wayback/Archive] rawgit.com having sunset years ago, but still having a [Wayback/Archive] few links to it from my blog, it was time to take a closer look at the alternative [Wayback/Archive] htmlpreview.github.io.
First of all, htmlpreview needs more examples. I might submit a pull request for it later, as it is open source at [Archive/Archive] htmlpreview/htmlpreview.github.com: HTML Preview for GitHub Repositories.
Second, some actual example URLs, based on content I previously accessed through rawgit.com.
Posted in Development, DVCS - Distributed Version Control, git, GitHub, HTML, Power User, rawgit, Software Development, Source Code Management, Versioning, Web Development | Leave a Comment »
Posted by jpluimers on 2022/09/29
If you ever come across git hanging after completing “Resolving deltas: 100%“, then remember this can still happen with recent git versions; the below output was with git version 2.24.1.windows.2.
C:\bin>git clone https://wiert@gitlab.com/wiert.me/private/Windows/bin.git Cloning into 'bin'... remote: Enumerating objects: 74, done. remote: Counting objects: 100% (74/74), done. remote: Compressing objects: 100% (54/54), done. remote: Total 1063 (delta 30), reused 39 (delta 15) Receiving objects: 100% (1063/1063), 26.74 MiB | 516.00 KiB/s, done. Resolving deltas: 100% (385/385), done.
or (after pressing Ctrl-C):
C:\bin>git clone https://wiert@gitlab.com/wiert.me/private/Windows/bin.git Cloning into 'bin'... remote: Enumerating objects: 74, done. remote: Counting objects: 100% (74/74), done. remote: Compressing objects: 100% (54/54), done. remote: Total 1063 (delta 30), reused 39 (delta 15) Receiving objects: 100% (1063/1063), 26.74 MiB | 516.00 KiB/s, done. Resolving deltas: 100% (385/385), done. fatal: index-pack failed
Sometimes this is as easy as waiting until the remote system comes to its senses. In this case, waiting some 8 hours resolved it:
C:\bin>git clone https://wiert@gitlab.com/wiert.me/private/Windows/bin.git C:\bin>git clone https://wiert@gitlab.com/wiert.me/private/Windows/bin.git Cloning into 'bin'... remote: Enumerating objects: 74, done. remote: Counting objects: 100% (74/74), done. remote: Compressing objects: 100% (54/54), done. remote: Total 1063 (delta 30), reused 39 (delta 15) Receiving objects: 100% (1063/1063), 26.74 MiB | 748.00 KiB/s, done. Resolving deltas: 100% (385/385), done.
In my case this worked, even though GitLab did not show any problems in their status history: [WayBack] GitLab System Status History.
I waited (and succeeded) because of [WayBack] git – How to solve’fatal: index-pack failed’? – Stack Overflow.
Some links that I want to check out later:
When it hangs, just kill the process with Ctrl+C and run this command in repository folder:
$ git fsck notice: HEAD points to an unborn branch (master) Checking object directories: 100% (256/256), done. Checking objects: 100% (3298/3298), done. notice: No default references dangling commit 2916d1238ca0f4adecbda580ef4329a649fc777cNow just merge that dangling commit:
$ git merge 2916d1238ca0f4adecbda580ef4329a649fc777cand from now on you can enjoy repository content in any way you want.
Likely workaround[4] that doesn’t require git update:
Since the pack files have been downloaded correctly all you need to do is to interrupt the process with Ctrl+C, do a git fetch to fetch branch information from the remote repository and checkout the master (or any other) branch again with a git checkout master.
- Interrupt the git process that hung on resolving deltas with
Ctrl+C- Fetch branch information with
git fetch- Checkout the master branch (or any other branch) with
git checkout masterThis made git set up my branch master to track remote branch master and unpack the files correctly while also preserving branch information.
–jeroen
Posted in Development, DVCS - Distributed Version Control, git, Software Development, Source Code Management | Leave a Comment »
The Wiert Corner - irregular stream of stuff 