Github messages for voidlinux
 help / color / mirror / Atom feed
From: gorecki3 <gorecki3@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: VLSub not automatically loading subs
Date: Sun, 16 Jul 2023 18:10:25 +0200	[thread overview]
Message-ID: <20230716161025.1ZKn5LKl5s8T0gFnSCKU82K3nWoAL3GxO78yNgbuN7U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-45045@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 680 bytes --]

New comment by gorecki3 on void-packages repository

https://github.com/void-linux/void-packages/issues/45045#issuecomment-1637129191

Comment:
>Is this the issue you're facing?: https://reddit.com/r/VLC/comments/phwhau/vlsub_0111_not_working/

Yes 

>Of course, this workaround was meant for windows. Maybe other distros have applied patches on their own, which is why VLSub fails on Void Linux?

oh good point, i forgot about that.

 >Where did you get vlsub 0.11.1?

i simply installed Vlc, it comes with vlsub.

i have also tried different versions of vlsub on void linux but none of them worked, but I'll see if i can find a workaround, thank you for replying 


  parent reply	other threads:[~2023-07-16 16:10 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14 21:42 [ISSUE] " gorecki3
2023-07-15  3:18 ` gorecki3
2023-07-15 14:08 ` TeusLollo
2023-07-16 16:09 ` gorecki3
2023-07-16 16:10 ` gorecki3 [this message]
2023-07-17 20:41 ` TeusLollo
2023-07-18  0:06 ` gorecki3
2023-07-18  1:26 ` TeusLollo
2023-07-18  1:28 ` TeusLollo
2023-07-18 12:40 ` gorecki3
2023-07-18 12:42 ` gorecki3
2023-07-18 12:47 ` gorecki3
2023-07-18 12:47 ` gorecki3
2023-07-18 13:10 ` TeusLollo
2023-07-18 13:10 ` TeusLollo
2023-07-18 21:37 ` gorecki3
2023-07-18 22:06 ` gorecki3
2023-07-18 23:30 ` TeusLollo

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230716161025.1ZKn5LKl5s8T0gFnSCKU82K3nWoAL3GxO78yNgbuN7U@z \
    --to=gorecki3@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).