Automatic Compiling

Automatic Compiling

[Ulrich Dirr]

Hi.

Is there an easy way how I can customize my PDFeLaTeX compile cycles? I
find it somewhat tedious to do all steps by hand.
(1) going to the compile menu and selecting PDFeLaTeX
(2) explictely confirm saving
(3) typing C-c C-c after successfully compiling
(4) typing 'View PDF'
(5) correcting the status line 'View PDF command: start <file>.tex.pdf'
to <file>.pdf

(5) or how can I change the output behavior so that <file>.tex.pdf is
written (which I would prefer).

I presume that this is nothing special as a lot of TeX afficionados are
using emacs and solved this already.

Best regards,
Ulrich Dirr

P.S. Where have I to look to find informations how to define shortcut
keys for actions.

Re: Automatic Compiling

[Kai Großjohann]

"Ulrich Dirr" <ud@art-satz.de> writes:

> Is there an easy way how I can customize my PDFeLaTeX compile cycles? I
> find it somewhat tedious to do all steps by hand.
> (1) going to the compile menu and selecting PDFeLaTeX
> (2) explictely confirm saving
> (3) typing C-c C-c after successfully compiling
> (4) typing 'View PDF'
> (5) correcting the status line 'View PDF command: start <file>.tex.pdf'
> to <file>.pdf

It seems you did some special setup to make the above work.  I think
it doesn't work by default.

So my suggestion is that you show us this setup, then maybe someone
can find the error.

FWIW, I use "%s.pdf" in TeX-command-list to refer to the PDF file.
Maybe you used %f instead of %s?  That might explain the problem.
-- 
file-error; Data: (Opening input file no such file or directory ~/.signature)

Re: Automatic Compiling

[David Kastrup]

"Ulrich Dirr" <ud@art-satz.de> writes:

> Hi.
> 
> Is there an easy way how I can customize my PDFeLaTeX compile cycles? I
> find it somewhat tedious to do all steps by hand.
> (1) going to the compile menu and selecting PDFeLaTeX
> (2) explictely confirm saving
> (3) typing C-c C-c after successfully compiling
> (4) typing 'View PDF'
> (5) correcting the status line 'View PDF command: start <file>.tex.pdf'
> to <file>.pdf
> 
> (5) or how can I change the output behavior so that <file>.tex.pdf is
> written (which I would prefer).
> 
> I presume that this is nothing special as a lot of TeX afficionados are
> using emacs and solved this already.

The current developer version does this, you might want to try it
using anonymous CVS.  Take a look at
<URL:http://savannah.gnu.org/projects/auctex> for more info about
getting at CVS.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Re: Automatic Compiling

[Ulrich Dirr]

David Kastrup wrote:
> "Ulrich Dirr" <ud@art-satz.de> writes:
>
>> Hi.
>>
>> Is there an easy way how I can customize my PDFeLaTeX compile
>> cycles? I find it somewhat tedious to do all steps by hand.
>> (1) going to the compile menu and selecting PDFeLaTeX
>> (2) explictely confirm saving
>> (3) typing C-c C-c after successfully compiling
>> (4) typing 'View PDF'
>> (5) correcting the status line 'View PDF command: start
>> <file>.tex.pdf' to <file>.pdf
>>
>> (5) or how can I change the output behavior so that <file>.tex.pdf is
>> written (which I would prefer).
>>
>> I presume that this is nothing special as a lot of TeX afficionados
>> are using emacs and solved this already.
>
> The current developer version does this, you might want to try it
> using anonymous CVS.  Take a look at
> <URL:http://savannah.gnu.org/projects/auctex> for more info about
> getting at CVS.

Sorry, but I'm too stupid to understand the steps needed to get this
working. Is there a guide for dummies like me?

Re: Automatic Compiling

[David Kastrup]

"Ulrich Dirr" <ud@art-satz.de> writes:

>
> > The current developer version does this, you might want to try it
> > using anonymous CVS.  Take a look at
> > <URL:http://savannah.gnu.org/projects/auctex> for more info about
> > getting at CVS.
> 
> Sorry, but I'm too stupid to understand the steps needed to get this
> working. Is there a guide for dummies like me?

I am too stupid to understand the objection: the mentioned web page
explicitly says 

    Anonymous CVS Access

    This project's CVS repository can be checked out through anonymous
    (pserver) CVS with the following instruction set. The module you
    wish to check out must be specified as the modulename. When
    prompted for a password for anoncvs, simply press the Enter key.

    Software repository :

    cvs -d:pserver:anoncvs@subversions.gnu.org:/cvsroot/auctex login

    cvs -z3 -d:pserver:anoncvs@subversions.gnu.org:/cvsroot/auctex co <modulename>

Apart from mentioning that the <modulename> is "auctex", I fail to
see how one could make a "guide for dummies" that would be any
different.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Re: Automatic Compiling

[Ulrich Dirr]

David Kastrup wrote:
> I am too stupid to understand the objection: the mentioned web page
> explicitly says
>
>     Anonymous CVS Access
>
>     This project's CVS repository can be checked out through anonymous
>     (pserver) CVS with the following instruction set. The module you
>     wish to check out must be specified as the modulename. When
>     prompted for a password for anoncvs, simply press the Enter key.
>
>     Software repository :
>
>     cvs -d:pserver:anoncvs@subversions.gnu.org:/cvsroot/auctex login
>
>     cvs -z3 -d:pserver:anoncvs@subversions.gnu.org:/cvsroot/auctex co
> <modulename>
>
> Apart from mentioning that the <modulename> is "auctex", I fail to
> see how one could make a "guide for dummies" that would be any
> different.

Ok, I've misunderstood something ... But I've successfully downloaded
this version and run the everything with the help of mingw make. First
I'm not sure if everything went ok.

The last lines of 'make install' are
[...]
 /bin/install -c -m 644 style/subfigure.el
/c/bin/emacs-21.2/site-lisp/auctex/style
 /bin/install -c -m 644 style/subfigure.elc
/c/bin/emacs-21.2/site-lisp/auctex/style
./mkinstalldirs /c/bin/emacs-21.2/site-lisp/auctex/auto
cd doc; make install
make[1]: Entering directory `/c/usr/uli/auctex/doc'
../mkinstalldirs /usr/local/info
for x in auctex auctex-*; do \
        /bin/install -c -m 644 $x /usr/local/info ; \
done
/bin/install-info  --info-dir=/usr/local/info auctex
make[1]: Leaving directory `/c/usr/uli/auctex/doc'

Is this 'standard' console output? Where can I check that the newest
auctex is correctly installed and working (maybe like the version info
of emacs in the menu bar)? Do I have to update other files besides
auctex?

Second I don't see any other behavior when compiling. I still have to
input everything by hand (as listed in my first mail).

Probably something is wrong. Any idea?

Best regards,
Ulrich Dirr

P.S. please be patient with me, I'm very unexperienced with this new
environment.

Re: Automatic Compiling

[David Kastrup]

"Ulrich Dirr" <ud@art-satz.de> writes:

> Ok, I've misunderstood something ... But I've successfully downloaded
> this version and run the everything with the help of mingw make. First
> I'm not sure if everything went ok.
> 
> The last lines of 'make install' are
> [...]
>  /bin/install -c -m 644 style/subfigure.el
> /c/bin/emacs-21.2/site-lisp/auctex/style
>  /bin/install -c -m 644 style/subfigure.elc
> /c/bin/emacs-21.2/site-lisp/auctex/style
> ./mkinstalldirs /c/bin/emacs-21.2/site-lisp/auctex/auto
> cd doc; make install
> make[1]: Entering directory `/c/usr/uli/auctex/doc'
> ../mkinstalldirs /usr/local/info
> for x in auctex auctex-*; do \
>         /bin/install -c -m 644 $x /usr/local/info ; \
> done
> /bin/install-info  --info-dir=/usr/local/info auctex
> make[1]: Leaving directory `/c/usr/uli/auctex/doc'
> 
> Is this 'standard' console output?

Apart from "/c/bin/emacs-21.2/site-lisp" being about the weirdest
directory I ever saw for installing Emacs files.  Are you sure that
this is in your load-path?

> Where can I check that the newest auctex is correctly installed and
> working (maybe like the version info of emacs in the menu bar)? Do I
> have to update other files besides auctex?

AUCTeX comes with an info file, and you have installed it.  C-h i d m
auctex RET should lead you to the AUCTeX info, and it has a chapter
"Installation".

> Second I don't see any other behavior when compiling. I still have to
> input everything by hand (as listed in my first mail).

C-h v AUC-TeX-version RET

should tell you the installed version.

> Probably something is wrong. Any idea?

Probably you installed into a wrong place.  What was the line that
you specified to ./configure?  What is the output of config.log?

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Re: Automatic Compiling

[Ulrich Dirr]

David Kastrup wrote:
> "Ulrich Dirr" <ud@art-satz.de> writes:
> Apart from "/c/bin/emacs-21.2/site-lisp" being about the weirdest
> directory I ever saw for installing Emacs files.  Are you sure that
> this is in your load-path?

I thought emacs-21.2/site-lisp/auctex is a good place. Where should it
be installed?

>> Where can I check that the newest auctex is correctly installed and
>> working (maybe like the version info of emacs in the menu bar)? Do I
>> have to update other files besides auctex?
>
> AUCTeX comes with an info file, and you have installed it.  C-h i d m
> auctex RET should lead you to the AUCTeX info, and it has a chapter
> "Installation".
>
>> Second I don't see any other behavior when compiling. I still have to
>> input everything by hand (as listed in my first mail).
>
> C-h v AUC-TeX-version RET
>
> should tell you the installed version.

tells CVS-5.297, is this the new version?

>> Probably something is wrong. Any idea?
>
> Probably you installed into a wrong place.  What was the line that
> you specified to ./configure?  What is the output of config.log?

???

Ulrich Dirr

P.S. what should have changed concerning the compile cycle keyboarding?


--- start config.log ---
This file contains any messages produced by compilers while
running configure, to aid debugging if configure makes a mistake.

It was created by auctex configure 11.14, which was
generated by GNU Autoconf 2.57.  Invocation command line was

  $
./configure --with-emacs=/c/bin/emacs-21.2/bin/emacs --with-texmf-dir=/c
/tex/bin/win32/tex --with-lispdir=/c/bin/emacs-21.2/site-lisp/auctex

## --------- ##
## Platform. ##
## --------- ##

hostname = DOMINUS
uname -m = i686
uname -r = 1.0.8(0.46/3/2)
uname -s = MINGW32_NT-5.0
uname -v = 2002-12-09 07:58

/usr/bin/uname -p = unknown
/bin/uname -X     = unknown

/bin/arch              = unknown
/usr/bin/arch -k       = unknown
/usr/convex/getsysinfo = unknown
hostinfo               = unknown
/bin/machine           = unknown
/usr/bin/oslevel       = unknown
/bin/universe          = unknown

PATH: .
PATH: /usr/local/bin
PATH: /mingw/bin
PATH: /bin
PATH: /c/ps/Ghostgum/gsview
PATH: /c/TeX/bin/win32
PATH: /perl/bin/
PATH: /c/bin/chess/utils
PATH: /c/bin/utils
PATH: /c/WINNT/system32
PATH: /c/WINNT
PATH: /c/WINNT/System32/Wbem
PATH: /bin
PATH: /mingw/bin
PATH: /c/cygwin
PATH: /c/cygwin/bin
PATH: /c/bin/emacs-21.2/bin
PATH: /c/bin/python22
PATH: /c/bin/tcl/bin
PATH: /c/ps/Ghostgum/gsview
PATH: /c/TeX/bin/win32
PATH: /perl/bin/
PATH: /c/bin/chess/utils
PATH: /c/bin/utils
PATH: /c/WINNT/system32
PATH: /c/WINNT
PATH: /c/WINNT/System32/Wbem


## ----------- ##
## Core tests. ##
## ----------- ##

configure:1100: loading site script /etc/config.site
| lt_cv_cc_dll_switch=${lt_cv_cc_dll_switch=-mdll}
| lt_cv_compiler_c_o=${lt_cv_compiler_c_o=yes}
| lt_cv_compiler_o_lo=${lt_cv_compiler_o_lo=yes}
| lt_cv_deplibs_check_method=${lt_cv_deplibs_check_method='file_magic
file format pei*-i386(.*architecture: i386)?'}
| lt_cv_file_magic_cmd=${lt_cv_file_magic_cmd='$OBJDUMP -f'}
| lt_cv_file_magic_test_file=${lt_cv_file_magic_test_file=}
| test "${lt_cv_global_symbol_to_c_name_address+set}" = set ||
lt_cv_global_symbol_to_c_name_address='sed -n -e '\''s/^: \([^ ]*\) $/
{\"\1\", (lt_ptr) 0},/p'\'' -e '\''s/^[BCDEGRST] \([^ ]*\) \([^ ]*\)$/
{"\2", (lt_ptr) \&\2},/p'\'''
| lt_cv_global_symbol_to_cdecl=${lt_cv_global_symbol_to_cdecl='sed -n -e
'\''s/^. .* \(.*\)$/extern char \1;/p'\'''}
| lt_cv_ld_reload_flag=${lt_cv_ld_reload_flag=-r}
| lt_cv_need_dllmain=${lt_cv_need_dllmain=no}
| lt_cv_prog_cc_can_build_shared=${lt_cv_prog_cc_can_build_shared=yes}
| lt_cv_prog_cc_no_builtin=${lt_cv_prog_cc_no_builtin=}
| lt_cv_prog_cc_pic=${lt_cv_prog_cc_pic='   -DDLL_EXPORT'}
| lt_cv_prog_cc_pic_works=${lt_cv_prog_cc_pic_works=yes}
| lt_cv_prog_cc_shlib=${lt_cv_prog_cc_shlib=}
| lt_cv_prog_cc_static=${lt_cv_prog_cc_static=-static}
| lt_cv_prog_cc_static_works=${lt_cv_prog_cc_static_works=yes}
| lt_cv_prog_cc_wl=${lt_cv_prog_cc_wl=-Wl,}
| lt_cv_prog_gnu_ld=${lt_cv_prog_gnu_ld=yes}
| lt_cv_sys_global_symbol_pipe=${lt_cv_sys_global_symbol_pipe=}
| lt_cv_sys_path_separator=${lt_cv_sys_path_separator=:}
configure:1208: checking whether make sets $(MAKE)
configure:1228: result: yes
configure:1274: checking for a BSD-compatible install
configure:1328: result: /bin/install -c
configure:1368: checking for /c/bin/emacs-21.2/bin/emacs
configure:1398: result: /c/bin/emacs-21.2/bin/emacs
configure:1414: checking if /c/bin/emacs-21.2/bin/emacs is XEmacs
/c/bin/emacs-21.2/bin/emacs -batch -no-site-file -eval (let* ((x (if
(string-match "XEmacs" emacs-version) "yes" "no"))) (write-region (if
(stringp x) (princ x 'ignore) (prin1-to-string x)) nil
"./conftest-1336"))
Wrote c:/usr/uli/auctex/conftest-1336
=> dummy
configure:1436: result: no
configure:1555: checking where lisp files go
configure:1668: result: /c/bin/emacs-21.2/site-lisp/auctex
configure:1679: checking for tex
configure:1697: found /c/TeX/bin/win32/tex
configure:1710: result: /c/TeX/bin/win32/tex
configure:1719: checking for makeinfo
configure:1737: found /bin/makeinfo
configure:1750: result: /bin/makeinfo
configure:1759: checking if /bin/makeinfo understands @acronym{}
configure:1764: result: yes
configure:1759: checking if /bin/makeinfo understands @env{}
configure:1764: result: yes
configure:1759: checking if /bin/makeinfo understands @option{}
configure:1764: result: yes
configure:1780: checking for install-info
configure:1798: found /bin/install-info
configure:1811: result: /bin/install-info
configure:1988: creating ./config.status

## ---------------------- ##
## Running config.status. ##
## ---------------------- ##

This file was extended by auctex config.status 11.14, which was
generated by GNU Autoconf 2.57.  Invocation command line was

  CONFIG_FILES    =
  CONFIG_HEADERS  =
  CONFIG_LINKS    =
  CONFIG_COMMANDS =
  $ ./config.status

on DOMINUS

config.status:609: creating Makefile
config.status:609: creating doc/Makefile

## ---------------- ##
## Cache variables. ##
## ---------------- ##

ac_cv_env_build_alias_set=
ac_cv_env_build_alias_value=
ac_cv_env_host_alias_set=
ac_cv_env_host_alias_value=
ac_cv_env_target_alias_set=
ac_cv_env_target_alias_value=
ac_cv_path_EMACS=/c/bin/emacs-21.2/bin/emacs
ac_cv_path_INSTALL_INFO=/bin/install-info
ac_cv_path_MAKEINFO=/bin/makeinfo
ac_cv_path_TEX=/c/TeX/bin/win32/tex
ac_cv_path_install='/bin/install -c'
ac_cv_prog_make_make_set=yes
lt_cv_cc_dll_switch=-mdll
lt_cv_compiler_c_o=yes
lt_cv_compiler_o_lo=yes
lt_cv_deplibs_check_method='file_magic file format
pei*-i386(.*architecture: i386)?'
lt_cv_file_magic_cmd='$OBJDUMP -f'
lt_cv_file_magic_test_file=
lt_cv_global_symbol_to_c_name_address='sed -n -e '\''s/^: \([^ ]*\) $/
{\"\1\", (lt_ptr) 0},/p'\'' -e '\''s/^[BCDEGRST] \([^ ]*\) \([^ ]*\)$/
{"\2", (lt_ptr) \&\2},/p'\'''
lt_cv_global_symbol_to_cdecl='sed -n -e '\''s/^. .* \(.*\)$/extern char
\1;/p'\'''
lt_cv_ld_reload_flag=-r
lt_cv_need_dllmain=no
lt_cv_prog_cc_can_build_shared=yes
lt_cv_prog_cc_no_builtin=
lt_cv_prog_cc_pic='   -DDLL_EXPORT'
lt_cv_prog_cc_pic_works=yes
lt_cv_prog_cc_shlib=
lt_cv_prog_cc_static=-static
lt_cv_prog_cc_static_works=yes
lt_cv_prog_cc_wl=-Wl,
lt_cv_prog_gnu_ld=yes
lt_cv_sys_global_symbol_pipe=
lt_cv_sys_path_separator=:

## ----------------- ##
## Output variables. ##
## ----------------- ##

DEFS='-DPACKAGE_NAME=\"auctex\" -DPACKAGE_TARNAME=\"auctex\" -DPACKAGE_V
ERSION=\"11.14\" -DPACKAGE_STRING=\"auctex\
11.14\" -DPACKAGE_BUGREPORT=\"auc-tex@sunsite.dk\" '
ECHO_C=''
ECHO_N='-n'
ECHO_T=''
EMACS='/c/bin/emacs-21.2/bin/emacs'
EMACS_FLAVOR='emacs'
INSTALL_DATA='${INSTALL} -m 644'
INSTALL_INFO='/bin/install-info'
INSTALL_PROGRAM='${INSTALL}'
INSTALL_SCRIPT='${INSTALL}'
LIBOBJS=''
LIBS=''
LTLIBOBJS=''
MAKEINFO='/bin/makeinfo'
MAKEINFO_MACROS=''
PACKAGE_BUGREPORT='auc-tex@sunsite.dk'
PACKAGE_NAME='auctex'
PACKAGE_STRING='auctex 11.14'
PACKAGE_TARNAME='auctex'
PACKAGE_VERSION='11.14'
PATH_SEPARATOR=':'
SET_MAKE=''
SHELL='/bin/sh'
TEX='/c/TeX/bin/win32/tex'
XEMACS='no'
bindir='${exec_prefix}/bin'
build_alias=''
datadir='${prefix}/share'
exec_prefix='${prefix}'
host_alias=''
includedir='${prefix}/include'
infodir='${prefix}/info'
libdir='${exec_prefix}/lib'
libexecdir='${exec_prefix}/libexec'
lispdir='/c/bin/emacs-21.2/site-lisp/auctex'
localstatedir='${prefix}/var'
mandir='${prefix}/man'
oldincludedir='/usr/include'
packagedir=''
prefix='/usr/local'
program_transform_name='s,x,x,'
sbindir='${exec_prefix}/sbin'
sharedstatedir='${prefix}/com'
sysconfdir='${prefix}/etc'
target_alias=''

## ----------- ##
## confdefs.h. ##
## ----------- ##

#define PACKAGE_BUGREPORT "auc-tex@sunsite.dk"
#define PACKAGE_NAME "auctex"
#define PACKAGE_STRING "auctex 11.14"
#define PACKAGE_TARNAME "auctex"
#define PACKAGE_VERSION "11.14"

configure: exit 0

--- end config.log ---

Re: Automatic Compiling

[David Kastrup]

"Ulrich Dirr" <ud@art-satz.de> writes:

> David Kastrup wrote:
> > "Ulrich Dirr" <ud@art-satz.de> writes:
> > Apart from "/c/bin/emacs-21.2/site-lisp" being about the weirdest
> > directory I ever saw for installing Emacs files.  Are you sure that
> > this is in your load-path?
> 
> I thought emacs-21.2/site-lisp/auctex is a good place. Where should it
> be installed?

Well, not under a bin directory.  Where are your other Emacs-related
files installed?

> > AUCTeX comes with an info file, and you have installed it.  C-h i
> > d m auctex RET should lead you to the AUCTeX info, and it has a
> > chapter "Installation".
> >
> >> Second I don't see any other behavior when compiling. I still
> >> have to input everything by hand (as listed in my first mail).
> >
> > C-h v AUC-TeX-version RET
> >
> > should tell you the installed version.
> 
> tells CVS-5.297, is this the new version?

Yes.  At least if any distributor distributes CVS versions, I'll kill
him.

> > Probably you installed into a wrong place.  What was the line that
> > you specified to ./configure?  What is the output of config.log?
> 
> ???
> 
> Ulrich Dirr
> 
> P.S. what should have changed concerning the compile cycle keyboarding?

compile cycle keyboarding?  Uh, what?

> --- start config.log ---
> This file contains any messages produced by compilers while
> running configure, to aid debugging if configure makes a mistake.
> 
> It was created by auctex configure 11.14, which was
> generated by GNU Autoconf 2.57.  Invocation command line was
> 
>   $
> ./configure --with-emacs=/c/bin/emacs-21.2/bin/emacs --with-texmf-dir=/c
> /tex/bin/win32/tex --with-lispdir=/c/bin/emacs-21.2/site-lisp/auctex

The texmf-dir is supposed to be the top of the TeX hierarchy (with
subdirectories tex, doc, bibtex, and a few others).  You seem to be
fond of installing data directories under */bin/*.  I don't suppose
that the programs themselves suggest such paths?

> hostname = DOMINUS
> uname -m = i686
> uname -r = 1.0.8(0.46/3/2)
> uname -s = MINGW32_NT-5.0

Does MINGW32 use the /c syntax?  Well, obviously it does.  What kind
of Emacs do you use?

> PATH: /c/bin/emacs-21.2/bin

I did not really want to know that...

Rest looks ok.  One thing worth noting is that it looks like you have
both mingw32 as well as Cygwin installed.  Not sure that is the best
idea.  What flavor of Emacs are you running?

Perhaps it would be an idea, if you are having problems, to report
them with M-x TeX-submit-bug-report, this gives us somewhat more
information.  The way the report looks up to now, things seem to be
properly installed and should work, as long as your have the required
(require 'tex-site) in your .emacs file.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

Re: Automatic Compiling

[Ulrich Dirr]

David Kastrup wrote:
> "Ulrich Dirr" <ud@art-satz.de> writes:
>
>> David Kastrup wrote:
>>> "Ulrich Dirr" <ud@art-satz.de> writes:
>>> Apart from "/c/bin/emacs-21.2/site-lisp" being about the weirdest
>>> directory I ever saw for installing Emacs files.  Are you sure that
>>> this is in your load-path?
>>
>> I thought emacs-21.2/site-lisp/auctex is a good place. Where should
>> it be installed?
>
> Well, not under a bin directory.  Where are your other Emacs-related
> files installed?

At the moment /bin/emacs-21.2 have subdirs /bin, /etc, /info, /lisp,
/lock (empty), and /site-lisp. I wanted to separate all packages which
did not come with the standard installation (I used a precompiled bin
version), e.g. /auctex, /leim, and /mule-ucs). Maybe the best idea is to
put every local lisp package into /usr/local[/emacs]/site-lisp???


>> P.S. what should have changed concerning the compile cycle
>> keyboarding?
>
> compile cycle keyboarding?  Uh, what?

My original question was how I to eliminate the tedious repetitive
typing, and gave as an example the steps below:

>> Is there an easy way how I can customize my PDFeLaTeX compile cycles?
I
>> find it somewhat tedious to do all steps by hand.
>> (1) going to the compile menu and selecting PDFeLaTeX
>> (2) explictely confirm saving
>> (3) typing C-c C-c after successfully compiling
>> (4) typing 'View PDF'
>> (5) correcting the status line 'View PDF command: start
<file>.tex.pdf'
>> to <file>.pdf
>>
>> (5) or how can I change the output behavior so that <file>.tex.pdf is
>> written (which I would prefer).
>>
>> I presume that this is nothing special as a lot of TeX afficionados
are
>> using emacs and solved this already.

You answered:
> The current developer version does this, you might want to try it
> using anonymous CVS.

So my hopes now were that after installing the CVS version something
have changed visible. But when TeXing some file nothing seems to have
changed at all (concerning the numerous keystrokes).


>> --- start config.log ---
>> This file contains any messages produced by compilers while
>> running configure, to aid debugging if configure makes a mistake.
>>
>> It was created by auctex configure 11.14, which was
>> generated by GNU Autoconf 2.57.  Invocation command line was
>>
>>   $
>> ./configure --with-emacs=/c/bin/emacs-21.2/bin/emacs
>> --with-texmf-dir=/c /tex/bin/win32/tex
>> --with-lispdir=/c/bin/emacs-21.2/site-lisp/auctex
>
> The texmf-dir is supposed to be the top of the TeX hierarchy (with
> subdirectories tex, doc, bibtex, and a few others).  You seem to be
> fond of installing data directories under */bin/*.  I don't suppose
> that the programs themselves suggest such paths?

Ah, ok, so it should be probably /c/tex/texmf (I have TeXLive/fpTeX
installed in c:/TeX)


>> hostname = DOMINUS
>> uname -m = i686
>> uname -r = 1.0.8(0.46/3/2)
>> uname -s = MINGW32_NT-5.0
>
> Does MINGW32 use the /c syntax?  Well, obviously it does.  What kind
> of Emacs do you use?
>
>> PATH: /c/bin/emacs-21.2/bin
>
> I did not really want to know that...

So you mean there's something wrong here?


> Rest looks ok.  One thing worth noting is that it looks like you have
> both mingw32 as well as Cygwin installed.  Not sure that is the best
> idea.  What flavor of Emacs are you running?

GNU Emacs 21.2.1 which is called NTEmacs I think (I then downloaded it
from ftp.gnu.org/gnu/windows/emacs/latest/. (BTW I plan to update to
21.3)

 Best regards,
Ulrich Dirr

Re: Automatic Compiling

[Kai Großjohann]

"Ulrich Dirr" <ud@art-satz.de> writes:

> At the moment /bin/emacs-21.2 have subdirs /bin, /etc, /info, /lisp,
> /lock (empty), and /site-lisp. I wanted to separate all packages which
> did not come with the standard installation (I used a precompiled bin
> version), e.g. /auctex, /leim, and /mule-ucs). Maybe the best idea is to
> put every local lisp package into /usr/local[/emacs]/site-lisp???

The Unix convention is to have a directory for a package.  The
directory for Emacs could be /usr/local/emacs-21.2.  Then this
directory contains subdirs bin, man, info, lib, share.  The bin
directory contains the programs.

So, the Emacs executable would be /usr/local/emacs-21.2/bin/emacs.

But you have a directory c:/bin (or /c/bin or whatever) which is
named bin but does not contain programs.  Instead, it contains a
subdir emacs-21.2 which contains subsubdirs...

So you could rename /c/bin to /c/sw or /c/local or /c/pkg or
something, and then David wouldn't have been surprised.
-- 
file-error; Data: (Opening input file no such file or directory ~/.signature)