[AUCTeX-diffs] GNU AUCTeX branch, master, updated. 0c01b75a9b990bf7810bd228d069548dea2c7c3e

2021-09-10 Thread Ikumi Keita
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "GNU AUCTeX". The branch, master has been updated via 0c01b75a9b990bf7810bd228d069548dea2c7c3e (commit) from

[AUCTeX-commit] GNU AUCTeX branch, master, updated. 0c01b75a9b990bf7810bd228d069548dea2c7c3e

2021-09-10 Thread Ikumi Keita
This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "GNU AUCTeX". The branch, master has been updated via 0c01b75a9b990bf7810bd228d069548dea2c7c3e (commit) from

Re: [FR] Recognize L3 \msg_line_context: on warning parsing

2021-09-10 Thread Florent Rougon
Hi Tassilo, Tassilo Horn wrote: > That's already caught by the AUCTeX error parser, `TeX-next-error' jumps > to the correct position which is also listed in `TeX-error-overview'. > So nothing to be done here on our side, right? Indeed, I hadn't checked but it works fine because of the

Re: [FR] Recognize L3 \msg_line_context: on warning parsing

2021-09-10 Thread Tassilo Horn
Florent Rougon writes: Hi Florent, > Unrelated to your question but related to the thread: there is > another, less common way to print error messages, which works in > expansion-only contexts: \msg_expandable_error:nnn and friends. Since > neither \message nor \write work in expansion-only