unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Michael Welsh Duggan <mwd@md5i.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Michael Welsh Duggan <mwd@md5i.com>,
	62248@debbugs.gnu.org, luangruo@yahoo.com
Subject: bug#62248: 29.0.60; nil obsolete
Date: Sat, 18 Mar 2023 03:15:11 -0400	[thread overview]
Message-ID: <877cve1qf4.fsf@md5i.com> (raw)
In-Reply-To: <838rfuczfc.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 18 Mar 2023 09:05:11 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

>> Cc: luangruo@yahoo.com
>> From: Michael Welsh Duggan <mwd@md5i.com>
>> Date: Sat, 18 Mar 2023 02:52:57 -0400
>> 
>> Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text
>> editors" <bug-gnu-emacs@gnu.org> writes:
>> 
>> > Type:
>> >
>> >   C-h v nil RET
>> >
>> > Emacs will describe `nil' as obsolete since 29.1.
>> > That is absurd.
>> 
>> Happens for me too, but not with -Q.  So some common package is causing
>> this, likely by accident.
>
> Can you step through help-fns--var-obsolete and tell what you see
> there?  E.g., does (get nil 'byte-obsolete-variable) return non-nil?
>
> If so, how about running Emacs with a breakpoint in Fput and condition
> that symbol == Qnil (assuming your Emacs is not configured to
> represent Lisp objects as structs)?

I traced it, in my instance, to this line from url-gw.el:

(make-obsolete-variable url-gw-rlogin-obsolete-warned-once nil "29.1")

Maybe `make-obsolete-variable' should warn or error with nil as its
initial argument.

-- 
Michael Welsh Duggan
(md5i@md5i.com)





  reply	other threads:[~2023-03-18  7:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <875yay3hco.fsf.ref@yahoo.com>
2023-03-18  2:48 ` bug#62248: 29.0.60; nil obsolete Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18  6:16   ` Eli Zaretskii
2023-03-18  6:52   ` Michael Welsh Duggan
2023-03-18  7:05     ` Eli Zaretskii
2023-03-18  7:15       ` Michael Welsh Duggan [this message]
2023-03-18  7:22         ` Eli Zaretskii
2023-09-07 23:02           ` Stefan Kangas
2023-03-18  7:29         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-03-18  7:16       ` Eli Zaretskii
2023-03-18  7:28       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=877cve1qf4.fsf@md5i.com \
    --to=mwd@md5i.com \
    --cc=62248@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    /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).