--- Begin Message ---
|
Subject: |
Re: [Ada-mode-users] Keywords not being identified in ada-mode 5.3.1 (or 5.2.2) |
|
Date: |
Tue, 13 Nov 2018 11:11:32 -0700 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/26.0.90 (windows-nt) |
Jonty Needham <address@hidden> writes:
> Keyword identification works in Python and Bash. GPR files are correctly
> coloured too.
>
> When starting emacs with emacs -Q filename.adb, keywords are recognised.
> The ada-mode-version comes up as 4.00.
That's using the old ada-mode distributed in Emacs. To use the ELPA
ada-mode:
emacs -Q
M-x package-initialize
C-c C-f filename.adb
> Note font-lock-keywords is not nil and global-font-lock-mode is not nil
> either.
Ok.
> Now, I don't know yet how to step through execution of ada-mode.el (trying
> to find that out as I'm no lisp guru to say the least) but when I evaluated
> ada-mode.el (in my emacs -Q instance)
Which ada-mode.el? ~/.emacs.d/elpa/ada-mode-5.3 or Emacs/lisp/progmodes ?
> and turned ada-mode off and on I get the following error:
>
> Wrong type argument: sequencep,
> "\\<\\(a\\(?b\\(?\\(?:ort\\|s\\|s\\(?:tract\\)?\\)\\|cce\\(?:pt\\|ss\\)\\|l\\)?:iased\\|l\\)\\|nd\\|rray\\|t\\)\\|b\\(?:egin\\|ody\\)\\|c\\(?:ase\\|onstant\\)\\|d\\(?:e\\(?:clare\\|l\\(?:ay\\|ta\\)\\)\\|igits\\|o)\\|e\\(?:ls\\)?
> (and then a few more like this, couldn't copy/paste as it appeared in the
> command area which disappears when entered).
The "command area" is called the "minibuffer". A copy of all messages
displayed there is in the "*Messages*" buffer.
The value shown is the optimized Ada keywords, but I'm guessing this is
from ada-mode 4.0.
If you try to load ada-mode 5.3 on top of ada-mode 4.0, it's not
surprising you get errors.
--
-- Stephe
--- End Message ---