2) Showing them is common behavior afaik. MacOS terminal is the one
that's odd here. Nothing wrong with that. Those characters are what
actually the keyboard sends to the terminal or, more accurately, what
the terminal prints for what it actually receives from the keyboard.
1) I can't tell what's the problem exactly because I am on mobile data
atm and I don't feel like wasting my bandwith with videos. Like Hiltjo
said, text is probably what you want for bug reports. A 'cool' thing,
yet perhaps unsuitable for this situation, is using asciinema to
record terminal sessions. It is definitely better for bandwith.
regards,
Lukáš
2017-09-15 15:53 GMT+02:00 Hiltjo Posthuma <hiltjo_AT_codemadness.org>:
> On Fri, Sep 15, 2017 at 08:56:13PM +0800, Kai Hendry wrote:
>> Hi Hiltjo,
>>
>
> This is dev_AT_.
>
>> I have a couple issues with st https://s.natalian.org/2017-09-15/st.mp4
>>
>> They are still reproduciable on b1338e91ed632adbcd08388de37e46cf25326e01
>>
>
> Bug reports are written using the universal text format. Your configuration
> issues are not bugs. The blind person with a slow connection can not see
> your issue report (in this case not so bad).
>
>> 1) Some readline isn't showing the line properly after a long input line
>> or I presume some line wrapping
>>
>> 2) When I hit key combos accidentally like shift+{up,down} I get
>> characters printed which I don't care for
>>
>> (Doesn't happen on MacOS's terminal)
>>
>
> Then use MacOS terminal, st isn't designed for Mac hipsters.
>
>> Haven't tried editing st.info yet since I don't know what I'm doing.
>>
>> Sorry, don't have a patch since I'm out of depth. Cheers,
>>
>
> Don't be lazy and learn the system.
>
> --
> Kind regards,
> Hiltjo
>
Received on Fri Sep 15 2017 - 17:40:52 CEST