From: Shenghuo ZHU <zsh@cs.rochester.edu>
Subject: Re: bug in calculation of line length again
Date: 23 Nov 1998 13:30:40 -0500 [thread overview]
Message-ID: <5bpvae2re7.fsf@schnapps.cs.rochester.edu> (raw)
In-Reply-To: Vladimir Volovich's message of "23 Nov 1998 11:02:06 +0300"
>>>>> "VVV" == Vladimir Volovich <vvv@vvv.vsu.ru> writes:
VVV> Hi,
VVV> in pgnus v0.53, i'm (again) getting a warning "You have lines longer
VVV> than 79 characters. Really post? " when i'm trying to send messages
VVV> in Russian, while there are no such lines in a message. Here is a
VVV> backtrace:
VVV> Signaling: (quit)
VVV> y-or-n-p("You have lines longer than 79 characters. Really post? ")
VVV> message-check-news-body-syntax()
VVV> message-check-news-syntax()
VVV> message-send-news(nil)
VVV> message-send-via-news(nil)
VVV> message-send(nil)
VVV> message-send-and-exit(nil)
VVV> * call-interactively(message-send-and-exit)
VVV> When such a warning appears, the message buffer contains `unencoded'
VVV> text like \301\310\302...
I guess it is because of decoding. By reading codes of
message-send-news, you can find that gnus does encoding before
checking. Is it a proper order?
`(standard-display-8bit 160 255)' may relieve your pain.
--
Shenghuo
next prev parent reply other threads:[~1998-11-23 18:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-23 8:02 Vladimir Volovich
1998-11-23 18:30 ` Shenghuo ZHU [this message]
1998-11-23 19:17 ` Vladimir Volovich
1998-11-23 19:37 ` Shenghuo ZHU
1998-11-24 10:00 ` Lars Magne Ingebrigtsen
1998-11-24 9:59 ` Lars Magne Ingebrigtsen
1998-11-24 13:49 ` Vladimir Volovich
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5bpvae2re7.fsf@schnapps.cs.rochester.edu \
--to=zsh@cs.rochester.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).