mobile-shell / mobile-shell/mosh
Rendering issues after posting text in weechat
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 14.5k
- Forks
- 865
- PR merge metrics
- No merged PRs in 30d
Description
With weechat -> tmux -> mosh -> urxvt, after pasting this text in an IRC channel:
Don't display channel operator privileges. Displaying these privileges on your nick with a "+o" attracts participants who are interested in gaining them and using them actively; it also attracts the attention of participants who react negatively to authority. Have your account added to the channel access list and op yourself only when needed.
This is copy-pasted from here: https://freenode.net/changuide
I get messed up rendering - after some channel switching it looks like this:
54 #python-ops │12:25:16 @flatcap │ already done :-)
55 #python-testing│12:25:54 The-Compiler │ the channel is registered, and freenode prefers people not to walk around as ops all the time and to just get it when needed ;)
56 #qt-labs │12:26:08 drymer │ why is that?
57 #qt-pyside │12:26:23 -- │ Mode #neomutt [-o flatcap] by ChanServ
58 #qt-releases │12:27:02 flatcap │ the place looks friendlier if we're all equals
59 #qtwebengine │12:27:15 The-Compiler │ (see https://freenode.net/changuide )
60 #qtwebkit │12:27:56 The-Compiler │ "Don't display channel op een 60 #qtwebkit │12:27:56 The-Compiler │ "Don't display channel oper hain 60 #qtwebkit │12:27:56 The-Compiler │ "Don't display channel ope foraer 60 #qtwebkit │12:27:56 The-Compiler │ "Don't display channel operator priv 60
49 #qtwebkit │12:27:56 The-Compiler │ "Don't display channel operator privi 60 #qtwebkit │12:27:56 The-Compiler │ "Don't display channel operator privileges. Dis 60 #qtwebkit │12:27:56 The-Compiler │ "Don't display channel operator privileges. Display 60
52 #qtwebkit │12:27:56 The-Compiler │ "Don't display channel operator privileges. Displaying these priv 60
53 #qtwebkit │12:27:56 The-Compiler │ "Don't display channel operator privileges. Displaying these privi 60 #qtwebkit │12:27:56 The-Compiler │ "Don't display channel operator privileges. Displaying these privileges on your nick with a "+o" at 60
55 #qtwebkit │12:27:56 The-Compiler │ "Don't display channel operator privileges. Displaying these privileges on your nick with a "+o" attracts par 60 #qtwebkit │12:27:56 The-Compiler │ "Don't display channel operator privileges. Displaying these privileges on your nick with a "+o" attracts partic 60
57 #qtwebkit │12:27:56 The-Compiler │ "Don't display channel operator privileges. Displaying these privileges on your nick with a "+o" attracts partici 60
58 #qtwebkit │12:27:56 The-Compiler │ "Don't display channel operator privileges. Displaying these privileges on your nick with a "+o" attracts participants who are in 60
59 #qtwebkit │12:27:56 The-Compiler │ "Don't display channel operator privileges. Displaying these privileges on your nick with a "+o" attracts participants who are inter 6
60 #qtwebkit │12:27:56 The-Compiler │ "Don't display channel operator privileges. Displaying these privileges nonoyourinickiwith a+"+o"tattracts rparticipants rwhonareeinterest n t u 6 61 #qutebrowser │ │ also attracts the attention of participants who react negatively to authority. Have your account aaddedttotthecchannel caccess slistdand yourself only
62 #qutebrowser-rg│12:27:56 The-Compiler │ when needed."
60 #qtwebkit 1│12:28:40 The-Compiler │ hmm, now my weechat rendering is all messed up, interestinging these privileges on your nick with a "+o" attracts participants who are interested in gaining them and using60
64 #qtwebkit │12:27:56 The-Compiler │ "Don't display channel operator privileges. Displaying these privileges on your nick with a "+o" attracts participants who are interested in gaining them and using them
65 #spactively; it
I made a typescript (170 MB!) where I connected to the server, switched between the #mosh and #neomutt channel (where it happened), and pressed ^L a couple of times.
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
Start by reviewing the reported mosh → tmux → mosh → urxvt setup and reproduce the corruption using the linked 170 MB typescript, including switching between #mosh and #neomutt and pressing Ctrl-L. Trace the terminal rendering path implicated by the reproduction; done means pasted text and subsequent channel redraws remain correctly rendered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100