Tremendously useful
Happy to see the plugin get a new lease on life from an active and engaged developer. I only use a small portion of the features (suggested local tags), but this features alone makes it one of the most useful plugins for me.
Happy to see the plugin get a new lease on life from an active and engaged developer. I only use a small portion of the features (suggested local tags), but this features alone makes it one of the most useful plugins for me.
Thanks for keeping Simple Tags alive!
Simple Tags is great in picking exact local tag matches from the post text, but with Finnish (and probably some other languages as well), inflection often causes it to miss relevant suggestions (from Local tags). For instance, when using the inessive case ”Helsingissä” in the post, Simple Tags won’t suggest (previously added local tag) ”Helsinki”.
A fuzzy matching feature would help here.
While Simple Tags’ future was in limbo, I tested some other plugins, and one of them (maybe Smart Tag Insert) had such a feature: it showed related tags using some kind of fuzzy matching. I have no idea how difficult this feature would be to incorporate into Simple Tags though.
I know I can show all tags with the ”Click tags” feature, but with close to 2000 pre-existing tags, the full list is quite unwieldy.
This doesn’t work with hidden files in Bash, unless you shopt -s dotglob first.
The version I’m using:
yle-dl 20200807 with wget 1.20.3 (in Ubuntu 20.04)
Steps to reproduce:
$ /usr/local/bin/yle-dl -qq --backend wget --wget /usr/bin/wget https://areena.yle.fi/1-50636796
What I expect to happen:
For the download to complete without any output in the terminal.
What happens instead:
The command outputs this line (which to me seems like is from wget):
2020-09-25 17:25:27 URL:https://ylekaod-a.akamaihd.net/s/p/1955031/sp/195503100/serveFlavor/entryId/1_ldivkmki/v/11/ev/2/flavorId/1_b6wtzy8f/name/a.mp3?__hdnea__=st=1601043921~exp=1601058321~acl=/s/p/1955031/sp/195503100/serveFlavor/entryId/1_ldivkmki/v/11/ev/2/flavorId/1_b6wtzy8f/name/a.mp3*~hmac=bddcd801a98d3560990842beccee528da3861e588cf3438880642267aab03dc4 [21436961/21436961] -> "Kaverin puolesta kyselen: Koppuraiset kalsarit ja muita deittimokia-2020-09-25T06:45.mp3" [1]
This is still an issue; a newer (and still open, as of writing this) issue number for reference: #4312
Tuulenkaatoja kuntoradan Hiukkavaara–Auranmaja-välillä.
I’m up for testing those packages. Would Github allow you to attach a deb to a comment here (perhaps wrapped in a Zip file)?
@Gilles’SO-stopbeingevil’ Ok, it was just my misunderstanding then; I interpreted the quote as meaning ”you should quote RHS regular expressions”.
”Except that you do need double quotes where a pattern or regular expression is expected: on the right-hand side of = or == or != or =~.” Perhaps I’m misunderstanding this, but AFAIK, a RHS regular expression (i.e. after =~) should always be unquoted (since Bash 3.2 at least).