Multiline message composition
Nobody has claimed this yet.
- Dominant language
- Haskell
- Stars
- 168
- Forks
- 27
- PR merge metrics
- No merged PRs in 30d
Description
It would be great to be able to read the entire message you're composing before sending. right now it scrolls horizontally as you compose. The tricky part I guess would be to distinguish it from M-enter. I've got some idea's: A new message created by M-enter adds a new ^ and $, an overflowing/line-wrapped message doesn't. for example:
^this is a message$
^this is another message by M-enter. this one is also too long
to fit on one line and therefore wraps.$
Alternatively messages could wrap, unless you use M-enter
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not name files, tests, or entry points. Start by locating the console client's message-composition and M-enter handling, then compare how wrapping and explicitly separated messages are represented. Done means a user can read the full message before sending while M-enter-created messages remain distinguishable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- haskell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100