headers
David Kastrup | 2 Sep 2005 11:33
Picon
Picon

Re: [AUCTeX-commit] auctex texmathp.el

Ralf Angeli <angeli <at> iwi.uni-sb.de> writes:

> CVSROOT:	/cvsroot/auctex
> Module name:	auctex
> Branch: 	
> Changes by:	Ralf Angeli <angeli <at> savannah.gnu.org>	05/09/02 08:43:33
>
> Modified files:
> 	.              : texmathp.el 
>
> Log message:
> 	(texmathp-tex-commands-default): Add "\textrm" as
> 	`arg-off'.
>
> CVSWeb URLs:
> http://savannah.gnu.org/cgi-bin/viewcvs/auctex/auctex/texmathp.el.diff?tr1=5.13&tr2=5.14&r1=text&r2=text

Would seem like the other \textxx commands would be equally fitting
candidates here.

--

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum
Permalink | Reply | 2 comments |
headers
Ralf Angeli | 2 Sep 2005 14:07
Picon

Re: Re: [AUCTeX-commit] auctex texmathp.el

* David Kastrup (2005-09-02) writes:

> Ralf Angeli <angeli <at> iwi.uni-sb.de> writes:
>
>> Log message:
>> 	(texmathp-tex-commands-default): Add "\textrm" as
>> 	`arg-off'.
>
> Would seem like the other \textxx commands would be equally fitting
> candidates here.

Are those commands used so frequently that it is worth adding them?
(I don't typeset lots of math, so I don't really know.)  I don't want
to slow down texmathp unnecessarily.

--

-- 
Ralf
Permalink | Reply | 1 comment |
headers
David Kastrup | 2 Sep 2005 14:23
Picon
Picon

Re: Re: [AUCTeX-commit] auctex texmathp.el

Ralf Angeli <angeli <at> iwi.uni-sb.de> writes:

> * David Kastrup (2005-09-02) writes:
>
>> Ralf Angeli <angeli <at> iwi.uni-sb.de> writes:
>>
>>> Log message:
>>> 	(texmathp-tex-commands-default): Add "\textrm" as
>>> 	`arg-off'.
>>
>> Would seem like the other \textxx commands would be equally fitting
>> candidates here.
>
> Are those commands used so frequently that it is worth adding them?
> (I don't typeset lots of math, so I don't really know.)  I don't want
> to slow down texmathp unnecessarily.

I don't think that something like
\\text\(rm\|it\|sf\|tt...

causes much of a slowdown, since it needs to match \text before the
added performance drain sets in.

--

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum
Permalink | Reply | 0 comments |
headers
Ralf Angeli | 8 Sep 2005 14:57
Picon

Re: Re: Fontification of titles in LaTeX slides

* Reiner Steib (2005-08-03) writes:

> On Wed, Aug 03 2005, Ralf Angeli wrote:
>
>> * Reiner Steib (2005-08-02) writes:
>>> On Tue, Aug 02 2005, Ralf Angeli wrote:
>>>> Do other LaTeX classes for producing slides have special macros for
>>>> titles as well?  
> [...]
>> What I found with help of
>> <URL:http://www.miwie.org/presentations/presentations.html>:
>>
>> beamer:       \frametitle
>
> [ And \begin{frame}{<title>} or \begin{frame}{<title>}{<subtitle>} as
> pointed out by Jochen Küpper. ]

As the \begin flavors are kinda hard to do I only implemented the
\frametitle case for now.

>>>> In this case we could add a new keyword class for such titles
>>>> instead [...]

There now is a new `slide-title' class and an associated face named
`font-latex-slide-title-face'.  It inherits from
`font-lock-type-face', so the color is different from the faces used
for the sectioning commands.  This seemed appropriate because IIRC
there is at least one slide class where sectioning commands can be
used besides title commands.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Reiner Steib | 8 Sep 2005 18:09
X-Face

Re: Fontification of titles in LaTeX slides

On Thu, Sep 08 2005, Ralf Angeli wrote:

> There are no extra options for adjusting the font size or for
> switching to `color' fontification as in the sectioning case because
> only a single face is involved.  I thought about making the type of
> fontification of slide titles dependent on
> `font-latex-fontify-sectioning' as well, but decided against it in
> order to give people the possibility to customize fontification of
> sectioning commands and slide titles independently.
>
> Comments appreciated.

Would it make sense to use `font-latex-fontify-sectioning' in the
defface for the calculation of the size?

--8<---------------cut here---------------start------------->8---
--- font-latex.el	08 Sep 2005 15:33:35 +0200	5.137
+++ font-latex.el	08 Sep 2005 15:37:24 +0200	
 <at>  <at>  -931,7 +931,9  <at>  <at> 
   :group 'font-latex-highlighting-faces)

 (defface font-latex-slide-title-face
-  (let* ((scale 1.2)
+  (let* ((scale (if (numberp font-latex-fontify-sectioning)
+		    font-latex-fontify-sectioning
+		  1.1))
 	 (size (when (featurep 'xemacs)
 		 (round (* 0.9 (face-height 'default) scale)))))
     (if (featurep 'xemacs)
--8<---------------cut here---------------end--------------->8---
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ralf Angeli | 9 Sep 2005 10:06
Picon

Re: Re: Fontification of titles in LaTeX slides

* Reiner Steib (2005-09-08) writes:

> Would it make sense to use `font-latex-fontify-sectioning' in the
> defface for the calculation of the size?

I'd prefer to keep the sectioning and slide title stuff independent
because e.g. it makes code maintenance and documentation easier.  But
I don't have a strong opinion here.

--

-- 
Ralf
Permalink | Reply | 0 comments |
headers
Christian Schlauer | 12 Sep 2005 18:37
Picon
Favicon

[Patch] `TeX-BibTeX-sentinel' checks BibTeX's output

Hello!

Right now, AUCTeX doesn't warn the user if BibTeX complains about
something, see
<URL:http://article.gmane.org/gmane.emacs.auc-tex/3084>.

I attach a patch that reports the number of warnings/errors from the
BibTeX run instead of only suggesting "You should perhaps run LaTeX
again to get citations right."

It is good to report the actual number of warnings/errors: you might
have some bib entries that are not complete yet (missing year or
volume or ...), so you expect that there will be, say, 2 warnings.
Then you can see directly with the attached patch if the number of
warnings increases (bad) or is constant (expected).

I also changed "You should perhaps run LaTeX again to get citations
right." to "BibTeX finished successfully. Run LaTeX again to get
citations right." It seems to me that a BibTeX run is only triggered
when necessary (see `TeX-LaTeX-sentinel'), so one _should_ run LaTeX
again, not perhaps.

(I haven't found the time yet to sign up at Savannah and get familiar
with CVS, so could someone (Ralf?) check this in? Thanks!)
Attachment (tex-buf.el.diff): text/x-patch, 1002 bytes
Attachment (changes.texi.diff): text/x-patch, 361 bytes
(Continue reading)

Permalink | Reply | 1 comment |
headers
Ralf Angeli | 12 Sep 2005 23:35
Face
Picon

Re: [Patch] `TeX-BibTeX-sentinel' checks BibTeX's output

* Christian Schlauer (2005-09-12) writes:

> I attach a patch that reports the number of warnings/errors from the
> BibTeX run instead of only suggesting "You should perhaps run LaTeX
> again to get citations right."

Thanks for taking care of this.  The patch looks okay, nevertheless
I'd like to postpone applying it till after the release which is only
a few days away now.

--

-- 
Ralf
Permalink | Reply | 0 comments |
headers
Christian Schlauer | 14 Sep 2005 17:42
Picon
Favicon

Some Font-Lock in output buffer?

Hello,

this is just an idea: sometimes one has to look in the output buffer
(with `C-c C-l'). It would be nice, IMO, if words like
warning/error/overfull/underfull boxes were highlighted in that buffer
so that one can easily spot them. No aggressive colour, just bold
maybe. Like the highlighting of `\\(', `\\)' and `\\|' in regular
expressions in emacs-lisp mode (in Emacs 22, very nice!), maybe?

I think the words mentioned above would be already sufficient. What do
you think?
--

-- 
Christian Schlauer
Permalink | Reply | 2 comments |
headers
Ralf Angeli | 15 Sep 2005 10:25
Picon

Re: Some Font-Lock in output buffer?

* Christian Schlauer (2005-09-14) writes:

> this is just an idea: sometimes one has to look in the output buffer
> (with `C-c C-l'). It would be nice, IMO, if words like
> warning/error/overfull/underfull boxes were highlighted in that buffer
> so that one can easily spot them. No aggressive colour, just bold
> maybe. Like the highlighting of `\\(', `\\)' and `\\|' in regular
> expressions in emacs-lisp mode (in Emacs 22, very nice!), maybe?
>
> I think the words mentioned above would be already sufficient. What do
> you think?

Some time ago I experimented with Compilation mode (in connection with
the output buffer) where you can set `compilation-error-regexp-alist'.
With that one would not only get highlighting like with `grep-find'
but also the possibility to jump to the respective position in the
source code.

Unfortunately I seem to have deleted the experiments I did.  I don't
recall exactly what the problems were, but possibly something related
to multifile documents or a clash with the system we currently have.

Another related idea would be to gather the errors (and warnings) and
display them in a new buffer each on a line of its own like it is done
in some IDEs.  Like this one would have all the errors displayed at
once in contrast to having to step through them one by one like it has
to be done now.  We just have to think of a smart way to display the
supplementary descriptive help messages we are currently offering in
the `TeX-next-error' buffers.
(Continue reading)

Permalink | Reply | 1 comment |

Gmane