Wow; that’s very strange! I don’t see any clear reason why `sys.platform` would be *empty* on your machine. Maybe this is a question for Stack Overflow?
> On Mar 23, 2017, at 2:14 PM, Spiros C <[email protected]> wrote: > > When I had the normal beets version installed all the colours where fine > > Τη Πέμπτη, 23 Μαρτίου 2017 - 7:46:54 μ.μ. UTC+2, ο χρήστης Spiros C έγραψε: > > <https://lh3.googleusercontent.com/-KN1xQPBDCC4/WNQKAKt4ocI/AAAAAAAAACU/nZHn6qgbOXUn57LHGABobQwsRNRQ2Pr1ACLcB/s1600/%25CE%25A3%25CF%2584%25CE%25B9%25CE%25B3%25CE%25BC%25CE%25B9%25CF%258C%25CF%2584%25CF%2585%25CF%2580%25CE%25BF%2B%25CE%25BF%25CE%25B8%25CF%258C%25CE%25BD%25CE%25B7%25CF%2582%2B%2528132%2529.png>An > error > > Τη Πέμπτη, 23 Μαρτίου 2017 - 7:31:22 μ.μ. UTC+2, ο χρήστης Adrian Sampson > έγραψε: > It looks like your terminal isn’t interpreting ANSI color escape sequences, > and our detection that turns them off on Windows isn’t working. > > What’s the value of `sys.platform` on your system? For example, you might run > `python -c 'print sys.platform’`. > > A > > >> On Mar 23, 2017, at 1:06 PM, Spiros C <[email protected] <>> wrote: >> >> >> <https://lh3.googleusercontent.com/--BKbB-FmKuc/WNQAh6V3tYI/AAAAAAAAACE/Wke8aOOqKAEg4knkcKJjI5jwCj7FBlsAQCLcB/s1600/%25CE%25A3%25CF%2584%25CE%25B9%25CE%25B3%25CE%25BC%25CE%25B9%25CF%258C%25CF%2584%25CF%2585%25CF%2580%25CE%25BF%2B%25CE%25BF%25CE%25B8%25CF%258C%25CE%25BD%25CE%25B7%25CF%2582%2B%2528131%2529.png>Adrian >> I did what it says on the wiki and everything seems fine..But when I run >> the beet import command I got this: >> >> <https://lh3.googleusercontent.com/--BKbB-FmKuc/WNQAh6V3tYI/AAAAAAAAACE/Wke8aOOqKAEg4knkcKJjI5jwCj7FBlsAQCLcB/s1600/%25CE%25A3%25CF%2584%25CE%25B9%25CE%25B3%25CE%25BC%25CE%25B9%25CF%258C%25CF%2584%25CF%2585%25CF%2580%25CE%25BF%2B%25CE%25BF%25CE%25B8%25CF%258C%25CE%25BD%25CE%25B7%25CF%2582%2B%2528131%2529.png> >> >> >> Τη Τετάρτη, 22 Μαρτίου 2017 - 3:58:01 μ.μ. UTC+2, ο χρήστης Adrian Sampson >> έγραψε: >> We also have advice about installing an “editable” git checkout on the wiki: >> https://github.com/beetbox/beets/wiki/Hacking >> <https://github.com/beetbox/beets/wiki/Hacking> >> >>> On Mar 22, 2017, at 9:54 AM, Fabrice Laporte <[email protected] <>> wrote: >>> >>> So you have two copies of beets : one installed on your system, and the one >>> in the cloned repo. >>> To test your edits you want to run beets from your repo, like ./beet (the >>> "./" is important here) >>> >>> Le mercredi 22 mars 2017 13:48:33 UTC+1, Spiros C a écrit : >>> I have another question Adrian, >>> I installed beets with the pip install beets command and then i forked and >>> cloned the repo in my copmuter..I noticed that changing the code in the >>> cloned folder doesnt affect the program.. Where are the code files that I >>> have to interfere with, in order to change beets (which is installed in my >>> computer)?? >>> Thanks, >>> Spiros >>> >>> Τη Τετάρτη, 22 Μαρτίου 2017 - 2:00:58 μ.μ. UTC+2, ο χρήστης Spiros C έγραψε: >>> Thanks a lot Adrian!! >>> >>> Τη Τετάρτη, 22 Μαρτίου 2017 - 1:57:40 μ.μ. UTC+2, ο χρήστης Adrian Sampson >>> έγραψε: >>> That part of the code just sets up the pipeline; it doesn't actually do any >>> work. You may want to try modifying the code where the interactive prompts >>> occur, in commands.py. >>> >>> Adrian >>> >>> On Mar 22, 2017, at 6:45 AM, Spiros C <[email protected] <>> wrote: >>> >>>> Greetings, >>>> I am trying to fix my first issue on beets.. I chose this one: >>>> https://github.com/beetbox/beets/issues/2366 >>>> <https://github.com/beetbox/beets/issues/2366> >>>> I found out tha the bell sound can be generated by using this command: >>>> print('\a') >>>> I added this command in importer.py in line 308 like this: >>>> if self.config['autotag']: >>>> stages += [lookup_candidates(self), user_query(self)] >>>> print('\a') >>>> else: >>>> stages += [import_asis(self)] >>>> print('\a') >>>> >>>> However when I use the autotagger and I am asked to interact I hear >>>> nothing. What have I done wrong?? >>>> Thanks a lot, >>>> Spiros >>>> >>>> -- >>>> You received this message because you are subscribed to the Google Groups >>>> "beets" group. >>>> To unsubscribe from this group and stop receiving emails from it, send an >>>> email to [email protected] <>. >>>> For more options, visit https://groups.google.com/d/optout >>>> <https://groups.google.com/d/optout>. >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "beets" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected] <>. >>> For more options, visit https://groups.google.com/d/optout >>> <https://groups.google.com/d/optout>. >> >> >> -- >> You received this message because you are subscribed to the Google Groups >> "beets" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <>. >> For more options, visit https://groups.google.com/d/optout >> <https://groups.google.com/d/optout>. > > > -- > You received this message because you are subscribed to the Google Groups > "beets" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout > <https://groups.google.com/d/optout>. -- You received this message because you are subscribed to the Google Groups "beets" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
