Bug 54561

Summary: Nedit.ad breaks NEdit scripts and fonts
Product: [Unmaintained] kcontrol Reporter: Nathaniel Gray <n8gray>
Component: krdbAssignee: Dirk Mueller <mueller>
Status: RESOLVED FIXED    
Severity: normal CC: brian.foddy, TheCesars, w.jones
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Nathaniel Gray 2003-02-12 20:24:12 UTC
Version:           unknown (using KDE 3.1.0)
Installed from:    compiled sources
Compiler:          gcc version 3.2 (Mandrake Linux 9.0 3.2-1mdk)
OS:          Linux (i686) release 2.4.19-16mdkcustom

I'm an NEdit developer and the NEdit.ad file that you supply with KDE has been causing many bug reports for us.  (e.g. https://sourceforge.net/tracker/index.php?func=detail&aid=561659&group_id=11005&atid=111005) There are two main problems that I am aware of.

1.  By setting "nedit*shell: /bin/sh" you break several of the entries on our shell menu.  This resource is only meant to be set by those who know what they're getting into and should not be set without the user's awareness.

2.  It appears that in some setups (Redhat 8.0 seems problematic) the FONTLIST macro is not expanded, leading to bad fonts and the error: 
Cannot convert string "FONTLIST" to type FontStruct

If run as root, the error is: 
Cannot convert string "%s" to type %s

I'm not sure if this is a distro problem or a KDE problem, but Nedit.ad is the only file that uses FONTLIST and there have been no reports of similar problems with BACKGROUND or any other krdb macro.
Comment 1 Michael Cesar 2003-03-19 20:07:14 UTC
I have encountered this problem on RH8 w/ it supplied KDE desktop.
Comment 2 Dirk Mueller 2003-04-14 06:47:21 UTC
removed both parts of the Nedit.ad (KDE 3.1.2 or later).  
Comment 3 Dirk Mueller 2003-04-15 03:53:08 UTC
*** Bug 26717 has been marked as a duplicate of this bug. ***
Comment 4 Maksim Orlovich 2003-06-15 04:11:38 UTC
*** Bug 32875 has been marked as a duplicate of this bug. ***