| idlwave help [message #27489] |
Wed, 24 October 2001 15:27  |
Ken Mankoff
Messages: 158
Registered: February 2000
|
Senior Member |
|
|
Hi,
I have been fooling around more with the IDLWAVE mode, but have run into a
problem. I have searched Carstens pages, but presumably missed the answer.
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:
No tag table loaded; try M-x visit-tag-table
I ran this in my idwave dir:
perl --etags @/tools/rsi/idl
and it built an IDLTAGS file. I then did M-x visit-tag-table, and gave it
the IDLTAGS file that idltags built.
now, when I type "plo ESC-TAB", it fills in with "plot__fields", not
"plot", as I would expect.
Any ideas anyone?
Thanks,
-k.
--
Ken Mankoff
LASP://303.492.3264
http://lasp.colorado.edu/~mankoff/
|
|
|
|
| Re: idlwave help [message #27576 is a reply to message #27489] |
Fri, 26 October 2001 01:29  |
dominik
Messages: 47
Registered: June 2000
|
Member |
|
|
>>>> > "KM" == Ken Mankoff <mankoff@I.HATE.SPAM.cs.colorado.edu> writes:
KM> My problem is that Alt-Tab is set up in Linux like it is in Windows: to
KM> cycle windows. Apparently my emacs config is set up correctly (using my
KM> local dir), and all that was required was to bind idlwave-complete to a
KM> new key sequence.
Or change the Linux setup to use something else for window cycling :-)
- Carsten
|
|
|
|
| Re: idlwave help [message #27602 is a reply to message #27489] |
Thu, 25 October 2001 11:05 |
Ken Mankoff
Messages: 158
Registered: February 2000
|
Senior Member |
|
|
On Thu, 25 Oct 2001, JD Smith wrote:
> 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.
>
> 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)))
>
Thank you!
My problem is that Alt-Tab is set up in Linux like it is in Windows: to
cycle windows. Apparently my emacs config is set up correctly (using my
local dir), and all that was required was to bind idlwave-complete to a
new key sequence.
-k.
--
Ken Mankoff
LASP://303.492.3264
http://lasp.colorado.edu/~mankoff/
|
|
|
|
| Re: idlwave help [message #27603 is a reply to message #27489] |
Thu, 25 October 2001 10:52 |
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.
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
