dline not running - Githubissues

NatTupper / dline

A feature-rich terminal discord client

GNU General Public License v3.0

63 stars 4 forks source link

dline not running #9

Closed mgarbvs closed 5 years ago

mgarbvs commented 5 years ago

OS: Linux/Debian Terminal: urxvt, xterm Font: ubuntu Python Version: 3.7 How to reproduce: For me, it just involves running dline. For some reason, when I run dline, it does not work. It stops working at the Starting... part of the startup.

mgarbvs commented 5 years ago

I got it to work, all I needed to do was make a new skeleton

NatTupper commented 5 years ago

Not having a skeleton should still work. Was it an old skeleton?

Alumniminium commented 5 years ago

not having a skeleton didn't work for me either, had to copy one first.

NatTupper commented 5 years ago

I'll look into it. Thanks.

Nevexo commented 5 years ago

I'm having the same issue, it's just hanging at "Starting..."

Tried 3.6 & 3.7 + with & without config.

NatTupper commented 5 years ago

Sorry for the wait. I'm unable to replicate the issue. dline should work without a config file. If the config file is not present, it will use the default values from the res/settings-skeleton.yaml. If there is a config file but it doesn't have all values present in the skeleton, it will use the settings defined in the user config and fill in the missing ones from the skeleton.

A common cause that might be causing the issue arises when you don't have a config and you aren't joined to the dline discord guild or you have a config and you aren't joined to the default_server specified in the config. If these causes sound like they could be causing the problem, fix it by either joining the dline discord guild if you don't have a config or changing the default_server setting in your existing config.

If the above does not work, please post your config and whether you're joined to the dline discord guild. Please note that the default_guild setting is case sensitive. In the future, I plan to eliminate the need for this setting to be set, but for now, that's how it works.

NatTupper commented 5 years ago

Looking into the config problem as of today.

NatTupper commented 5 years ago

Could not reproduce the issue.

Things tested:

dline run from repo directory with ./dline.py with blank config file specified
dline run from repo directory with ./dline.py without config file specified and no config at default path
dline installed through pip in the repo directory without config file specified and no config at default path
dline installed through pip outside of the repo directory without config file specified and no config at the default path

All of these tests passed with dline running fine. Closing for now. Reopen if you have an alternate method for reproducing the issue.