From: Pankaj Jangid <p4j@j4d.net>
To: emacs-devel <emacs-devel@gnu.org>
Subject: Where has the list gnus-newsgroup-variables gone?
Date: Wed, 11 Dec 2019 19:58:26 +0000 [thread overview]
Message-ID: <0100016ef68a8fc5-40722ea4-5189-4a0e-a6e8-a1f5d16a6544-000000@email.amazonses.com> (raw)
I had a setting in my Gnus configuration,
#+BEGIN_SRC emacs-lisp
;; Set the default value of ‘mm-discouraged-alternatives’.
(add-to-list
'gnus-newsgroup-variables
'(mm-discouraged-alternatives . '("text/html" "text/richtext" "image/.*")))
#+END_SRC
Today when pull from master. It produced variable void error for
gnus-newsgroup-variables list.
Has something changed?
Regards,
--
Pankaj Jangid
next reply other threads:[~2019-12-11 19:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-11 19:58 Pankaj Jangid [this message]
2019-12-11 20:51 ` Where has the list gnus-newsgroup-variables gone? Andreas Schwab
2019-12-12 6:11 ` Pankaj Jangid
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0100016ef68a8fc5-40722ea4-5189-4a0e-a6e8-a1f5d16a6544-000000@email.amazonses.com \
--to=p4j@j4d.net \
--cc=emacs-devel@gnu.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://git.savannah.gnu.org/cgit/emacs.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).