Package: ttytter Version: 2.1.0+1-1 Severity: minor Tags: upstream Twitter.com allows line breaks when composing tweets.
When the -newline command line option of TTYtter is not present, these line breaks are displayed as the literal string "\n". When the -newline command line option is present, these line breaks are actually conserved, and real line breaks occur in the terminal when the tweet is displayed. So far so good. But independent of the -newline switch, retweeting such a tweet -- or composing a new tweet -- containting the literal string "\n", will not transform it back into a real line break. The Twitter.com website and other twitter clients therefore display the literal string "\n" for such messages sent by TTYtter. It's not a big deal when composing new tweets (because one simply doesn't type \n), but if one wants to /oretweet such a message (containing a line break), the tweet display will be messed up for others. -- System Information: Debian Release: jessie/sid APT prefers testing-updates APT policy: (500, 'testing-updates'), (500, 'testing') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages ttytter depends on: ii curl 7.38.0-3 ii perl 5.20.1-2 Versions of packages ttytter recommends: ii libterm-readline-gnu-perl 1.24-2+b1 ii libtimedate-perl 2.3000-2 ttytter suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
