From: Uwe Brauer <oub@mat.ucm.es>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Uwe Brauer <oub@mat.ucm.es>, 58474@debbugs.gnu.org
Subject: bug#58474: 29.0.50; gnus does not startup in latest master: (void-variable gnus-local-domain)
Date: Thu, 13 Oct 2022 12:08:17 +0200 [thread overview]
Message-ID: <87k054yr1q.fsf@mat.ucm.es> (raw)
In-Reply-To: <87h708opey.fsf@mat.ucm.es>
[-- Attachment #1: Type: text/plain, Size: 2265 bytes --]
>>> "EZ" == Eli Zaretskii <eliz@gnu.org> writes:
>> From: Uwe Brauer <oub@mat.ucm.es>
>> Cc: Uwe Brauer <oub@mat.ucm.es>, 58474@debbugs.gnu.org
>> Date: Wed, 12 Oct 2022 22:22:21 +0200
>>
>> > Did you try looking up this variable in NEWS?
>>
>>
>> Sigh, I did now,
>> ** Some functions and variables obsolete since Emacs 24 have been removed:
>>
>> But no hint how to somehow use it anyhow.
> Look at the code which caused the problem:
>> Debugger entered--Lisp error: (void-variable gnus-local-domain)
>> (or gnus-local-domain (message-make-domain) (system-name) "")
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> So if gnus-local-domain is nil, the code in bbdb already knows how to
> deal with that, it just needs the variable to exist.
> Now look at how this obsolete variable was defined in Emacs 28:
> (defcustom gnus-local-domain nil
> This is how you have been "using" this variable since Emacs 24: with a
> nil value. So just
> (defvar gnus-local-domain nil)
> somewhere in your init file should do. Better yet, modify bbdb to
> remove all the references to that variable.
Thanks, may I propose, and I think I will propose it in devel later today:
Why not have a file called
obsolete-var-funcs.el or backward-compatiblity-var-func.el
That contains these old compatibility code?
Such a file could be loaded by users who need this sort of compatibility?
In my case such a file would look, for the moment (I have to run more tests)
(define-obsolete-function-alias 'set-face-underline-p
'set-face-underline "24.3")
(defcustom gnus-local-domain nil
"Local domain name without a host name.
The DOMAINNAME environment variable is used instead if it is defined.
If the function `system-name' returns the full Internet name, there is
no need to set this variable."
:group 'gnus-message
:type '(choice (const :tag "default" nil)
string))
(make-obsolete-variable 'gnus-local-domain nil "24.1")
--
I strongly condemn Putin's war of aggression against the Ukraine.
I support to deliver weapons to Ukraine's military.
I support the ban of Russia from SWIFT.
I support the EU membership of the Ukraine.
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5673 bytes --]
prev parent reply other threads:[~2022-10-13 10:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-12 18:41 bug#58474: 29.0.50; gnus does not startup in latest master: (void-variable gnus-local-domain) Uwe Brauer
2022-10-12 19:10 ` Eli Zaretskii
2022-10-12 20:22 ` Uwe Brauer
2022-10-12 20:38 ` Lars Ingebrigtsen
2022-10-13 5:20 ` Eli Zaretskii
2022-10-13 10:08 ` Uwe Brauer [this message]
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=87k054yr1q.fsf@mat.ucm.es \
--to=oub@mat.ucm.es \
--cc=58474@debbugs.gnu.org \
--cc=eliz@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).