* error: Cannot send unencoded text.
@ 2001-04-18 9:31 Dmitry Paduchih
2001-04-19 12:57 ` (Patch) " Dmitry Paduchih
0 siblings, 1 reply; 3+ messages in thread
From: Dmitry Paduchih @ 2001-04-18 9:31 UTC (permalink / raw)
Hi.
File rfc2047.el contains at the line 165 (or near) the following form:
(if (or (message-options-get
'rfc2047-encode-message-header-encode-any)
(message-options-set
'rfc2047-encode-message-header-encode-any
(y-or-n-p
"Some texts are not encoded. Encode anyway?")))
(rfc2047-encode-region (point-min) (point-max))
(error "Cannot send unencoded text."))
Can You, please, fix this asking y-or-n-p?
First, it seems to be inconsistent to ask user and then produce an
error on one of his choices.
Second, I have adjusted my settings so to send unencoded `Subject',
and I don't understand why this statement is disagree or why it should
ask me to confirm my settings every time I send message.
I upgraded Gnus to the CVS version from Apr 11 2001 found at the Manoj
Srivastava's page but it contains this form too.
Thank You for your attention and efforts,
-- Dmitry
^ permalink raw reply [flat|nested] 3+ messages in thread
* (Patch) Cannot send unencoded text.
2001-04-18 9:31 error: Cannot send unencoded text Dmitry Paduchih
@ 2001-04-19 12:57 ` Dmitry Paduchih
2001-04-19 16:52 ` Dmitry Paduchih
0 siblings, 1 reply; 3+ messages in thread
From: Dmitry Paduchih @ 2001-04-19 12:57 UTC (permalink / raw)
[-- Attachment #1: Type: text/plain, Size: 442 bytes --]
Hi,
Here is a patch which is to allow sending messages with unencoded
headers. I mean a possibility to do that, the defaults say to encode
headers. I wrote in my yesterday letter the reasons why it is needed
in my opinion. But it is only kinda work-arround.
Seriously I think it is better to redesign the concept of
message-options if I understand it correctly.
Can somebody commit this patch?
Thanks in advance,
Dmitry
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: The patch --]
[-- Type: text/x-patch, Size: 790 bytes --]
--- /usr/share/emacs/site-lisp/gnus/rfc2047.el Thu Mar 15 17:57:24 2001
+++ rfc2047.el Thu Apr 19 18:20:12 2001
@@ -161,14 +161,9 @@
(and (delq 'ascii
(mm-find-charset-region (point-min)
(point-max)))
- (if (or (message-options-get
+ (if (message-options-get
'rfc2047-encode-message-header-encode-any)
- (message-options-set
- 'rfc2047-encode-message-header-encode-any
- (y-or-n-p
- "Some texts are not encoded. Encode anyway?")))
- (rfc2047-encode-region (point-min) (point-max))
- (error "Cannot send unencoded text."))))
+ (rfc2047-encode-region (point-min) (point-max)))))
((mm-coding-system-p method)
(if (and (featurep 'mule)
(if (boundp 'default-enable-multibyte-characters)
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: (Patch) Cannot send unencoded text.
2001-04-19 12:57 ` (Patch) " Dmitry Paduchih
@ 2001-04-19 16:52 ` Dmitry Paduchih
0 siblings, 0 replies; 3+ messages in thread
From: Dmitry Paduchih @ 2001-04-19 16:52 UTC (permalink / raw)
Oops, please forgive me. I have found much simpler solution:
;;; Hm.
(add-to-list 'rfc2047-header-encoding-alist '("Subject" . none))
It simply wasn't documented. :)
>>>>> "DP" == Dmitry Paduchih <paduch@imm.uran.ru> writes:
DP> Hi,
DP> Here is a patch which is to allow sending messages with unencoded
DP> headers. I mean a possibility to do that, the defaults say to encode
DP> headers. I wrote in my yesterday letter the reasons why it is needed
DP> in my opinion. But it is only kinda work-arround.
DP> Seriously I think it is better to redesign the concept of
DP> message-options if I understand it correctly.
DP> Can somebody commit this patch?
DP> Thanks in advance,
DP> Dmitry
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2001-04-19 16:52 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2001-04-18 9:31 error: Cannot send unencoded text Dmitry Paduchih
2001-04-19 12:57 ` (Patch) " Dmitry Paduchih
2001-04-19 16:52 ` Dmitry Paduchih
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).