search

zulip / zulip-terminal

Official Zulip terminal client.
Apache License 2.0
661 stars 251 forks source link

Minimize length of stream box during compose based on available space & maximum stream length #905

Open neiljp opened 3 years ago

neiljp commented 3 years ago

Currently the stream box can be quite wide; we spread the boxes between the available width.

While topic length can vary, we should be able to find some way to determine a smaller length using urwid's features based on what we know about the maximum stream length at the time.

Good related features to consider

I've labelled this as a good first issue initially as this would be good to help someone new to this to get to know urwid and the core UI, but this may be challenging or trickier than I expect and involve digging a little to find the right combination of spacing, so that this works over a wide range of window widths.

cyberShaw commented 3 years ago

@zulipbot claim

zulipbot commented 3 years ago

Welcome to Zulip, @cyberShaw! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip-terminal/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!

Here's some tips to get you off to a good start:

As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.

See you on the other side (that is, the pull request side)!

zulipbot commented 3 years ago

Hello @cyberShaw, you claimed this issue to work on it, but this issue and any referenced pull requests haven't been updated for 10 days. Are you still working on this issue?

If so, please update this issue by leaving a comment on this issue to let me know that you're still working on it. Otherwise, I'll automatically remove you from this issue in 4 days.

If you've decided to work on something else, simply comment @zulipbot abandon so that someone else can claim it and continue from where you left off.

Thank you for your valuable contributions to Zulip!

Sickaada commented 3 years ago

@zulipbot claim

zulipbot commented 3 years ago

Hello @silentC1C4D4, it looks like someone has already claimed this issue! Since we believe multiple assignments to the same issue may cause some confusion, we encourage you to search for other unclaimed issues to work on. However, you can always reclaim this issue if no one is working on it.

We look forward to your valuable contributions!

cyberShaw commented 3 years ago

@zulipbot abandon

zulipbot commented 3 years ago

Hello @jalajcodes, it looks like you've currently claimed 1 issue in this repository. We encourage new contributors to focus their efforts on at most 1 issue at a time, so please complete your work on your other claimed issues before trying to claim this issue again.

We look forward to your valuable contributions!

Sickaada commented 3 years ago

@zulipbot claim

zulipbot commented 3 years ago

Welcome to Zulip, @silentC1C4D4! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip-terminal/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!

Here's some tips to get you off to a good start:

As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.

See you on the other side (that is, the pull request side)!

zulipbot commented 3 years ago

Hello @jalajcodes, it looks like you've currently claimed 1 issue in this repository. We encourage new contributors to focus their efforts on at most 1 issue at a time, so please complete your work on your other claimed issues before trying to claim this issue again.

We look forward to your valuable contributions!

b-thebest commented 3 years ago

@zulipbot claim

zulipbot commented 3 years ago

Welcome to Zulip, @b-thebest! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip-terminal/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!

Here's some tips to get you off to a good start:

As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.

See you on the other side (that is, the pull request side)!

as2539-ctrl commented 3 years ago

@zulipbot claim

zulipbot commented 3 years ago

Welcome to Zulip, @as2539-ctrl! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip-terminal/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!

Here's some tips to get you off to a good start:

As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.

See you on the other side (that is, the pull request side)!

suzaram3 commented 3 years ago

@zulipbot claim

zulipbot commented 3 years ago

Welcome to Zulip, @suzaram3! We just sent you an invite to collaborate on this repository at https://github.com/zulip/zulip-terminal/invitations. Please accept this invite in order to claim this issue and begin a fun, rewarding experience contributing to Zulip!

Here's some tips to get you off to a good start:

As you work on this issue, you'll also want to refer to the Zulip code contribution guide, as well as the rest of the developer documentation on that site.

See you on the other side (that is, the pull request side)!

notlelouch commented 10 months ago

is the issue still unresolved?

neiljp commented 10 months ago

@notlelouch You could look through open PRs, but there is no merged fix - try running the development version of ZT on a wide terminal and you should be able to see the problem.