Bug 77696 – JDEE does not with without deactive-mark

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 77696 - JDEE does not with without deactive-mark

Summary:	JDEE does not with without deactive-mark

Status:	CLOSED RAWHIDE

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	xemacs (Show other bugs)
Sub Component:
Version:	8.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:	75440
Blocks:
	Show dependency tree / graph

Reported:	2002-11-12 06:03 EST by Mike Hearn
Modified:	2015-01-07 19:01 EST (History)
CC List:	2 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2002-12-18 06:55:42 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 Mike Hearn 2002-11-12 06:03:55 EST

Please read this:

http://www.mail-archive.com/jde@sunsite.dk/msg05179.html

To save JDEE users like myself some hassle in the future, would it be possible
to ship this in the .xemacs/init.el file as standard?

Comment 1 Jens Petersen 2002-11-12 06:51:34 EST

Better still I am going to try to uncomment the definition in
simple.el in the next package release.  Hopefully that won't
break anything...

Comment 2 Jens Petersen 2002-11-12 09:47:13 EST

Fix is in xemacs-21.4.10-1.  Thanks.

Comment 3 Mike Hearn 2002-11-12 09:52:21 EST

Ta very much.

Comment 4 Ville Skyttä 2002-11-17 16:06:20 EST

This change seems plain wrong to me.  deactivate-mark or transient-mark-mode
don't have a meaning in XEmacs.  The deactivate-mark errors people are seeing
with RedHat's XEmacs and JDE are actually caused by another bug, #75440.  Please
back this one out.

Comment 5 Jens Petersen 2002-11-17 21:44:00 EST

Oops, I guess you're right.  I'll backout the change in the next
package release.  Thanks.

Comment 6 Jens Petersen 2002-11-18 20:41:19 EST

Done in 21.4.10-3.

Comment 7 Ville Skyttä 2002-11-21 14:56:01 EST

Thanks.

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