unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
Cc: david@tethera.net,  notmuch@notmuchmail.org,  35370@debbugs.gnu.org
Subject: Re: bug#35370: notmuch-emacs: avoiding deprecated message-default-charset
Date: Sun, 21 Apr 2019 18:05:19 -0400	[thread overview]
Message-ID: <87sgubrp40.fsf@gmail.com> (raw)
In-Reply-To: <87a7gjw479.fsf@fifthhorseman.net> (Daniel Kahn Gillmor's message of "Sun, 21 Apr 2019 15:25:46 -0400")

Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes:

>>> In notmuch-maildir-setup-message-for-saving:
>>> emacs/notmuch-maildir-fcc.el:172:31:Warning: ‘message-default-charset’ is an
>>>     obsolete variable (as of 26.1); The default charset comes from the
>>>     language environment
>>>
>>> I'm not enough of an emacs guru to know the right way to avoid this
>>> warning, but i'm hoping that someonen else can take a stab at it, since
>>> extraneous warnings make it easier to ignore real problems.
>>
>> Good question. I looked at message.el in emacs master and it
>>
>>      1) Obsoletes message-default-charset as in 26.1
>>      2) Still uses it in exactly the construction we do.
>
> interesting, thanks for digging that up.
>
>> I'm not sure if it's exactly a reportable bug in emacs, but it is a bit
>> annoying.
>
> seems reportable, if not exactly high-severity.  what does upstream
> expect downstream users of message-default-charset to do?  I'm
> (trying to) forward this to the emacs upstream bugtracker; maybe we can
> get guidance from them on what to do.

The commit which marks this variable as obsolete, has a couple hunks
that just remove uses of it.  Not clear why other uses were left in.
Oversight?

[1: 66d9ef95c0]: 2016-02-14 17:07:48 +1100
  Remove compat code for older Emacsen
  https://git.savannah.gnu.org/cgit/emacs.git/commit/?id=66d9ef95c0f9407d2a6d26bcd7ed84a303294b53

--- a/lisp/gnus/gnus-int.el
+++ b/lisp/gnus/gnus-int.el
@@ -777,8 +777,7 @@ (defun gnus-request-accept-article (group &optional gnus-command-method last
       (message-options-set-recipient)
       (save-restriction
 	(message-narrow-to-head)
-	(let ((mail-parse-charset message-default-charset))
-	  (mail-encode-encoded-word-buffer)))
+	(mail-encode-encoded-word-buffer))
       (message-encode-message-body)))
   (let ((gnus-command-method (or gnus-command-method
 				 (gnus-find-method-for-group group)))
@@ -800,8 +799,7 @@ (defun gnus-request-replace-article (article group buffer &optional no-encode)
       (message-options-set-recipient)
       (save-restriction
 	(message-narrow-to-head)
-	(let ((mail-parse-charset message-default-charset))
-	  (mail-encode-encoded-word-buffer)))
+	(mail-encode-encoded-word-buffer))
       (message-encode-message-body)))
   (let* ((func (car (gnus-group-name-to-method group)))
          (result (funcall (intern (format "%s-request-replace-article" func))

  reply	other threads:[~2019-04-21 22:05 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-20 20:00 notmuch-emacs: avoiding deprecated message-default-charset Daniel Kahn Gillmor
2019-04-21 14:41 ` David Bremner
2019-04-21 19:25   ` Daniel Kahn Gillmor
2019-04-21 22:05     ` Noam Postavsky [this message]
2019-04-22  1:55       ` bug#35370: " Daniel Kahn Gillmor
2019-04-22  6:33         ` Eli Zaretskii
2019-04-22 14:21           ` Daniel Kahn Gillmor
2019-04-22 15:37             ` Eli Zaretskii
2019-04-22 20:51               ` [PATCH] emacs: drop use of message-default-charset Daniel Kahn Gillmor
2019-04-22 21:23                 ` Tomi Ollila
2019-05-07  9:38                 ` David Bremner
2019-05-07 12:26           ` bug#35370: notmuch-emacs: avoiding deprecated message-default-charset Noam Postavsky
2019-05-07 14:36             ` Eli Zaretskii
2019-05-09 18:33               ` Lars Ingebrigtsen
2019-05-10  5:32                 ` Eli Zaretskii
2019-05-10 10:45                   ` Noam Postavsky

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

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87sgubrp40.fsf@gmail.com \
    --to=npostavs@gmail.com \
    --cc=35370@debbugs.gnu.org \
    --cc=david@tethera.net \
    --cc=dkg@fifthhorseman.net \
    --cc=notmuch@notmuchmail.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

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 read-only IMAP folder(s) and NNTP newsgroup(s).