comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » idlwave help
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Return to the default flat view Create a new topic Submit Reply
Re: idlwave help [message #27603 is a reply to message #27489] Thu, 25 October 2001 10:52 Go to previous message
John-David T. Smith is currently offline  John-David T. Smith
Messages: 384
Registered: January 2000
Senior Member
Ken Mankoff wrote:
>
> On Thu, 25 Oct 2001, John-David Smith wrote:
>> Ken Mankoff wrote:
>>>
>>> I would like to start using completion in the editing buffer, not just the
>>> shell. I think this is bound to M-TAB (or ESC-TAB). When I hit that, I get
>>> the following:
>>
>> This is all covered in the INSTALL file you'll find in the distribution.
>
> Hi JD,
>
> I had done a custom location install before, as I dont have root
> priviliges on my main computer. I do on another one, and am now testing
> this there. I have followed the INSTALL file verbatim, and here is my
> .emacs:
>
> ;(setq load-path (cons "~/local/idlwave-4.9d" load-path))
> (autoload 'idlwave-mode "idlwave" "IDLWAVE Mode" t)
> (autoload 'idlwave-shell "idlw-shell" "IDLWAVE Shell" t)
> (setq auto-mode-alist
> (cons '("\\.pro\\'" . idlwave-mode) auto-mode-alist))
> (setq idlwave-help-directory "/usr/local/etc")
>
> If I do this, and emacs a .pro file, it starts in my default major-mode,
> Text. However, even in text mode, ESC-TAB *does* bring up completions. But
> obviously, font-lock-mode and other stuff does not work.
>
> Also, the *Messages* buffer has this:
> File mode specification error: (file-error "Cannot open load file" "idlwave")
>
> -----
> If I change my .emacs so that the commented line above is uncommented,
> then when I edit a file, I get loaded into "IDLWAVE Abbrev Fill" mode,
> syntax is highlighted, and "C-c,?" brings up help, etc... In short,
> everything works but the ESC-TAB. If I hit that, it says that 'tags are
> not loaded'.
>
> The confusing thing is that ~/local/idlwave-4.9d is where I ran
> % make; su; make install-all
>
> Ideally, I would like to run everything out of ~/local/idlwave, so that I
> can have the same setup on all my computers, even where i am not root.

Aha, I think I see. You do need idlwave on your path, so the commented
line is necessary unless you allow IDLWAVE to be installed in a standard
location. "make install-all" copies things into
/usr/local/share/emacs/site-lisp (unless you told it otherwise), and
/usr/local/etc for the help file. You might consider using this default
location, instead of ~/local/idlwave-4.9d, in the load-path statement.
Alternatively, if you want to leave things where they are, simply omit
the "make install-all", and add the build directory to load-path.

In case you are curious, the problem is that different Emaacs
installations have different default "load-path" variables for emacs
(similar to the !PATH variable for IDL .pro files). Some include
/usr/local/share/emacs, others don't. You can figure out if yours does
by doing "[C-h v] load-path [Ret]" to inspect the path variable.

The problem here is that [ESC-Tab] is actually *not* bound to anything
by IDLWAVE, but [M-Tab] is, so the former defaults to the standard emacs
binding. I always use the Meta form, since it's much faster (Meta is
the same as Alt, for all you PC users), and I encourage you to do the
same. If you can't, or just want ESC-Tab to work in addition, add
something to .emacs like:

(add-hook 'idlwave-mode-hook
(lambda ()
(local-set-key [?\e?\t] 'idlwave-complete)))

Good luck,

JD

P.S. RSI has dealt IDLWAVE a noticeable blow with v5.5, including no
documentation updates, and changed format for certain "help" reports.
Hopefully a new version which overcomes these issues will be
forthcoming.
[Message index]
 
Read Message
Read Message
Read Message
Read Message
Previous Topic: Re: How to do a "match merge"?
Next Topic: Rotate 3D matrix

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Sun Oct 12 16:54:08 PDT 2025

Total time taken to generate the page: 0.32031 seconds