Uwe Brauer writes:
> Now in that file, I turn on invisible toggle on and off the
> font-lock-mode and voila, ^ and _ disappears. Now again I set it to
> nil I do (font-lock-flush) turn on and off font lock, no way the ^ and
> _ not show up again.
That's a bug I've left there for you to discover.
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, simplify-TeX-parse-error has been updated
via 6f365c53646728de857796bbf96cabe5a121cffa (commit)
via
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 d4ba58533a321bb2ec04a6589de1905190f2e15c (commit)
from 647a8fc8a5678eab4
Mosè Giordano writes:
(after a bit of testing)! I think we have accumulated more than
enough additions, fixes, and new features to think about that.
>>>
>>> Regarding testing. I think `LaTeX-command-run-all-section' should
>>> check if it's on a LaTeX document, for example in a plain
Hi Tassilo,
2015-09-04 11:02 GMT+02:00 Tassilo Horn :
> Mosè Giordano writes:
>
>>> (after a bit of testing)! I think we have accumulated more than enough
>>> additions, fixes, and new features to think about that.
>>
>> Regarding testing. I think `LaTeX-command-run-all-section' should
>> check
> Uwe Brauer writes:
> A simply `font-lock-flush' should suffice.
Hm it does not work, look at the following example
(setq font-latex-fontify-script nil)
Now in that file, I turn on invisible toggle on and off the
font-lock-mode and voila, ^ and _ disappears. Now again I set it to nil
I do (fo
Uwe Brauer writes:
> Especially I wanted to see how to toggle it off and on in a buffer.
>
> Rationale: if the feature is set to invisible and you write __ this is
> a LaTeX error but you would *not* see it (I know this what was the
> mayor objection against that feature.)
>
> When I run customiz
> Uwe Brauer writes:
I downloaded the latest git checkin and played around with the new feature.
> (setq font-latex-fontify-script 'invisible)
Especially I wanted to see how to toggle it off and on in a buffer.
Rationale: if the feature is set to invisible and you write __ this is a
LaTeX
Mosè Giordano writes:
>> Sure, but I am in a latex buffer and still get:
>
> Uh, here I get C-c C-a as expected :-/
Me, too, with emacs 24.5. So that's a regression in the current master.
I've reported it as bug#21412.
Thanks,
Tassilo
___
auctex-dev
Marcin Borkowski writes:
>> Do you know why \\[universal-argument] expands to `C-u' in
>> `TeX-command-run-all's docstring but \\[TeX-command-run-all] expands
>> to `M-x TeX-command-run-all' instead of `C-c C-a'?
>
> Maybe this?
>
> ‘\’
> stands for no text itself. It is used only for a sid
2015-09-04 13:47 GMT+02:00 Tassilo Horn :
> Sure, but I am in a latex buffer and still get:
Uh, here I get C-c C-a as expected :-/
Bye,
Mosè
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
Mosè Giordano writes:
>>> * tex-buf.el (TeX-command-run-all): Use `universal-argument' to
>>> reference C-u.
>>
>> Do you know why \\[universal-argument] expands to `C-u' in
>> `TeX-command-run-all's docstring but \\[TeX-command-run-all] expands to
>> `M-x TeX-command-run-all' instead of
Hi Tassilo,
2015-09-04 13:33 GMT+02:00 Tassilo Horn :
> Mosè Giordano writes:
>
> Hi!
>
>> * tex-buf.el (TeX-command-run-all): Use `universal-argument' to
>> reference C-u.
>
> Do you know why \\[universal-argument] expands to `C-u' in
> `TeX-command-run-all's docstring but \\[TeX-command
On 2015-09-04, at 13:33, Tassilo Horn wrote:
> Do you know why \\[universal-argument] expands to `C-u' in
> `TeX-command-run-all's docstring but \\[TeX-command-run-all] expands to
> `M-x TeX-command-run-all' instead of `C-c C-a'?
Maybe this?
‘\’
stands for no text itself. It is used only
Mosè Giordano writes:
Hi!
> * tex-buf.el (TeX-command-run-all): Use `universal-argument' to
> reference C-u.
Do you know why \\[universal-argument] expands to `C-u' in
`TeX-command-run-all's docstring but \\[TeX-command-run-all] expands to
`M-x TeX-command-run-all' instead of `C-c C-a'?
> Uwe Brauer writes:
> You normally don't include png files when you care about the quality of
> your output. So usually, the graphic files are EPS or PDF. Ok, these
> could be converted to PNG in order to show them inline. But a harder
> problem is that you don't need to (and
Uwe Brauer writes:
>Tassilo> Glad we have that now. Then I'll do the region/section stuff
>Tassilo> ASAP, Mosè does the Index suggestion, and then we can have a
>Tassilo> new shiny release (after a bit of testing)! I think we have
>Tassilo> accumulated more than enough additions,
Mosè Giordano writes:
>> (after a bit of testing)! I think we have accumulated more than enough
>> additions, fixes, and new features to think about that.
>
> Regarding testing. I think `LaTeX-command-run-all-section' should
> check if it's on a LaTeX document, for example in a plain tex docume
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 647a8fc8a5678eab472daadc43f9b1c5e9e01264 (commit)
from e2b24137ddfcda625
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, simplify-TeX-parse-error has been updated
via 0719b3db936ad7eddbbd6bd083fb02c72f04a9e6 (commit)
via
Hi Tassilo,
2015-09-04 6:56 GMT+02:00 Tassilo Horn :
> Tassilo Horn writes:
>
Is `TeX-command-run-all' an option? Rational: `TeX-command-list'
mostly uses `run'. +1 for C-c C-a.
>>>
>>> Uhm, good point but I really don't know which option to choose: for
>>> me `TeX-command-compile-all
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 e2b24137ddfcda625264d513da6de3bb0b5270b3 (commit)
from 22c7d9fb60ddc7110
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, simplify-TeX-parse-error has been updated
via 9ee4f28a47e433836829ff3f1b028f3376f34101 (commit)
via
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 22c7d9fb60ddc71102d41ea45dcad5493202ff70 (commit)
from c3cb0ff1f6dc2f699
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, simplify-TeX-parse-error has been updated
via 0a0eb3eea718b5b4aaa07e7b04add24d9b2e7cc3 (commit)
from
>> "Tassilo" == Tassilo Horn writes:
Hi,
Tassilo> Glad we have that now. Then I'll do the region/section stuff
Tassilo> ASAP, Mosè does the Index suggestion, and then we can have a
Tassilo> new shiny release (after a bit of testing)! I think we have
Tassilo> accumulated more than e
26 matches
Mail list logo
