Bug 1020562 - Please ship source lisp files with emacs
Summary: Please ship source lisp files with emacs
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: emacs
Version: 19
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Petr Hracek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-10-17 23:40 UTC by Omair Majid
Modified: 2013-10-21 17:00 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-10-21 17:00:23 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Omair Majid 2013-10-17 23:40:22 UTC
The packaging guildelines for emacs [1] state that emacs packages should ship source lisp files:

"""
Packaging of source elisp files

Typically, an Emacs add-on package will be compiled from source elisp files. The resulting compiled elisp files will then be included in the relevant emacs-foo and xemacs-foo packages. It is important to also include the source elisp files for several reasons. For example when debugging a problem with an (X)Emacs package, the Elisp debugger can look up the relevant code or symbol definition in the source lisp file if present. Also, it's sometimes helpful to jump to a variable description string from the Emacs help system.
"""

Please modify the emacs package itself to install the source lisp files. There are so many times I want to see how a function is implemented but emacs cant point me to the source :(

[1] https://fedoraproject.org/wiki/Packaging:Emacs#Packaging_of_source_elisp_files

Comment 1 Petr Hracek 2013-10-21 14:13:11 UTC
Hello Omair,

Did you try to install emacs-el package?
Are there any files missing?

By the way I do not think to provide el files together with emacs package.

Best regards
Petr

Comment 2 Omair Majid 2013-10-21 17:00:23 UTC
Ah, yes. I somehow missed the emacs-el package. Everything works fine when I install it.

Sorry for the noise.


Note You need to log in before you can comment on or make changes to this bug.