Format of compilation-error-regexp-alist-alist

Format of compilation-error-regexp-alist-alist

[Lennart Borgman]

I do not understand the format of `compilation-error-regexp-alist-alist. 
I can not find in the documentation how the first element in the entries 
are used. Where is absoft, ada, aix etc used? If I want to add a new 
entry to the alist for support of a new command what should this new 
command output to match the names (absoft, ada etc)?

Am I missing something in the documentation?

Re: Format of compilation-error-regexp-alist-alist

[Kevin Rodgers]

Lennart Borgman wrote:
> I do not understand the format of `compilation-error-regexp-alist-alist. 
> I can not find in the documentation how the first element in the entries 
> are used. Where is absoft, ada, aix etc used? If I want to add a new 
> entry to the alist for support of a new command what should this new 
> command output to match the names (absoft, ada etc)?
> 
> Am I missing something in the documentation?

Well, it's doc string says:

| Alist of values for `compilation-error-regexp-alist'

And if you click on the link in the *Help* buffer, that
variable's doc string says:

| Instead of an alist element, you can use a symbol, which is
| looked up in `compilation-error-regexp-alist-alist'.  You can see
| the predefined symbols and their effects in the file
| `etc/compilation.txt' (linked below if you are customizing this).

So I think a new command should have its own symbol.

-- 
Kevin Rodgers

Re: Format of compilation-error-regexp-alist-alist

[Lennart Borgman]

Kevin Rodgers wrote:
> Lennart Borgman wrote:
>> I do not understand the format of 
>> `compilation-error-regexp-alist-alist. I can not find in the 
>> documentation how the first element in the entries are used. Where is 
>> absoft, ada, aix etc used? If I want to add a new entry to the alist 
>> for support of a new command what should this new command output to 
>> match the names (absoft, ada etc)?
>>
>> Am I missing something in the documentation?
>
> Well, it's doc string says:
>
> | Alist of values for `compilation-error-regexp-alist'
>
> And if you click on the link in the *Help* buffer, that
> variable's doc string says:
>
> | Instead of an alist element, you can use a symbol, which is
> | looked up in `compilation-error-regexp-alist-alist'.  You can see
> | the predefined symbols and their effects in the file
> | `etc/compilation.txt' (linked below if you are customizing this).
>
> So I think a new command should have its own symbol.
>
Thanks for the answer. I finally understood that I could bind 
`compilation-error-regexp-alist' etc before calling (compile ...). That 
made it very simple.