unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "T.V Raman" <raman@google.com>
To: monnier@iro.umontreal.ca
Cc: larsi@gnus.org, raman@google.com, eliz@gnu.org, emacs-devel@gnu.org
Subject: Re: Howto fix: package autoload is deprecated
Date: Thu, 15 Sep 2022 11:19:03 -0700	[thread overview]
Message-ID: <25379.27799.702520.380990@retriever.mtv.corp.google.com> (raw)
In-Reply-To: <jwvk064zhiy.fsf-monnier+emacs@gnu.org>

for now, no, because if you remove the (require 'autoload), it gets
pulled in by the hack in subr.el.

My issue was that I 1. had missed the obsoletion, and 2. On my new
laptop, (new as from May) building and installing emacs from HEAD
wasn't replacing the info manuals because of compressed vs
uncompressed install, go figure!

So as Eli suspected I was reading an older manual. 

Makes me wonder: when Emacs Info pages are displayed, should the
version info of that info manual be part of the Header line?

Stefan Monnier writes:
 > >> FWIW, I think the obsoletion(?) of `autoload.el` is a bit rash:
 > >> it breaks all existing packages which just called the (formerly)
 > >> autoloaded entry points without first doing (require 'autoload).
 > > Unless I missed something, all the previously ###;;;autoloaded entry
 > > points should still be available without doing that (see subr.el).
 > 
 > Hmm... indeed.  Sorry 'bout the noise.
 > Tho I wonder then if Raman's code could work "unchanged" by just
 > removing the explicit (require 'autoload).
 > 
 > 
 >         Stefan

-- 

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮

--

Thanks,

--Raman(I Search, I Find, I Misplace, I Research)
♉ Id: kg:/m/0285kf1  🦮



  reply	other threads:[~2022-09-15 18:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14  2:38 Howto fix: package autoload is deprecated T.V Raman
2022-09-14 11:30 ` Eli Zaretskii
2022-09-15  2:02   ` T.V Raman
2022-09-15  2:54     ` Stefan Monnier
2022-09-15  7:16       ` Lars Ingebrigtsen
2022-09-15 17:16         ` Stefan Monnier
2022-09-15 18:19           ` T.V Raman [this message]
2022-09-15 13:56       ` T.V Raman
2022-09-15  6:03     ` Eli Zaretskii

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=25379.27799.702520.380990@retriever.mtv.corp.google.com \
    --to=raman@google.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.org \
    --cc=monnier@iro.umontreal.ca \
    /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).