* Christian Schlauer (2007-06-24) writes: > I'd say the period has to be allowed in AUCTeX, because it is `valid > LaTeX', as it seems. Fixed in CVS. Thanks for the report. -- -- Ralf
Thank you, you are right, actually it's an emacs problem, the behauviour in C-Mode is the same, i will report it to an appropriate list. Georg _________________________________________________________________ Express yourself instantly with MSN Messenger! Download today it's FREE! http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
Hi,
[pst-pdf: Produce an pdf-file with using postscript environments where
you place pstricks pictures environments etc.]
When using pst-pdf, you are supposed to run the shell script ps4pdf to
produce a pdf-file, which I run by setting a local file variable.
When typing C-c C-v afterwards, AUCTeX opens ghostview to view the
results.
The process to find the right extension by scanning LaTeX's output for
viewing is not sufficient since a further run of ps2pdf was applied to
the result of last LaTeX run.
Maybe, one could check whether a newer pdf-file is present?
Something along:
(defun TeX-my-view ()
"Select the viewer depending on local variables like
`TeX-command-default' and `TeX-PDF-mode'."
(interactive)
(if (or (eq TeX-command-default "make pdf") (eq TeX-PDF-mode t))
(TeX-command "Xpdf" 'TeX-master-file)
;; (message "%s" TeX-command-default)
(if (file-newer-than-file-p (TeX-master-file "pdf" nil) (TeX-master-file "dvi" nil))
(TeX-command "Xpdf" 'TeX-master-file)
(if (file-newer-than-file-p (TeX-master-file "ps" nil) (TeX-master-file "dvi" nil))
(Continue reading)
Holger Sparr <sparr+usenet <at> mfk.tu-dresden.de> writes: > [pst-pdf: Produce an pdf-file with using postscript environments where > you place pstricks pictures environments etc.] > > When using pst-pdf, you are supposed to run the shell script ps4pdf to > produce a pdf-file, which I run by setting a local file variable. > > When typing C-c C-v afterwards, AUCTeX opens ghostview to view the > results. > > The process to find the right extension by scanning LaTeX's output for > viewing is not sufficient since a further run of ps2pdf was applied to > the result of last LaTeX run. > > > Maybe, one could check whether a newer pdf-file is present? Perhaps we should scrap the logic for viewing (and printing) and always open the newest output file candidate independent of PDF-TeX-mode? -- -- David Kastrup, Kriemhildstr. 15, 44793 Bochum
* David Kastrup (2007-07-11) writes: > Perhaps we should scrap the logic for viewing (and printing) and > always open the newest output file candidate independent of > PDF-TeX-mode? Sounds interesting. Once we have toolchains we could also define the viewer explicitely in a toolchain. Nevertheless we need to fix the mode recognition. The pst-pdf case worked some time ago. It probably stopped working when I added the pstricks.el style file. But I have to check this. -- -- Ralf
* Ralf Angeli (2007-07-11) writes: > Nevertheless we need to fix the mode recognition. The pst-pdf case > worked some time ago. It probably stopped working when I added the > pstricks.el style file. But I have to check this. It's fixed now. -- -- Ralf
Remember to cover the basics, that is, what you expected to happen and
what in fact did happen.
Be sure to consult the FAQ section in the manual before submitting
a bug report. 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.
Your bug report will be posted to the AUCTeX bug reporting list.
------------------------------------------------------------------------
Hi,
I like complexe LaTeX documents to be organized in directories
and subdirectories but it seem to generate problems with
auctex. Anyway I particularly like functionalities provided by
auctex that's why I am very disappointed that something goes
wrong in this case. The problems appear in style loading.
Let's take an example : The master directory (let's name it
..../MyDoc) contains the master file MyDoc.tex.
It contains as well a directory Chapter-1 containing all files
corresponding to chapter one of the document and in particular
a file Chapter-1.tex. Hence there is an input command
\input{Chapter-1/Chapter-1} in the MyDoc.tex file.
In the subdirectory Chapter-1 lives a file Section-1-1.tex as
well. The latter is called by Chapter-1.tex by the input
(Continue reading)
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. Be sure to consult the FAQ section in the manual before submitting a bug report. 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. Your bug report will be posted to the AUCTeX bug reporting list. ------------------------------------------------------------------------ Hi, I already send a bug report a few days ago. Now investigating the code more carefully I wonder why ther are this two lines of code at line 1831 in the tex.el file : (setq default-directory (expand-file-name (file-name-directory style)) It does semme consistant with the way the master-dir is set (relatively) at line 1742 in the tex.el file : (master-dir (if (stringp TeX-master) (file-name-directory (file-relative-name TeX-master)) "./"))(Continue reading)
Remember to cover the basics, that is, what you expected to happen and what in fact did happen. Be sure to consult the FAQ section in the manual before submitting a bug report. 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. Your bug report will be posted to the AUCTeX bug reporting list. ------------------------------------------------------------------------ Hi, When I have an included file in my document whose name is to long, erros cannot be retrieved correctly in it : When typing C-c `or M-g n, a truncated file is open. It means the file name is note correctly read in the output buffer by the parse method. It occurs when the file name in the output buffer is splitt with a newline in it because it is to long. In this case, the parse method only take the part being on the first line and hence tries to open a file with truncated truncated name which does not exist and where the error can naturally not be found ! In my opinion, the problem is in file tex-buf.el at line 1370 in command : (rplaca TeX-error-file (TeX-match-buffer 2))))(Continue reading)
* Pierre Lorenzon (2007-07-16) writes: > I already send a bug report a few days ago. Now investigating > the code more carefully I wonder why ther are this two lines of > code at line 1831 in the tex.el file : > > (setq default-directory (expand-file-name > (file-name-directory > style)) They were supposed to fix a bug. See <URL:http://thread.gmane.org/1121262217.11339.20.camel%40localhost.localdomain>. -- -- Ralf
RSS Feed12 | |
|---|---|
16 | |
4 | |
2 | |
13 | |
1 | |
4 | |
3 | |
10 | |
7 | |
6 | |
2 | |
4 | |
2 | |
2 | |
2 | |
4 | |
5 | |
3 | |
7 | |
2 | |
12 | |
9 | |
8 | |
17 | |
9 | |
16 | |
6 | |
6 | |
14 | |
3 | |
35 | |
19 | |
16 | |
4 | |
9 | |
24 | |
29 | |
15 | |
6 | |
3 | |
7 | |
11 | |
4 | |
14 | |
12 | |
28 | |
34 | |
7 | |
5 | |
10 | |
14 | |
11 | |
6 | |
18 | |
8 | |
27 | |
2 | |
6 | |
36 | |
11 | |
6 | |
14 | |
61 | |
41 | |
2 | |
15 | |
15 | |
9 | |
30 | |
23 | |
43 | |
42 | |
78 | |
60 | |
26 | |
46 | |
35 | |
47 | |
60 | |
11 | |
25 | |
17 | |
16 | |
18 | |
38 | |
20 | |
47 | |
60 | |
23 | |
43 | |
85 | |
24 | |
7 | |
47 | |
96 | |
99 | |
39 |
