headers
Ralf Angeli | 5 Oct 20:40

Switching TeX engines

Okay, I got rid of the minor modes for XeTeX and Omega.  (To be precise,
the one for Omega is being kept for compatibility reasons for the time
being.)  Instead, there is a variable called `TeX-engine' which can be
used to select the engine.  Since we don't have a way to set stuff for a
document, it is global at the moment but can obviously also be set
file-locally.  The three engine options are currently `default', `xetex'
and `omega'.  One could probably add PDFTeX as well but I didn't see a
need for that because it is already handled by `TeX-DVI-via-PDFTeX'.
The engine can be set through the TeXing options menu or with `M-x
TeX-engine-set <RET>'.

Lemme know what you think.

--

-- 
Ralf
Permalink | Reply | 0 comments |
headers
Angelo Graziosi | 29 Sep 16:58

Deleting generated intermediate files in Emacs+AUCTeX

Let us consider the following example, using current CVS Emacs 23.1 and
current AUCTeX CVS.

The directory Foo_dir contains Foo.tex (the main file of a document),
and the directory FrontBackmatter which contains TitlePage.tex:

$ ls -lrtR Foo_dir
...
-rw-r--r-- 1 ... 948 Sep 29 00:07 Foo.tex
drwxr-xr-x+ 2 ... 0 Sep 29 10:25  FrontBackmatter

Foo_dir/FrontBackmatter:
totale 9
...
-rw-r--r-- 1 ... 707 Sep 28 23:54 TitlePage.tex

Foo.tex includes TitlePage.tex with:

\include{FrontBackmatter/TitlePage}

In Foo.tex there is:

%%% Local Variables:
%%% mode: latex
%%% TeX-master: t
%%% End:

while in TitlePage.tex:

%%% Local Variables:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Andreas Neiser | 21 Sep 18:10

Development of refstyle.sty support

Hey,
I've read some messages about implementing support for refstyle.sty (and
maybe other referencing packages). I widely use some things like
\figlabel{bla} and then \figref{bla} to reference it. Is there some
ongoing (and maybe already working) patches which I can try?
I'm not really experienced with Lisp and/or Emacs and/or AucTeX,
therefor I hope somebody can explain some steps in detail here.
Thanks in advance
Andreas
Permalink | Reply | 3 comments |
headers
Uwe Brauer | 10 Sep 12:40

the xemacs pkg sync:tex-wizard.el is *not* needed?

Hello                                           

We are almost done with the sync. (I said this a couple of weeks ago, I
know).
I just realized that the auctex source dir contains a file called
tex-wizard.el
This file is *not* included in the xemacs pkg provided by the auctex
team, therefore we also will not include it. But just out of curiosity 
this file is only used in GNU emacs?

Uwe Brauer
Permalink | Reply | 1 comment |
headers
Uwe Brauer | 5 Sep 12:37

REftex: bug in reftex-create-bibtex-file


Hello

4 years ago, I asked Carsten about a BUG in this reftex function.
Since now the auctex team maintains reftex, Carsten suggested to contact
you. 

Here are the relevant emails:

>
>>
>> Hi Uwe,
>>
>> yes, I know about this problem.  The format of the comments is like
>> this in order to allow comments of cite macros with several citations
>> in one macro.  It could be fixed, I guess.  When I find time, I will.
>>
>> - Carsten
>
>
> Did you had the time to fix it?
>
>
>>>>>> "UB" == Uwe Brauer <oub <at> mat.ucm.es> writes:
>
> UB> Hello Carsten,
> UB> I  seems   that reftex-create-bibtex-file does    not  work
> well, when
> UB> reftex-comment-citations set to
> UB> t. If it is nil, reftex indeed generated a bibtex file.
(Continue reading)

Permalink | Reply | 6 comments |
headers
Phillip Lord | 4 Sep 15:07

Re: adventures with --prefix, TeX-data-directory and style files

>>>>> "DK" == David Kastrup <dak <at> gnu.org> writes:

  DK> Phillip Lord <phillip.lord <at> newcastle.ac.uk> writes:

  >> The main expedient is using the `--prefix' option to the `configure'
  >> script, and let it point to the personal home directory.
  >> 
  >> 
  >> Which I tried and which doesn't work. In the end, I did...
  >> 
  >> ./configure --prefix=/cygdrive/d/home/phillord/emacs/packages/auctex
  >> --with-lispdir=/cygdrive/d/home/phillord/emacs/package/auctex
  >> --disable-preview

  DK> ARG!!!

  DK> The installation instructions for Windows quite explicitly state:

  DK>        Avoid `helpful' magic file names like `/cygdrive/c' and
  DK>     `C:\PROGRA~1\' like the plague. It is quite unlikely that the
  DK>     scripts will be able to identify the actual file names involved. Use
  DK>     the full paths, making use of normal Windows drive letters like `
  DK>     'C:/Program Files/Emacs' ' where required, and using the same
  DK>     combination of upper- and lowercase letters as in the actual files.
  DK>     File names containing shell-special characters like spaces or
  DK>     backslashes (if you prefer that syntax) need to get properly quoted
  DK>     to the shell: the above example used single quotes for that.

Ah, yes, so they do. Well, I've got the build to work either way which is
good. Style file loading is not working, at least on windows, which is a
(Continue reading)

Permalink | Reply | 0 comments |
headers
Phillip Lord | 4 Sep 13:25

Re: adventures with --prefix, TeX-data-directory and style files

>>>>> "RA" == Ralf Angeli <angeli <at> caeruleus.net> writes:

  RA> * Phillip Lord (2008-09-03) writes:

  >> In practice, I stopped bothering. I've never managed to get to grips with
  >> how emacs finds its info files

  RA> C-h v Info-directory-list <RET> C-h v Info-additional-directory-list
  RA> <RET>

  >> and found it unreliable;

  RA> Probably because you use a non-standard setup and haven't configured it
  RA> correctly.

No. I went through the entire code to try and work out what was happening
sometime ago. Essentially, there is some caching going on, so changes don't
necessarily get reflected immediately. 

Rather, I should say in past tense. I did this a long time ago and it may have
changed since. 

  >> I normally just open them with C-uC-hi in my ~/emacs/packages directory.
  >> Or more often these days, I type the name into google and use a web
  >> browser.

  RA> Sounds inconvenient.

Not hugely. I've been using most of the packages for years, so don't look at
the info. For new packages, you open once, and then *info* is in the right
(Continue reading)

Permalink | Reply | 3 comments |
headers
Phillip Lord | 3 Sep 20:37

Re: adventures with --prefix, TeX-data-directory and style files

>>>>> "RA" == Ralf Angeli <angeli <at> caeruleus.net> writes:

  RA> * Phillip Lord (2008-09-03) writes:
  >> Just to explain, the reason I do this is that my emacs configuration and
  >> add-on packages are shared between the five machines and 2 operating
  >> systems that I use regularly. I use unison to sync it all together; this
  >> means I only have to install things once and behaviour is identical
  >> between my machines.

  RA> How do you make sure that the different Emacs installations have access
  RA> to the info files of the "add-on packages"?

Good question. 

What I used to do is dump all the info files into ~/emacs/info. The gets
unisoned also, so ends up on all my machines. 

In practice, I stopped bothering. I've never managed to get to grips with how
emacs finds its info files and found it unreliable; I normally just open them
with C-uC-hi in my ~/emacs/packages directory. Or more often these days, I
type the name into google and use a web browser.

  >> I don't think that this was the problem. I've just tried again, including
  >> with --prefix=/tmp and got the same thing.

  RA> If you are talking about the lisp files not being put below the prefix
  RA> then you should use --with-lispdir in addition to --prefix. IIRC the
  RA> configure script will put the lisp files into a directory in the
  RA> load-path of Emacs. If it cannot find such a directory below the given
  RA> prefix, another available one is chosen.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Phillip Lord | 3 Sep 13:16

Re: adventures with --prefix, TeX-data-directory and style files

>>>>> "RA" == Ralf Angeli <angeli <at> caeruleus.net> writes:

  RA> * Phillip Lord (2008-09-01) writes:

  >> I normally install auctex by unpacking the tar ball in ~/emacs/packages
  >> (creating auctex-x.x where x is the version number), and doing
  >> ./configure, make, but no make install.

  RA> This is not a good idea as you obviously found out.

Yes; it works for almost all of the packages that I use, but not auctex which
is unfortunate. Still, as there isn't a standard for doing this on emacs, I
guess auctex's method is as good as everyone else. 

Just to explain, the reason I do this is that my emacs configuration and
add-on packages are shared between the five machines and 2 operating systems
that I use regularly. I use unison to sync it all together; this means I only
have to install things once and behaviour is identical between my machines.

  >> So I decided to try the make install option instead. So I move auctex
  >> away from ~/emacs/packages, and try
  >> 
  >> ./configure --prefix=/home/username/emacs/packages/auctex
  >> 
  >> which is nearly what was suggested in "Installation for non-privelleged
  >> users". But this appears to be ignored -- make install tries to isntall
  >> in /usr/share...

  RA> You have to provide the --prefix option with a directory that actually
  RA> exists.
(Continue reading)

Permalink | Reply | 1 comment |
headers
Phillip Lord | 1 Sep 20:27

adventures with --prefix, TeX-data-directory and style files


I recently noticed that the auctex style files were not being loaded.
Following some investigation, I've discovered the cause, and thought I would
relate the story. 

With a bit of fiddling, I tracked the problem down to TeX-data-directory,
which is my case is set wrong, specifically to 

~/emacs/packages/auctex-11.58/auctex

Notice the extra "auctex". Hence the style files were not being found. 

I traced this back to 

(defvar TeX-lisp-directoryr
  (expand-file-name "auctex" (file-name-directory load-file-name))
  "The directory where most of the AUCTeX lisp files are located.
For the location of lisp files associated with
styles, see the variables TeX-style-* (hand-generated lisp) and
TeX-auto-* (automatically generated lisp).")

where the problem is evident. 

I normally install auctex by unpacking the tar ball in ~/emacs/packages
(creating auctex-x.x where x is the version number), and doing ./configure,
make, but no make install. This is how I install most packages and it works
well for me; I just add all directories in ~/emacs/packages to the path
recursively. 

So, I figure, auctex must use one directory structure for packaging (where no
(Continue reading)

Permalink | Reply | 1 comment |
headers
auxsvr | 22 Aug 17:01

Re: [AUCTeX] How to implement the function? Identify state of input method.

On Thursday 21 August 2008, you wrote:
> I try . When I input $, mule switch to the math mode. This is OK.
> It does not take effect to \[ \] .
> Another question , I am using "cdlatex".
> In minor mode cdlatex, when I input $ ,it put another $ and put point in
> middle.
> "latex-i18n.el" make the ability disable.
>
> Thanks

I wrote this minor mode 7 years ago, so it isn't up to date with current 
auctex functionality. I will ask the mailing list to see what is the best way 
to do these things and send you an updated version.

auctex-devs:
What is the best way to allow both my minor mode and auctex to catch "$" key 
presses?
Permalink | Reply | 0 comments |

Gmane