Re: master d486947c: Enable LaTeX abbrevs in docTeX mode buffer.
> Arash Esbati writes:
>> +@item
>> +Now @LaTeX{} abbreves are available in doc@TeX{} mode buffers.
> ^
> Thanks for installing this change which is reasonable, I think. I think
> there is one 'e' too much in the entry above, should I fix it?
Oops, thanks. I fixed it ;-)
Bye,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine
master 66941e5a: ; * doc/changes.texi: Fix typo.
branch: master
commit 66941e5aad4d9ba86fbedc0df2cc71802e43104d
Author: Ikumi Keita
Commit: Ikumi Keita
; * doc/changes.texi: Fix typo.
---
doc/changes.texi | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/changes.texi b/doc/changes.texi
index f9e7ee58..cbb341c6 100644
--- a/doc/changes.texi
+++ b/doc/changes.texi
@@ -15,7 +15,7 @@
@AUCTeX{} now requires GNU Emacs 26.1 or higher.
@item
-Now @LaTeX{} abbreves are available in doc@TeX{} mode buffers.
+Now @LaTeX{} abbrevs are available in doc@TeX{} mode buffers.
@end itemize
@heading News in 13.2
Re: verbatim shorthand problem
Arash Esbati wrote (Fri, Aug 25, 2023 at 11:38:36AM +0200):
> Can you please file a bug report for this, incl. a MWE starting with
> emacs -Q? TIA.
>
> For the time being, you can use delimiters instead of braces for the
> optional argument which works, e.g.:
>
> \lstinline[language=C,basicstyle=\ttfamily]|for (i=0; i<8; i++)
> printf("%c\n"), str1 [ i]);|
Thanks very much for confirming, and for the work-around! Will file the bug
report with an MWE this weekend.
Warm regards,
Mandar.
Re: verbatim shorthand problem
Arash Esbati writes:
> For the time being, you can use delimiters instead of braces for the
> optional argument which works, e.g.:
mandatory argument, sorry.
> \lstinline[language=C,basicstyle=\ttfamily]|for (i=0; i<8; i++)
> printf("%c\n"), str1 [ i]);|
Re: verbatim shorthand problem
Mandar Mitra writes:
> I'm facing a fontification problem with \lstinline + beamer. Just
> wondering if it might be vaguely related to your fix for
> fancyvrb.el. I have the following line in a frame environment:
>
> \lstinline[language=C,basicstyle=\ttfamily]{for (i=0; i<8; i++)
> printf("%c\n", str1[i]);} \\
>
> The attached screenshot suggests that the closing ] of str1[i] somehow
> throws fontification off-track.
No, it has nothing to do with my latest change to fancyvrb.el. I can
reproduce what you describe but I don't understand why. As you said,
AUCTeX currently gets confused by the pair of brackets inside the
mandatory argument
> If this does NOT sound like an "Ah, of course" type problem, then I'll
> try and put together an MWE starting with emacs -Q. Could you please
> let me know?
Can you please file a bug report for this, incl. a MWE starting with
emacs -Q? TIA.
For the time being, you can use delimiters instead of braces for the
optional argument which works, e.g.:
\lstinline[language=C,basicstyle=\ttfamily]|for (i=0; i<8; i++) printf("%c\n"),
str1 [ i]);|
Best, Arash
