| IDLWAVE Mac OS X [message #49258] |
Wed, 12 July 2006 01:00  |
jgc
Messages: 10
Registered: July 2006
|
Junior Member |
|
|
Hi there,
(This is a question for a non-computer expert. I am sorry but if you
are an expert, I believe your good intentions, but you will shower me
with a megaton of computer bablespeak that I will be unable to
understand, even if I ca read Sanskrit backwards)
Has any of you idlwave running smoothly on a Mac OS X?
Idlde in X11 deserves the price of MrMs universe ugliest and greyest,
so I am trying idlwave.
I get emacs to recognise idl .pro files, and it attempt to show the idl
toolbars, but then, everything dissapear, when I invoque the idl shell
(or C-c C-s) two terminals open up separately, no inside buffer on
emacs. I wonder if you will be willing to share some hints on the
instruccions in your .emacs file, how many .emacs and .profiles and
where (where by default, I know that you can customise everything).
It looks to me that macs are rather pseudo-unix, and idl for macs does
not run with /../../bin/idl
but rather with /applcations/rsi/idl_6.2/idl.app, which seems to be in
rather bad terms with emacs
Many many thanks in advance for your answer, and many thanks to the
cube if it is in plain English.
Javier
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: IDLWAVE Mac OS X [message #49381 is a reply to message #49258] |
Mon, 17 July 2006 08:00  |
Kenneth P. Bowman
Messages: 585
Registered: May 2000
|
Senior Member |
|
|
In article <1153101510.116804.56860@p79g2000cwp.googlegroups.com>,
wallabadah@hotmail.com wrote:
> TextWrangler/BBEdit use 'codeless' text modules, which are XML files
> containing the specs for a given language. No SDK or compiling
> required. They're documented in Appendix-C of the TextWrangler manual.
>
> I've got a working version I can post here if people want - the only
> thing that doesn't work is 'function definitions', probably because all
> those begins and ends get a bit confusing (ie. 'end' is used in several
> ways, not just to end a procedure/function).
If you can post it here or e-mail it to me (k-bowman at tamu.edu), I
would be happy to make it available on my IDL web page (idl.tamu.edu).
Thanks, Ken
|
|
|
|
| Re: IDLWAVE Mac OS X [message #49382 is a reply to message #49258] |
Mon, 17 July 2006 05:49 |
btt
Messages: 345
Registered: December 2000
|
Senior Member |
|
|
wallabadah@hotmail.com wrote:
> Kenneth P. Bowman wrote:
>> In article <1152758616.309618.91380@35g2000cwc.googlegroups.com>,
>> wallabadah@hotmail.com wrote:
>>
>>> On the subject of TextWrangler - it's also possible to use syntax
>>> highlighting, which can be a big help.
>> Is there an IDL plug-in for TextWrangler/BBEdit? I have never been able
>> to find one. They provide a software development kit for creating such
>> things, but I don't know all (any?) of the technical bits required to
>> make one.
>>
>> Ken Bowman
>
> TextWrangler/BBEdit use 'codeless' text modules, which are XML files
> containing the specs for a given language. No SDK or compiling
> required. They're documented in Appendix-C of the TextWrangler manual.
>
> I've got a working version I can post here if people want - the only
> thing that doesn't work is 'function definitions', probably because all
> those begins and ends get a bit confusing (ie. 'end' is used in several
> ways, not just to end a procedure/function).
>
> SubEthaEdit (SEE) uses different terminology for their 'Language
> Modes', although they're still defined in a set of XML files. SEE is a
> bit more flexible in that it allows you to define different types of
> keywords, with different highlighting - eg. System Procedures, System
> Procedures, Library Procedures, Library Functions, etc. TextWrangler
> just recognises a single type of keyword and only one style of
> highlighting. However, for some reason I can't recall right now, I
> never liked SEE much, and preferred TextWrangler.
>
> I have working versions of the language modules for both programs,
> although they're probably not 100% up to date. Let me know if you want
> them, and I'll work out how to post them to the list...
>
> Will Powell
>
Hello,
I never could get my fingers to work the emacs shortcuts and I haven't
used TextWrangler at all. However, I use SubEthaEdit for all my coding
(not just IDL). It handles regex-y string handling for search and
replace, block editing,syntax highlighting, colored printing, etc. Larry
van Peursem, formerly of RSI, wrote the language mode for IDL, although
it maybe getting a bit dated now. Recent versions of SubEthaEdit have
greatly improved speediness. The most recent version has introduced a
compile-and-run option which runs an AppleScript that invokes the
compiler for java, perl, etc. I haven't figured out how to make it do
the same with IDL yet.
As Will points out, it comes with a command line which I have wrapped
inside with a SPAWN command from IDL...
IDL> see, "arrow"
and, pop!, "arrow.pro" is opened. I have one for objects, too,
IDL> osee, "myobject"
which will add the "__define.pro" for the lazy types like me.
One thing I would wish for SubEthaEdit is to have optional tabbed windows.
It is worth a test drive. http://www.subethaedit.net/
Ben
|
|
|
|
| Re: IDLWAVE Mac OS X [message #49383 is a reply to message #49327] |
Sun, 16 July 2006 18:58 |
wallabadah
Messages: 28
Registered: November 2005
|
Junior Member |
|
|
Kenneth P. Bowman wrote:
> In article <1152758616.309618.91380@35g2000cwc.googlegroups.com>,
> wallabadah@hotmail.com wrote:
>
>> On the subject of TextWrangler - it's also possible to use syntax
>> highlighting, which can be a big help.
>
> Is there an IDL plug-in for TextWrangler/BBEdit? I have never been able
> to find one. They provide a software development kit for creating such
> things, but I don't know all (any?) of the technical bits required to
> make one.
>
> Ken Bowman
TextWrangler/BBEdit use 'codeless' text modules, which are XML files
containing the specs for a given language. No SDK or compiling
required. They're documented in Appendix-C of the TextWrangler manual.
I've got a working version I can post here if people want - the only
thing that doesn't work is 'function definitions', probably because all
those begins and ends get a bit confusing (ie. 'end' is used in several
ways, not just to end a procedure/function).
SubEthaEdit (SEE) uses different terminology for their 'Language
Modes', although they're still defined in a set of XML files. SEE is a
bit more flexible in that it allows you to define different types of
keywords, with different highlighting - eg. System Procedures, System
Procedures, Library Procedures, Library Functions, etc. TextWrangler
just recognises a single type of keyword and only one style of
highlighting. However, for some reason I can't recall right now, I
never liked SEE much, and preferred TextWrangler.
I have working versions of the language modules for both programs,
although they're probably not 100% up to date. Let me know if you want
them, and I'll work out how to post them to the list...
Will Powell
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
