headers
Frank Küster | 3 Aug 2005 15:42
Picon

filling error (commented lines produced!)


Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.

If the bug (or problem) is triggered by a specific (La)TeX
file, you should try to produce a minimal sample file showing the
problem and include it in your report.

This is how it looked like before:

\subsection*{\dots Einzelmolekülexperimente bei verschiedenen GdmCl-Konzentrationen}
\label{sec:dots-single-molec}

\begin{minipage}{0.33\linewidth}
  \includegraphics[width=\linewidth]{0M}%
  \includegraphics[width=\linewidth]{0-25M}%
  \includegraphics[width=\linewidth]{0-5M}%
  \includegraphics[width=\linewidth]{0-75M}%
  \includegraphics[width=\linewidth]{1M}%
\end{minipage}
\begin{minipage}{0.33\linewidth}
  \includegraphics[width=\linewidth]{1-25M}%
  \includegraphics[width=\linewidth]{1-5M}%
\includegraphics[width=\linewidth]{1-75M}%
  \includegraphics[width=\linewidth]{2M}%
  \includegraphics[width=\linewidth]{2-25M}%
\end{minipage}
      \includegraphics[width=\linewidth]{2-5M}%
      \includegraphics[width=\linewidth]{3M}%
      \includegraphics[width=\linewidth]{4M}%
(Continue reading)

Permalink | Reply | 1 comment |
headers
Uwe Siart | 3 Aug 2005 16:40
Picon
Favicon

Re: filling error (commented lines produced!)

On 3 Aug 2005 at 15:42, Frank Küster wrote:

> I pinpoint the region that contains the last five lines with
> \includegrahics macros and do C-c C-e minipage RET RET RET.  I get:

No problem here with a recent developer version of AUCTeX.

--

-- 
Uwe
Permalink | Reply | 0 comments |
headers
Stefan Pofahl | 5 Aug 2005 14:17
Picon

insert \newline{}RET via keystroke

Hello,
I want to define the keystroke "C-RET" as:
------
   \newline{}RET
   CURSOR
------
If I define this in init.el (or .emacs):
(add-hook 'LaTeX-mode-hook 
  '(lambda nil
      ; control key bindings
      (define-key LaTeX-mode-map '[(control return)] "\\newline\n")   
      ;; newline (\f = C-f, \n = C-n)
      ;(define-key LaTeX-mode-map '"\C-RET" "\\newline\n")  
      ;; "\C-RET" = (control return); newline
    )    ) ;;end add-hook 'LaTeX-mode-hook

The result is:
-------
   \newline{CURSOR}
----------------------------
Workaround:
First define a kbd-macro, then call the macro:
(defalias 'neuezeile
  (read-kbd-macro "\\newline RET <right> RET"))
(add-hook 'LaTeX-mode-hook 
  '(lambda nil
      ; control key bindings
      (define-key LaTeX-mode-map '[(control return)] 'neuezeile)
      ;; insert \newline{}
    )    ) ;;end add-hook 'LaTeX-mode-hook
(Continue reading)

Permalink | Reply | 0 comments |
headers
Harald von Aschen | 9 Aug 2005 12:24
Picon
Picon

Re: Install report: Emacs and Windows 98

At 17:13 29.07.05 +0200, Ralf Angeli wrote:
>* Harald von Aschen (2005-07-28) writes:

Hi Ralf!

Sorry for not writing earlier. I was in Holidays for one week.

> > GS="F:/Programme/gs/gs8.13/bin/gswin32c.exe" ./configure 
> --prefix=g:/tst/emac
> > s-21.3 --with-texmf-dir=f:/Programme/TeXLive/texmf
> > checking whether make sets $(MAKE)... yes
> > checking for a BSD-compatible install... /bin/install -c
> > checking for date in ChangeLog... 2005-07-21
> > checking for release in ChangeLog... not found, using 2005-07-21 instead
> > checking for emacs... /f/PROGRAMME/CYGWIN/BIN/emacs
> > checking if /f/PROGRAMME/CYGWIN/BIN/emacs is XEmacs... no
> > checking for Emacs prefix... cat: ./conftest-1648743: No such file or 
> directory
>
>The shell finds an Emacs in a Cygwin path.  This looks a bit messed
>up.  Can you make sure that the MSYS/MinGW and Cygwin stuff
>(executables, libs, etc.) don't mix?  Maybe this will help already.
>If it doesn't, please send the file config.log which you should find
>in AUCTeX's build directory.  (Zip it before sending.)

Argh, no good, my fault. This should have been deleted in my $path, I'm 
really sorry.

Again. Now with the snapshot auctex-20050806-a.
(Continue reading)

Permalink | Reply | 2 comments |
headers
Ralf Angeli | 10 Aug 2005 11:08
Picon

Re: Install report: Emacs and Windows 98

* Harald von Aschen (2005-08-09) writes:

> In Mingw I have to set the path-variable to my needs, this is GhostScript, 
> TeXLive and the rest who has aready been in path:
>
> $ PATH=".:/usr/local/bin:/mingw/bin:/bin: \
> /c/WINDOWS:/c/WINDOWS/COMMAND: \
> /f/PROGRAMME/GS/GS8.13/BIN: \
> /f/PROGRAMME/TEXLIVE/BIN/WIN32"
>
> $ export PATH
>
> After that the installation runs through without any problems and with
>
> $ ./configure --prefix=g:/tst/emacs-21.3 \
> --with-texmf-dir=f:/Programme/TeXLive/texmf
>
> and then make and then make install.

Okay.

> Perhaps this could be a hint in the 
> installation guide for Windows users?

You mean setting $PATH?  I think this can be mentioned in the
installation instructions.  But users should rather set the permanent,
system-wide variable than doing this temporarily in the shell used for
the installation.  In the end, many of the programs in $PATH are
supposed to be found after the installation as well.  And many may not
have variables associated with them which hold the path to the
(Continue reading)

Permalink | Reply | 1 comment |
headers
Harald von Aschen | 10 Aug 2005 20:19
Picon
Picon

Re: Install report: Emacs and Windows 98

At 11:08 10.08.05 +0200, Ralf Angeli wrote:
>* Harald von Aschen (2005-08-09) writes:
>
> > In Mingw I have to set the path-variable to my needs, this is GhostScript,
> > TeXLive and the rest who has aready been in path:

[...]

> > Perhaps this could be a hint in the
> > installation guide for Windows users?
>
>You mean setting $PATH?  I think this can be mentioned in the
>installation instructions.  But users should rather set the permanent,
>system-wide variable than doing this temporarily in the shell used for
>the installation.  In the end, many of the programs in $PATH are
>supposed to be found after the installation as well.  And many may not
>have variables associated with them which hold the path to the
>executable.

Here Ghostscript hasn't set up $path. E.g. the command line tool epstopdf 
for converting eps files to pdf who uses gswin32c.exe is nevertheless working.

And thank you very much, Ralf, for your great help!

Best regards

Harald
Permalink | Reply | 0 comments |
headers
Martin Siegumfeldt | 11 Aug 2005 17:44
Picon
Picon
Favicon

Next version of Auctex?

Are there any plans for when the next Auctex release will be up? I have 
a new FC4 installation, and won't install 11.55, if the next release is 
just around the corner

Br,
Martin
Permalink | Reply | 0 comments |
headers
Harald von Aschen | 14 Aug 2005 19:43
Picon
Picon

Multifile document questions

(AUCTex snapshot dated 2005-07-16).

Hi,

Perhaps this is wrong asking this question about only an old snapshot?

Please consider following:

Master document with typical AMS-classes loaded
\usepackage{amsmath,amssymb,amsthm}

Subdocs are included with the LaTeX-command \include, and in .emacs or 
site-start.el there is
(require 'tex-site)
(setq TeX-auto-save t)
(setq TeX-parse-self t)
(setq-default TeX-master nil)

Then I want to insert an environment in my subdoc by C-c C-e and a type 
mismatch "equa", so it is inserted in the auto file.

O.k., perhaps resetting buffer would help? Do the menu command "LaTeX" -> 
Multifile/Parsing -> Reset Buffer (C-c C-n). This helps, "equa" has gone. 
But then the AMS-environments like "split" are no longer available. Only 
closing the subdoc and open it again in Emacs helps. Correct? (I have just 
started this subdoc, so "split" has never been used here.) In the subdoc 
defined macros are known.

Next: C-c C-c or TeX-command-master called in the subdoc runs on the master 
file and correctly starts LaTeX/PDFTeX or BiBTeX etc. after each change in
(Continue reading)

Permalink | Reply | 2 comments |
headers
CB | 15 Aug 2005 12:54
Picon

Problem running configure for preview-latex-0.9.1

Hi,

I have managed to install and run Auctex on my Win XP box (with
XEmacs), using the excellent instructions on the Auctex site.

I'm having some trouble getting preview-latex going though. I've
pasted the results of my 'configure' attempt below.

Note that my %Systemdrive% is oddly labelled H:, but that didn't cause
any problems with configure for Auctex. I've  used the short version
of 'Program Files' here -- this was just me trying things; the first
time I had used the full-length version. I also get the same result if
I run 'configure' without offering any prefix options.

------ 8<--------

$ ./configure --prefix=H:/progra~1/XEmacs --with-xemacs --with-texmf-dir=H:/tex
mf/
checking whether make sets $(MAKE)... yes
checking for a BSD-compatible install... /bin/install -c
checking for xemacs... /h/Program
Files/XEmacs/XEmacs-21.4.13/i586-pc-win32/xemacs
checking if /h/Program
Files/XEmacs/XEmacs-21.4.13/i586-pc-win32/xemacs is XEmacs... yes
checking for XEmacs prefix... "h:\Program
Files\XEmacs\XEmacs-21.4.13\i586-pc-win32"
checking if XEmacs is recent enough... yes
checking if build directory is valid... yes
checking for XEmacs package directory...
${datadir}/xemacs/xemacs-packages\H:\Program Fil
(Continue reading)

Permalink | Reply | 0 comments |
headers
Ralf Angeli | 15 Aug 2005 14:21
Picon

Re: Multifile document questions

* Harald von Aschen (2005-08-14) writes:

> Then I want to insert an environment in my subdoc by C-c C-e and a type 
> mismatch "equa", so it is inserted in the auto file.

I don't understand that sentence.

> O.k., perhaps resetting buffer would help? Do the menu command "LaTeX" -> 
> Multifile/Parsing -> Reset Buffer (C-c C-n). This helps, "equa" has gone. 
> But then the AMS-environments like "split" are no longer available. Only 
> closing the subdoc and open it again in Emacs helps. Correct? (I have just 
> started this subdoc, so "split" has never been used here.) In the subdoc 
> defined macros are known.
>
> Next: C-c C-c or TeX-command-master called in the subdoc runs on the master 
> file and correctly starts LaTeX/PDFTeX or BiBTeX etc. after each change in 
> the subdocs or in the master. TeX-command-buffer or C-c C-b should run on 
> the buffer but does not recognize when changes have been done, so after the 
> first LaTeX-call only "View" is proposed as the next command and I have to 
> enter manually LaTeX.

Great, that bug is of the same category like the one I fixed for
`TeX-ispell-document' a few weeks ago.  `TeX-command-buffer' calls
`TeX-command-region'.  This creates a _region_.tex file in the
directory of the master file and prompts for the command by calling
`TeX-command-query'.  `TeX-command-query' calls `TeX-command-next' for
figuring out which command to call next.  In order to find out if any
of the files necessary to produce the derived file ("_region_.dvi" in
this case) is newer than the derived file, it calls `TeX-check-files'
with "_region_.dvi" as argument for `derived' and ("_region_") as
(Continue reading)

Permalink | Reply | 1 comment |

Gmane