[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#62767: 29.0.90; [PATCH] *lisp/emacs-lisp/package.el: set variables a
From: |
Eli Zaretskii |
Subject: |
bug#62767: 29.0.90; [PATCH] *lisp/emacs-lisp/package.el: set variables after info package |
Date: |
Sat, 15 Apr 2023 13:58:05 +0300 |
> From: Philip Kaludercic <philipk@posteo.net>
> Cc: sunlin7@yahoo.com, 62767@debbugs.gnu.org
> Date: Sat, 15 Apr 2023 10:43:21 +0000
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> From: Philip Kaludercic <philipk@posteo.net>
> >> Cc: 62767@debbugs.gnu.org, eliz@gnu.org
> >> Date: Fri, 14 Apr 2023 20:07:54 +0000
> >>
> >> lin Sun <sunlin7@yahoo.com> writes:
> >>
> >> > Hi,
> >> >
> >> > The package.el will always require the entire `info.el` on its package
> >> > activating function.
> >> > Using the `with-eval-after-load` to arrange the work can avoid the
> >> > unnecessary loading the `info` package.
> >>
> >> Note that this is not the only place where info is required. If this is
> >> an acceptable solution (which I am not sure since `with-eval-after-load'
> >> is something I usually encounter in user configurations), then we should
> >> think about consistently addressing the issue:
> >
> > What exactly are the problems with requiring info.el? We require
> > packages that define some function in gazillion other places, so what
> > makes this one case special?
>
> Some people optimise the startup time of Emacs and want to avoid loading
> files that are not necessary for Emacs to start-up.
And this is the only place in Emacs where we have (require 'FOO) and
FOO is not necessary for Emacs to start up? I'd be surprised.
- bug#62609: 29.0.60; [PATCH] src/comp.c: New variable `comp-el-to-eln-strip-prefix` for `comp-el-to-eln-rel-filename`, (continued)
- bug#62767: 29.0.90; [PATCH] *lisp/emacs-lisp/package.el: set variables after info package, lin Sun, 2023/04/11
- bug#62767: 29.0.90; [PATCH] *lisp/emacs-lisp/package.el: set variables after info package, Philip Kaludercic, 2023/04/14
- bug#62767: 29.0.90; [PATCH] *lisp/emacs-lisp/package.el: set variables after info package, lin Sun, 2023/04/14
- bug#62767: 29.0.90; [PATCH] *lisp/emacs-lisp/package.el: set variables after info package, Eli Zaretskii, 2023/04/15
- bug#62767: 29.0.90; [PATCH] *lisp/emacs-lisp/package.el: set variables after info package, Philip Kaludercic, 2023/04/15
- bug#62767: 29.0.90; [PATCH] *lisp/emacs-lisp/package.el: set variables after info package,
Eli Zaretskii <=
- bug#62767: 29.0.90; [PATCH] *lisp/emacs-lisp/package.el: set variables after info package, lin Sun, 2023/04/17
- bug#62767: 29.0.90; [PATCH] *lisp/emacs-lisp/package.el: set variables after info package, Ruijie Yu, 2023/04/17
- bug#62767: 29.0.90; [PATCH] *lisp/emacs-lisp/package.el: set variables after info package, Ruijie Yu, 2023/04/17
- bug#62767: 29.0.90; [PATCH] *lisp/emacs-lisp/package.el: set variables after info package, Philip Kaludercic, 2023/04/17
- bug#62767: 29.0.90; [PATCH] *lisp/emacs-lisp/package.el: set variables after info package, lin Sun, 2023/04/17
- bug#62767: 29.0.90; [PATCH] *lisp/emacs-lisp/package.el: set variables after info package, Philip Kaludercic, 2023/04/17
- bug#62767: 29.0.90; [PATCH] *lisp/emacs-lisp/package.el: set variables after info package, Eli Zaretskii, 2023/04/17
- bug#62767: 29.0.90; [PATCH] *lisp/emacs-lisp/package.el: set variables after info package, Stefan Monnier, 2023/04/17
- bug#62767: 29.0.90; [PATCH] *lisp/emacs-lisp/package.el: set variables after info package, lin Sun, 2023/04/19
- bug#62767: 29.0.90; [PATCH] *lisp/emacs-lisp/package.el: set variables after info package, Eli Zaretskii, 2023/04/20