Lemmy

12680 readers

1 users here now

Everything about Lemmy; bugs, gripes, praises, and advocacy.

For discussion about the lemmy.ml instance, go to [email protected].

founded 4 years ago

MODERATORS

[email protected]

Is there a TUI or CLI client for lemmy? (lemmy.ml)

submitted 3 years ago by [email protected] to c/[email protected]

17 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 3 points 3 years ago* (last edited 3 years ago) (3 children)

It seems quite... minimalist at the moment. And it doesn't seem to take any notice of the instance in the config file. Seems okay otherwise. I think I'd prefer an emacs version, maybe with gnus as the front-end, to be honest.

[–] [email protected] 5 points 3 years ago (2 children)

It's supposed to be minimalist (as in very less metadata), the ui is just a placeholder it will be polished once the core logic is done,

Please open a issue on github on how to improve the config I didn't put a lot of thought into it becuase I wanted to prioritize another issue

[–] [email protected] 1 points 3 years ago (1 children)

"Minimalist" wasn't a criticism, just a comment really. It's odd that I can't see who posted what though.

I don't have a github account so can't create a ticket there. Basically I assumed that since the config contained the instance name (URL? I forget), that would be picked up in the absence of an instance on the command line and it would connect to that automatically.

[–] [email protected] 2 points 3 years ago

you'll be able to see the creator, It wasn't relevant to the features I was working on that's why I left it out,It will be done by this weekend.

Basically I assumed that since the config contained the instance name (URL? I forget), that would be picked up in the absence of an instance on the command line and it would connect to that automatically.

That's the intended behavior but there was a bug that prevented default instance from loading if it wasn't prefixed with 'https://'. just fixed that👍