Bug 78764 – emacs is broken

Bug 78764 - emacs is broken

Summary:	emacs is broken

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Raw Hide
Classification:	Retired
Component:	emacs (Show other bugs)
Sub Component:
Version:	1.0
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Jens Petersen
QA Contact:	Jay Turner
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2002-11-29 08:16 EST by Tim Waugh
Modified:	2015-01-07 19:02 EST (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-12-01 22:45:28 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Tim Waugh 2002-11-29 08:16:22 EST

Description of Problem:
Emacs doesn't work any more.  21.2-22 worked fine.

Version-Release number of selected component (if applicable):
21.2-23

How Reproducible:
100%

Steps to Reproduce:
1. Start 'emacs textfile' for an existing textfile

Actual Results:
Errors.

Expected Results:
textfile loads ready to edit

Additional Information:

Comment 1 Jens Petersen 2002-11-30 02:00:02 EST

Works fine me for me.  What are the errors you're seeing?

Comment 2 Tim Waugh 2002-11-30 05:15:09 EST

Firstly a seemingly harmless warning:

Warning: Lisp directory `/usr/share/emacs/21.2/leim' does not exist.

But then this in the minibuffer:

Symbol's function definition is void: defalias-maybe

Comment 3 Jens Petersen 2002-12-01 22:45:21 EST

Thanks for pointing this out.  There were some functions only defined
in the apel package that were causing this in rpm-spec-mode-init.el.

This and the leim dir warning should be fixed in emacs-21.2-24.

Comment 4 Tim Waugh 2002-12-02 07:37:43 EST

Works for me.

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