NEdit problems with ***tif on xyz system (was: Future of NEdit?)

[Paterline, David L.]

Is all this discussion about how to get NEdit to work with "abc" version
of Motif on "xyz" system more appropriate for the developer's list?

-
David L. Paterline
Principal Engineer       
Westinghouse Electric Company
Nuclear Fuel Engineering
Engineering Computing
paterldl at westinghouse.com   
PH: 412-374-2286
FX: 412-374-2284


-----Original Message-----
From: discuss-bounces at nedit.org [mailto:discuss-bounces at nedit.org] On
Behalf Of Duane Clark
Sent: Tuesday, November 27, 2007 4:38 PM
To: General NEdit discussion list
Subject: Re: Future of NEdit?

Aaron Hsu wrote:
> I just want to make a small comment here. People who are looking for  
> stability and reliability in their Operating Systems should not run  
> Fedora. In my personal experience, programs that should work, have  
> strange and sometimes unidentifiable "issues" that make no sense. The

> same goes for Ubuntu's systems, which, though reliable, are not from  
> my limited experience, known for being really stable.
> 
> I would be interested to see if many of these issues can be duplicated

> on a Slackware system. If so, it *may* be easier to isolate the  
> issues. Of course, I speak only of the "general" case, and not of the

> specific incident at hand.

Oh, I understand that I am running a system that is not completely 
stable. The number of updates that still come in every week remind me of

that;) But at least I'm not trying Fedora 9 test :) I've used HPUX, 
Solaris, and several versions of Redhat/Fedora since RH6, totalling 
about 18 years. So I at least have a reasonably good idea of what I am 
getting into, and am willing to deal with the accompanying "challenges".

But I think that Fedora/Ubuntu give an "early warning" of upcoming 
problems. And really, these problems should be addressed in a beta 
version like Fedora 9 test, so that ordinary users on stable systems 
never see a problem. Eventually slackware and other systems will be 
adopting the kernel and X xerver code used there.

On the other hand, my system is being used to run a bunch of complex 
commercial engineering/math software. And all of it runs extremely well,

and is quite stable. I still use nedit primarily because I like the 
simple VHDL language package for it. It actually works reasonably good, 
even with lesstif. The main problem is that every once in a while (I 
have not yet isolated the trigger) it will stop allowing copy to the 
clipboard, generating a message about the clipboard being locked. 
Exiting and restarting nedit restores normal copy/paste operation.

I guess since I have used the Motif file open dialog for 18 years, I 
never really thought about it as clumsy :) But I can see the limitations

Adam mentions, now that he points them out.
-- 
NEdit Discuss mailing list - Discuss at nedit.org
http://www.nedit.org/mailman/listinfo/discuss