ESS installed without autoloads

  • Done
  • quality assurance status badge
Details
3 participants
  • Alex Kost
  • Ricardo Wurmus
  • zimoun
Owner
unassigned
Submitted by
Ricardo Wurmus
Severity
normal
R
R
Ricardo Wurmus wrote on 10 Mar 2017 10:03
(address . bug-guix@gnu.org)
87lgsd1p2o.fsf@elephly.net
The “emacs-ess” package does not behave like all other Emacs packages.
Its files are installed to “$out/share/emacs/site-lisp/ess” (not
“guix.d”) and there are no autoloads.

I don’t know how to get ESS to work like this. Should the package be
changed such that it installs autoload files like all other packages?

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
A
A
Alex Kost wrote on 11 Mar 2017 15:38
(name . Ricardo Wurmus)(address . rekado@elephly.net)(address . 26046@debbugs.gnu.org)
878tobg9od.fsf@gmail.com
Ricardo Wurmus (2017-03-10 10:03 +0100) wrote:

Toggle quote (7 lines)
> The “emacs-ess” package does not behave like all other Emacs packages.
> Its files are installed to “$out/share/emacs/site-lisp/ess” (not
> “guix.d”) and there are no autoloads.
>
> I don’t know how to get ESS to work like this. Should the package be
> changed such that it installs autoload files like all other packages?

Yeah, I think its elisp files should be put either directly into
"site-lisp" (as it is done by 'magit') or into "site-lisp/guix.d/..."
(as it is done by 'let-alist', for example).

As for the "...-autoloads.el" file, it can be created with
'emacs-generate-autoloads' procedure (see 'emacs-wget' or 'git-modes'
for examples).

Note: I've not looked at 'emacs-ess', so it was a theoretical comment :-)

--
Alex
Z
Z
zimoun wrote on 13 May 2020 02:02
bug#26046: ESS installed without autoload
CAJ3okZ07wPJbmA-EWR7n+Q7RzCxjUC3qpWvOTMgYy4YkkWXtdg@mail.gmail.com
Dear,

Digging in the bug tracker, I found this bug [1] about ESS saying that
it does not behave like all other Emacs packages; installing in
'$out/share/emacs/site-lisp/ess' instead of "guix.d".

Well, all other packages do install in '$out/share/emacs/site-lisp/'
as the manual says [2]. Because the Emacs packages location changes
recently, AFAIU.

Does it make sense to close it now?

Cheers,
simon

R
R
Ricardo Wurmus wrote on 14 May 2020 07:55
(name . zimoun)(address . zimon.toutoune@gmail.com)
87lflvcb7q.fsf@elephly.net
zimoun <zimon.toutoune@gmail.com> writes:

Toggle quote (10 lines)
> Digging in the bug tracker, I found this bug [1] about ESS saying that
> it does not behave like all other Emacs packages; installing in
> '$out/share/emacs/site-lisp/ess' instead of "guix.d".
>
> Well, all other packages do install in '$out/share/emacs/site-lisp/'
> as the manual says [2]. Because the Emacs packages location changes
> recently, AFAIU.
>
> Does it make sense to close it now?

Yes, I think this is no longer a problem now that we no longer use
“guix.d”.

--
Ricardo
Closed
?
Your comment

This issue is archived.

To comment on this conversation send an email to 26046@debbugs.gnu.org

To respond to this issue using the mumi CLI, first switch to it
mumi current 26046
Then, you may apply the latest patchset in this issue (with sign off)
mumi am -- -s
Or, compose a reply to this issue
mumi compose
Or, send patches to this issue
mumi send-email *.patch