Phillip Lord | 1 Sep 20:27 2008
Picon
Picon

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)

Ralf Angeli | 2 Sep 19:30 2008
Picon

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

* 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.

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

> 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...

You have to provide the --prefix option with a directory that actually
exists.

--

-- 
Ralf
Phillip Lord | 3 Sep 13:16 2008
Picon
Picon

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)

Ralf Angeli | 3 Sep 18:53 2008
Picon

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

* 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.

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

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

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

--

-- 
Ralf
Phillip Lord | 3 Sep 20:37 2008
Picon
Picon

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)

Ralf Angeli | 3 Sep 22:53 2008
Picon

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

* 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

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

> and found it unreliable;

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

> 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.

Sounds inconvenient.

>   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.
>
> Okay. 
>
> So I've tried
>
> ./configure --with-lispdir=/home/phillord/emacs/package/auctex
(Continue reading)

Phillip Lord | 4 Sep 13:25 2008
Picon
Picon

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)

David Kastrup | 4 Sep 14:14 2008
Picon
Picon

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

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

ARG!!!

The installation instructions for Windows quite explicitly state:

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

--

-- 
David Kastrup
Phillip Lord | 4 Sep 15:07 2008
Picon
Picon

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)

Uwe Brauer | 5 Sep 12:41 2008
Picon

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)


Gmane