Bug 88262 - aspell-init.el and xemacs location
aspell-init.el and xemacs location
Status: CLOSED RAWHIDE
Product: Red Hat Linux
Classification: Retired
Component: aspell (Show other bugs)
9
All Linux
medium Severity medium
: ---
: ---
Assigned To: Eido Inoue
Ben Levenson
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-04-08 07:14 EDT by Jens Petersen
Modified: 2007-04-18 12:52 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2003-06-24 23:48:24 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Jens Petersen 2003-04-08 07:14:42 EDT
Description of problem:
Currently the contents of the small "aspell-init.el" file are
actually duplicated in emacs' "/usr/share/emacs/site-lisp/site-start.el".
Also for xemacs the file should now be installed in
"%{_datadir}/xemacs/site-packages/lisp/site-start.d/",
ie no longer "/usr/lib/xemacs/xemacs-packages/lisp/site-start.d".

Version-Release number of selected component (if applicable):
aspell-0.33.7.1-21

How reproducible:
every time

Steps to Reproduce:
1.rpm -ql aspell | grep init.el

Additional info:
Since it is just a one-liner I don't mind carrying the
`ispell-program-name' in site-start.el files of emacs and xemacs,
but I guess keeping it in the aspell package is equally good.
Comment 1 Eido Inoue 2003-05-23 12:32:28 EDT
would you prefer that I remove it? I'd rather now have emacs-specific add-ons in
aspell if emacs already has it. If it needs to be added to xemacs, I'd prefer
that it be there.
Comment 2 Jens Petersen 2003-05-23 17:55:54 EDT
Sounds fine to me.

So the setup line is in xemacs' site-start.el already and I will add it to
emacs' default.el in the next build, so feel free to remove aspell-init.el
from aspell. :)
Comment 3 Eido Inoue 2003-06-24 23:48:24 EDT
fixed in 0.50-14

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