Development

[Krrishdhaneja]

@fm-sys would you help me up in this project?

[fm-sys]

If there is something specifically, I would help. But please describe in detail what the problem is. Over Christmas I will take a Github break but after that I am looking forward to a challenge 😉

[Krrishdhaneja]

Nah, I haven't commited that, but when I made that I included that file in .gitingnore.

[Krrishdhaneja]

Do you have Linux? @fm-sys

[fm-sys]

Do you have Linux? @fm-sys

Ne except a virtual machine

[fm-sys]

Hey, and I wanted to implement gTTS instead of pyttsx3, cuz the voice is much better, but it can only say one speak() command cuz it saves data to an mp3, and making multiple mp3s is not a good idea at all, so what should I do @fm-sys ?

>>> from gtts import gTTS
>>> tts = gTTS('hello')
>>> tts.save('temp_file.mp3')

and then

pip install python-vlc

>>> import vlc
>>> p = vlc.MediaPlayer("file:///path/to/temp_file.mp3")
>>> p.play()

...or any other library for playing

[fm-sys]

Nah, I haven't commited that, but when I made that I included that file in .gitingnore.

See https://stackoverflow.com/questions/1143796/remove-a-file-from-a-git-repository-without-deleting-it-from-the-local-filesyste for removing files from the repo

[fm-sys]

@Krrishdhaneja

By the way, you do not need to link users every time you write a comment. Project Owners and people who participate in the issue before automatically receive a notification. Linking them every time could be perceived as intrusive. (I saw you where also linking RobinLinus in the Snapdrop Repo in every comment. You can be sure that the Owners most probably will read your comments even without linking them)

[Krrishdhaneja]

Would be remebering next time for sure

[Krrishdhaneja]

Hey, should I now delete this conversation cuz there is Friday discussions already, what do you think?

[Krrishdhaneja]

Happy New Year @fm-sys !

[fm-sys]

But can you tell me how to do that?

Use these cmd commands in your project directory:

git reset --soft 08da87ce555794820e1788740ff1d872d44a6e7b
git commit --amend -m "The commit message you want"
git push --force

(08da87ce555794820e1788740ff1d872d44a6e7b is the commit hash of your initial commit)

The result should look like this. Be aware that your commit history will then only contain one commit, see: https://github.com/fm-sys/Friday/tree/squash_test

By the way, this is something you should really do only in really rare cases, where it is really necessary and nothing else is possible. Because all forks are no longer compatible with the repo after that and so on.

I also had to delete and recreate my fork. Fortunately I noticed it before I started with the GUI...

[fm-sys]

If something like this happens with the API keys again, and you notice it directly you should rather edit the last commit (you can do that with the "amend commit" button when committing in PyCharm)

[Krrishdhaneja]

If something like this happens with the API keys again, and you notice it directly you should rather edit the last commit (you can do that with the "amend commit" button when committing in PyCharm)

Thanks!

[Krrishdhaneja]

If something like this happens with the API keys again, and you notice it directly you should rather edit the last commit (you can do that with the "amend commit" button when committing in PyCharm)

Thanks!