2013/5/26 Mosè Giordano :
> Hi Ralf,
>
> 2013/5/25 Ralf Angeli :
>> What worked in my case was replacing the second and third occurrences
>> (not the first one) of `TeX-in-commented-line' with `TeX-in-comment'.
> It seems to work also for me and in a ~100 KiB file I don't get the
> "Lisp nesting ex
Hi Ralf,
2013/5/25 Ralf Angeli :
> What worked in my case was replacing the second and third occurrences
> (not the first one) of `TeX-in-commented-line' with `TeX-in-comment'.
It seems to work also for me and in a ~100 KiB file I don't get the
"Lisp nesting exceeds `max-lisp-eval-depth'" error I
* Mosè Giordano (2013-05-25) writes:
> I don't intend to apply any of these changes without further
> discussion, I know they may break something ;-)
Phew. (c;
> For the time being I haven't other ideas.
The problem is that even if `LaTeX-current-environment' is called
outside of a comment, it
Hi Ralf,
2013/5/25 Ralf Angeli :
> I'd appreciate it if you didn't do such a change. I've tried hard to
> keep stuff in the commented and non-commented parts of a LaTeX file
> separate. If those get mixed up, you cannot put anything you want
> anymore into comments and may get surprising behavio
* Mosè Giordano (2013-05-24) writes:
> Hi David,
>
> 2013/5/24 David Kastrup :
>> Huh? fontification is _lazy_ by default. Off-screen areas are not
>> fontified unless you page over them.
Is this a problem with the current code?
> How about not checking comments in `LaTeX-current-environment'?
Mosè Giordano writes:
> Hi David,
>
> 2013/5/24 David Kastrup :
>> Huh? fontification is _lazy_ by default. Off-screen areas are not
>> fontified unless you page over them.
>>
>> Check out the documentation for jit-lock-mode, the variant of font-lock
>> that is active as Emacs' _default_.
> Ok,
Hi David,
2013/5/24 David Kastrup :
> Huh? fontification is _lazy_ by default. Off-screen areas are not
> fontified unless you page over them.
>
> Check out the documentation for jit-lock-mode, the variant of font-lock
> that is active as Emacs' _default_.
Ok, got it, thanks for the reference.
M
Mosè Giordano writes:
> With my patch it becomes
> (if (fboundp 'font-latex-faces-present-p)
> (font-latex-faces-present-p 'font-latex-verbatim-face)
> (or (member (LaTeX-current-verbatim-macro)
> (LaTeX-verbatim-macros-with-delims))
> (member (TeX-current-macro) (La
Hi David,
2013/5/24 David Kastrup :
> Mosè Giordano writes:
>
>> It seems `LaTeX-verbatim-p' is the bottleneck when executing
>> `TeX-in-comment' in latex mode. The attached patch should speedup
>> `LaTeX-verbatim-p' (and so `LaTeX-current-environment' with
>> `TeX-in-comment') when `font-latex
It seems `LaTeX-verbatim-p' is the bottleneck when executing
`TeX-in-comment' in latex mode. The attached patch should speedup
`LaTeX-verbatim-p' (and so `LaTeX-current-environment' with
`TeX-in-comment') when `font-latex-faces-present-p' is available,
otherwise it is still really slow. Is there
Hi Gerard,
2013/5/23 Gerard Brunick :
> I believe I have found a bug in LaTeX-current-environment which reads:
> [...]
Thank you for taking the time to report this bug. The obvious
solution would be to replace `TeX-in-commented-line' with
`TeX-in-comment', but that would sensibly degrade performa
I believe I have found a bug in LaTeX-current-environment which reads:
(defun LaTeX-current-environment (&optional arg)
(setq arg (if arg (if (< arg 1) 1 arg) 1))
(let* ((in-comment (TeX-in-commented-line))
(comment-prefix (and in-comment (TeX-comment-prefix
(save-excursion
12 matches
Mail list logo
