Ralf Angeli | 3 Apr 15:29 2011
Picon

Re: preview \cite

* emacs user (2011-03-27) writes:

>> Hm, that's odd.  A cause for the problem could be that preview-latex
>> gets confused by some unbalanced parenthesis in the log output.  Looking
>> at the output you sent I could not see anything obvious.  Does it get
>> better if you enable file:line:error messages in your TeX system?
>
> I used
>
> %%% Local Variables:
> %%% mode: LaTeX
> %%% LaTeX-command: "latex --file-line-error-style"
> %%% TeX-master: t
> %%% TeX-PDF-mode: t
> %%% End:
>
> to add this option, and am attaching the log with and without this.
> it didn't seem to help.  best, Eli

In the log you sent I saw that you seem to be running a preview-latex
command other than `preview-document'.  (Something I failed to notice in
the original log you sent.)  Commands like `preview-at-point' or
`preview-buffer' generate previews by running LaTeX on a LaTeX file
which is just a part of the whole file.  However, preview-latex does not
run BibTeX on this file, so the necessary data to resolve the reference
is missing.  That's why you see a question mark in the preview.

You can work around this by running `preview-document' instead one of
the preview commands which only operate on a part of the document (and
make sure that BibTeX was run before) or by running BibTeX manually on
(Continue reading)

Ralf Angeli | 3 Apr 16:18 2011
Picon

Re: Viewing problems!

Please keep the mailing list copied!  I'm including a full quote of your
text below, including the odd linebreaks.

* gerald jean (2011-03-28) writes:

> Thanks Ralf for your hep,
>
> Ralf Angeli <angeli <at> caeruleus.net> a écrit sur 2011/03/27 10:24:55 :
>
>> * gerald jean (2011-03-23) writes:
>>
>> > 1) When viewing a document (C-cC-c) auctex guesses wrong what I want to
> do
>> > 95% of the time.  I know it is trying to be smart and start Ghostscript
> if
>> > there is embedded graphics in my document but it does anyhow, even for
> a
>> > very simple document with just a little bit of text I do get:
>> >
>> > dvips myfile.dvi -o && gv myfile.ps
>>
>> Could you be using PSTricks?
>
> No.  But I had a few settings repeated in my preamble, removing the
> duplicates seems to have solved this problem, on the file I am testing on
> anyway!
>
>>
>> > What I would like to have 100% of the time (I'll manually take care of
> the
(Continue reading)

emacs user | 3 Apr 19:07 2011
Picon

Re: preview \cite

Thank you!  this indeed works and is very helpful, apologies for
taking your time on something that wasn't a bug. am most grateful!
best, E

On Sun, Apr 3, 2011 at 9:29 AM, Ralf Angeli <angeli <at> caeruleus.net> wrote:
>
> In the log you sent I saw that you seem to be running a preview-latex
> command other than `preview-document'.  (Something I failed to notice in
> the original log you sent.)  Commands like `preview-at-point' or
> `preview-buffer' generate previews by running LaTeX on a LaTeX file
> which is just a part of the whole file.  However, preview-latex does not
> run BibTeX on this file, so the necessary data to resolve the reference
> is missing.  That's why you see a question mark in the preview.
>
> You can work around this by running `preview-document' instead one of
> the preview commands which only operate on a part of the document (and
> make sure that BibTeX was run before) or by running BibTeX manually on
> the _region_.tex file mentioned above.  The latter workaround does not
> seem very practical, though.
>
> I don't think we'll see preview-latex automatically running stuff like
> BibTeX soon because we don't even have this feature yet in AUCTeX.
>
> --
> Ralf
>
Frederik | 4 Apr 17:03 2011
Picon

RefTeX: citing process

Hi there!

Some time ago I asked on this list if it is possible to insert 
`footcites' provided by biblatex via RefTeX.

I just discovered a nifty feature in RefTeX which I missed back then: 
when citing a reference, you can mark several entries in the bib-file 
and by pressing `A' RefTeX inserts several citing commands, each citing 
one of the selected entries.

Now it shouldn't be too difficult to make RefTeX not to insert several 
citing commands but to insert `\footcites' and to append the marked 
entries in braces, e.g.

\footcites[foo]{first-marked-entry}[bar]{second-marked-entry}

(Right now it's \footcite[foo]{first-marked-entry} 
\footcite[bar]{second-marked-entry} )

Ah, and I wonder if it is possible to avoid the standard-regexp when 
citing with RefTeX:

After having cited some reference, say with bibtex-key `foo', I want to 
cite some other references, but I don't remember the exact bibtex-keys. 
Now, when citing with `C-c [' the default regexp corresponds to the last 
cited reference `foo'. When I press RET I can just select `foo'. Now I 
have to visit my bib file, look for the appropriate key `bar1' and 
insert the beginning of that key in the regexp (after having started the 
citing process again).

(Continue reading)

Rasmus Villemoes | 7 Apr 05:53 2011
Picon
Picon

font-latex-built-in-keyword-classes - minor errors and omissions

Hi,

I believe there are a few minor errors in
font-latex-built-in-keyword-classes (font-latex.el). I use version
11.85, but I've just checked 11.86, and it seems to contain the same
definitions.

Errors:

("documentclass" "[{")
("usepackage" "[{")

These both take an optional trailing argument.

("renewenvironment" "*{[{{")

Should be the same as newenvironment, i.e., two optional arguments.

("sbox" "{")

\sbox "officially" takes two arguments, but it may be on purpose that
only the first is fontified as such.

("newcounter" "{[") is in the "function" section, but probably belongs
logically to the "variable" section (where setcounter and addtocounter
already live).

"include" is listed under "warning" and under "reference" (in the
latter as taking "{"); while "input" and "includeonly" are
"function"s, both taking a mandatory argument. Is there a reason
(Continue reading)

Ralf Angeli | 10 Apr 19:34 2011
Picon

Re: RefTeX: citing process

* Frederik (2011-04-04) writes:

> Now it shouldn't be too difficult to make RefTeX not to insert several 
> citing commands but to insert `\footcites' and to append the marked 
> entries in braces, e.g.
>
> \footcites[foo]{first-marked-entry}[bar]{second-marked-entry}
>
> (Right now it's \footcite[foo]{first-marked-entry} 
> \footcite[bar]{second-marked-entry} )

AFAICS you can only choose between \cite{a}\cite{b} (inserted with `A')
and \cite{a,b} (inserted with `a').  The syntax you want does not seem
to be very common.

> Ah, and I wonder if it is possible to avoid the standard-regexp when 
> citing with RefTeX:
>
> After having cited some reference, say with bibtex-key `foo', I want to 
> cite some other references, but I don't remember the exact bibtex-keys. 
> Now, when citing with `C-c [' the default regexp corresponds to the last 
> cited reference `foo'. When I press RET I can just select `foo'. Now I 
> have to visit my bib file, look for the appropriate key `bar1' and 
> insert the beginning of that key in the regexp (after having started the 
> citing process again).
>
> This is annoying; is there a way to get all my bib-entries in the 
> selection window when I just hit enter?

That would defeat the purpose of the regexp proposal.  Or do you want to
(Continue reading)

Dominic Jänichen | 11 Apr 16:26 2011
Picon

Bug with fold mode (tries to fold recursively)

Hello,

 

I just discovered emacs  24.0.50.1 with AUCTeX 11.86 locking up as I tried to fold code.

It happens if I try to fold code to an expression containing a reference to a parameter (“{1}”), if this parameter includes the same string as one that is not going to be folded.

 

Minimal example:

 

Add “br” to fold as “({1})” in math mode

 

Try to fold

$\br{x_{1}}$

 

AUCTeX then holds emacs (in an infinite loop?)

 

Backtrace is

Debugger entered--Lisp error: (quit)

  byte-code( -- omitted here, but attached -- )

  TeX-fold-expand-spec("({1})" 20 30)

  TeX-fold-hide-item(#<overlay from 20 to 30 in test.txt.tex>)

  TeX-fold-region-macro-or-env(1 91 math)

  TeX-fold-region(1 91)

  TeX-fold-buffer()

  call-interactively(TeX-fold-buffer nil nil)

 

 

If I change $\br{x_{1}}$ to $\br{x_{1 }}$, there is no error.

 

 

 

Sincerely,

Dominic

Attachment (backtrace): application/octet-stream, 1062 bytes
Attachment (smime.p7s): application/pkcs7-signature, 6436 bytes
_______________________________________________
auctex mailing list
auctex <at> gnu.org
http://lists.gnu.org/mailman/listinfo/auctex
Dominic Jänichen | 11 Apr 17:47 2011
Picon

Bug with fold mode (tries to fold recursively)

(sent again / removed attachement)

Hello,

I just discovered emacs  24.0.50.1 with AUCTeX 11.86 locking up as I tried
to fold code.

It happens if I try to fold code to an expression containing a reference to
a parameter (“{1}”), if this parameter includes the same string as one that
is not going to be folded.

Minimal example:

Add “br” to fold as “({1})” in math mode

Try to fold

$\br{x_{1}}$

AUCTeX then holds emacs (in an infinite loop?)

Backtrace is

Debugger entered--Lisp error: (quit)

  byte-code( -- omitted here, but attached -- )

  TeX-fold-expand-spec("({1})" 20 30)

  TeX-fold-hide-item(#<overlay from 20 to 30 in test.txt.tex>)

  TeX-fold-region-macro-or-env(1 91 math)

  TeX-fold-region(1 91)

  TeX-fold-buffer()

  call-interactively(TeX-fold-buffer nil nil)

If I change $\br{x_{1}}$ to $\br{x_{1 }}$, there is no error.

Sincerely,

Dominic
Frederik | 15 Apr 10:35 2011
Picon

Re: RefTeX: citing process

Am 10.04.2011 19:34, schrieb Ralf Angeli:
> AFAICS you can only choose between \cite{a}\cite{b} (inserted with `A')
> and \cite{a,b} (inserted with `a').  The syntax you want does not seem
> to be very common.

Hm, it's the biblatex-way of citing several references in a single 
footnote. This way of citing is quite common in the humanities and 
biblatex provides very good support for these purposes. I just meant, 
that it shouldn't be too difficult to support this syntax...

>> This is annoying; is there a way to get all my bib-entries in the
>> selection window when I just hit enter?
>
> That would defeat the purpose of the regexp proposal.  Or do you want to
> get rid of the feature?  I couldn't find a switch for that.  But in
> cases like yours I simply type `.' before<RET>  and then get all
> entries.  This is probably not too unconvenient.  The doc string of
> `reftex-citation' mentions that `=' can be used as well.

Ah, cool I didn't realize that - Thanks.

Regards,
Fred

--

-- 
Frederik

freak.fred <at> gmail.com
AW | 15 Apr 14:39 2011
Picon

Feature request: Auto-compiling every ten seconds

Quite often I'm just writing text, left hand emacs, right hand the pdf-viewer 
showing my page. 

To compile I'm typing C-C C-S C-C C-C (1. save 2. compile). What about an 
auto-compilation-modus, which saves and compiles every ten or 15 seconds? "M-x 
autocompile 15" => every 15 seconds.  

Nowadays most Computers are so fast, it would not disturb whatever running in 
the background. Maybe the module to do that could even stop if the last run 
terminated with an error. 

Just an idea. 

Gmane