diff options
| author | Wynn Wolf Arbor | 2020-07-15 10:57:48 +0200 |
|---|---|---|
| committer | Wynn Wolf Arbor | 2020-07-15 10:57:48 +0200 |
| commit | 3970744f9fba676d1a6253cae652941a804c9dfe (patch) | |
| tree | 611d7d4fad1e37ae6f721ed6bd17484f924b0457 | |
| parent | 4cc1d86beede1ff83f3abd8707ba8c8879ddab2a (diff) | |
| download | site-3970744f9fba676d1a6253cae652941a804c9dfe.tar.gz | |
posts: Update outdated URLs
| -rw-r--r-- | posts/debug-ncmpcpp-taglib.md | 8 | ||||
| -rw-r--r-- | posts/the-long-journey-to-cgit.md | 2 | ||||
| -rw-r--r-- | posts/weltschmerz.md | 2 |
3 files changed, 6 insertions, 6 deletions
diff --git a/posts/debug-ncmpcpp-taglib.md b/posts/debug-ncmpcpp-taglib.md index 2e17d81..4dcd4a2 100644 --- a/posts/debug-ncmpcpp-taglib.md +++ b/posts/debug-ncmpcpp-taglib.md @@ -4,7 +4,7 @@ author: Wynn Wolf Arbor I have a pretty extensive music library which I manage with [mpd(1)](https://www.musicpd.org/) and -[ncmpcpp(1)](https://github.com/arybczak/ncmpcpp). Whilst I would love to +[ncmpcpp(1)](https://github.com/ncmpcpp/ncmpcpp). Whilst I would love to find a standalone tag editor that is easily usable from the command line (or alternatively a nicely designed GUI one), ncmpcpp's built-in tag editor has always been enough for my needs. @@ -28,7 +28,7 @@ to my to-do list. Today I decided to look into this finally. First stop: the `ncmpcpp(1)` source code. I already knew that it used `taglib` to access and modify Vorbis comments, so I quickly found the [part of the -code](https://github.com/arybczak/ncmpcpp/blob/31ee76e8eee0cdc953f85d6c9369fb0aca010889/src/tags.cpp#L173-L199) +code](https://github.com/ncmpcpp/ncmpcpp/blob/31ee76e8eee0cdc953f85d6c9369fb0aca010889/src/tags.cpp#L173-L199) that was responsible for saving changes: ```cpp @@ -167,8 +167,8 @@ decided that it was a good idea to use work-in-progress code as a stable candidate for a package. Around the time I discovered this, someone else had already opened an -[issue](https://github.com/arybczak/ncmpcpp/issues/371) on GitHub. I +[issue](https://github.com/ncmpcpp/ncmpcpp/issues/371) on GitHub. I shared my findings and later opened a [pull -request](https://github.com/arybczak/ncmpcpp/pull/373). I am pondering +request](https://github.com/ncmpcpp/ncmpcpp/pull/373). I am pondering bringing this to the package maintainer's attention, but am not confident it will result in any positive change. diff --git a/posts/the-long-journey-to-cgit.md b/posts/the-long-journey-to-cgit.md index d5cc636..8360317 100644 --- a/posts/the-long-journey-to-cgit.md +++ b/posts/the-long-journey-to-cgit.md @@ -210,7 +210,7 @@ random instance on the internet. On the other hand, if I disable[^3] all the features I do not need, the 10% that remains of the whole of Gitea is not even that great. Barely worth putting in the effort of going through its one thousand line -[sample configuration](https://github.com/go-gitea/gitea/blob/master/custom/conf/app.ini.sample) +[sample configuration](https://github.com/go-gitea/gitea/blob/670db99f4fa26c9e97ce7945b61d9a6f20558634/custom/conf/app.example.ini) file. ### cgit diff --git a/posts/weltschmerz.md b/posts/weltschmerz.md index 0d46849..fd0f21c 100644 --- a/posts/weltschmerz.md +++ b/posts/weltschmerz.md @@ -21,7 +21,7 @@ terminal emulator for daily use. ([signature](/snapshots/weltschmerz/weltschmerz-1.3.0.tar.gz.SHA256.sig), [checksum](/snapshots/weltschmerz/weltschmerz-1.3.0.tar.gz.SHA256), [verify?](verify-with-signify), - [archive](/snapshots/weltschmerz)) + [archive](/snapshots/weltschmerz/)) - [Git repository](https://git.oriole.systems/weltschmerz) ## Requirements |