summaryrefslogtreecommitdiffstatshomepage
path: root/posts/debug-ncmpcpp-taglib.md
diff options
context:
space:
mode:
Diffstat (limited to 'posts/debug-ncmpcpp-taglib.md')
-rw-r--r--posts/debug-ncmpcpp-taglib.md8
1 files changed, 4 insertions, 4 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.