> On Thursday, June 20, 2002, at 01:19 PM, ima sudonim wrote:
>
I got VIM (that's a GREAT tutorial that came with), joe (a wordstar
klone -- I used to use Borland sidekick tsr to do my compiles so I don't
have to memorize the commands at least), nedit give errors:
NEdit: Locale not supported by C library.
NEdit: Using C locale instead.
NEdit: Can't open display
X is screwed up, giving:
[localhost:plib_examples-1.4.1/src/js] root# startx -quartz
XFree86 Version 4.1.0 / X Window System
(protocol Version 11, revision 0, vendor release 6510)
Release Date: 2 June 2001
If the server is older than 6-12 months, or if your hardware is
newer than the above date, look for a newer version before
reporting problems. (See http://www.XFree86.Org/FAQ)
Operating System: Darwin
Display mode: IOKit
Fatal server error:
Failed to connect as window server!
Quit the Mac OS X window server or use the -quartz option.
OsVendorFatalError
AbortDDX
Quitting XDarwin...
giving up.
xinit: No such file or directory (errno 2): unable to connect to X
server
xinit: No such process (errno 3): Server error.
[localhost:plib_examples-1.4.1/src/js] root#
Using BBEDIT lite but also unsure if it can do the compile error/edit
thing...
Slickedit BSD version won't install on macos x, they're not making a
macos x version at this time. None of these afaik alow me to jump right
into an edit session from a compiler error or warning msg. Am I missing
something in my setup or is there a magic keypress in these editors to
do this?
TIA,
ima
> > I'd like to have something that I could set up to do my compiles, go
> from
> > errors straight to an editing session at the point of error. Find in
> > file like grep or the ability to call an external command like grep
> would
> > be great too. It would either have to be open source, or macos x
> > compatible to work for me. A powerful c-like macro editor would be a
> > plus... 8-) I've heard of something called joe, but think that it
> > requires a library that I can't get on macos x. Any other
> suggestions?
>
> I would really recommend Project Builder, which I would expect that you
> already have installed. There is an effort ongoing to try to get
> FlightGear to build natively under Project Builder, bit I have been
> having
> some problems with my hand-build projects (more talented people than I
> are
> working on getting the autoconfig to generate the project files). You
> could try using Project Builder's legacy interface and see if it fits
> the
> bill.
>
>
>http://developer.apple.com/techpubs/macosx/Darwin/PortingUNIX/compiling/Building_Le_ect_Builder.
> html
>
The link is out of date, i think, but I'll look into it.
> I haven't given it a try, but I may be doing so. Some questions I have
> concerning the legacy interface is that I cannot generate Frameworks or
> .app wrappers, unless the underlying makefile does so.
>
> Jonathan Polley
>
>
>
>
_______________________________________________
Flightgear-devel mailing list
[EMAIL PROTECTED]
http://mail.flightgear.org/mailman/listinfo/flightgear-devel
