Gnus development mailing list
 help / color / mirror / Atom feed
From: Dmitry Paduchih <paduch@imm.uran.ru>
Subject: (Patch) Cannot send unencoded text.
Date: 19 Apr 2001 18:57:14 +0600	[thread overview]
Message-ID: <878zkx6o9h.fsf@ait.uran.ru> (raw)
In-Reply-To: <87snj6zh98.fsf@ait.uran.ru> (Dmitry Paduchih's message of "18 Apr 2001 15:31:15 +0600")

[-- 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)

  reply	other threads:[~2001-04-19 12:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-04-18  9:31 error: " Dmitry Paduchih
2001-04-19 12:57 ` Dmitry Paduchih [this message]
2001-04-19 16:52   ` (Patch) " Dmitry Paduchih

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=878zkx6o9h.fsf@ait.uran.ru \
    --to=paduch@imm.uran.ru \
    /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).