GNU bug report logs - #61400
Different filling for verbatim macros

Previous Next

Package: auctex;

Reported by: Arash Esbati <arash <at> gnu.org>

Date: Fri, 10 Feb 2023 08:53:01 UTC

Severity: normal

Done: Arash Esbati <arash <at> gnu.org>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Ikumi Keita <ikumi <at> ikumi.que.jp>
To: 61400 <at> debbugs.gnu.org
Cc: Arash Esbati <arash <at> gnu.org>, Tassilo Horn <tsdh <at> gnu.org>
Subject: bug#61400: Different filling for verbatim macros
Date: Mon, 13 Feb 2023 14:34:39 +0900
Following up myself.

>>>>> Ikumi Keita <ikumi <at> ikumi.que.jp> writes:
> (2) `LaTeX-verbatim-p' is currently used only in
> `fill-nobreak-predicate', `LaTeX-search-forward-comment-start' and
> `TeX-in-comment' (through `TeX-verbatim-p-function'):

Sorry, there is another instance of usage in `TeX-insert-dollar'. That
is safe for the proposed change for `LaTeX-verbatim-p', too.

> (By the way, as written in the comment of the patch, I don't understand
> the reason why the while loop in `LaTeX-verbatim-macro-boundaries' goes
> back to the previous line. Is there any \verb variant, say in fancyverb
> or fvextra, which allows newline in its argument?)

I misunderstood the role of `(forward-char -1)'. (^_^;) It passes over
the backslash. Going back to the previous line is just an unintentional
side effect, `(bobp)' in front of `(forward-char -1)' should actually be
`(bolp)'.

Regards,
Ikumi Keita
#StandWithUkraine #StopWarInUkraine




This bug report was last modified 2 years and 155 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.