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
initialize
the variable every time if a single syntax table is to be shared between
all the buffers of dirrerent modes.
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-auctex
-table-parent foo (make-char-table 'syntax-table nil))
(char-to-string (with-syntax-table foo (char-syntax ?\(
=
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-auctex
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
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. In addition check if the bug is reproducable with an
up-to-date version of AUCTeX. So please upgrade to the version
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. In addition check if the bug is reproducable with an
up-to-date version of AUCTeX. So please upgrade to the version
(unless (featurep 'xemacs)
...
(defun TeX-activate-region ()
(setq deactivate-mark nil)
(activate-mark))
...
... )
---
Regards,
Ikumi Keita
P.S. Although I used goto-char in the patch-2, it may be better to use
set-mark
Well, I think that's actually an improvement. So I committed your
previous version but with `set-mark' instead of `goto-char'.
I see. Thanks!
Bye,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo
h the defcustom of `TeX-modes' when
tex-site.el is loaded, because it has the line
:set 'TeX-modes-set
. Thus `tex-site-unload-hook' should remove these advices when
`advice-add' is available.
I confirmed that the attached crude workaround makes unloading tex-site
to work as expected.
Regards,
Ik
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. In addition check if the bug is reproducable with an
up-to-date version of AUCTeX. So please upgrade to the version
Hi Tassilo,
> Do you know if XEmacs has some similar feature, i.e., a way to check
> which variables have been set using file (or directory) local variables?
Hmm, now I'm looking at files.el of xemacs and unfortunately xemacs
doesn't seem to have such features.
Bye,
Ikumi
Hi Tassilo,
> Ikumi, I'll implement that now. Could you please check if it works as
> expected in the coming days?
With the updated code, the error went away. Thank you.
Bye,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
[]
("Load\\(Class\\)\\(\\[\\([^#\\.%]*?\\)\\]\\)?{\\([^#\\.\n\r]+?\\)}"
(3 4 1) LaTeX-auto-style)
;; \LoadClassWithOptions{}[]
("Load\\(Class\\)WithOptions\\(\\){\\([^#\\.\n\r]+?\\)}"
(2 3 1) LaTeX-auto-style)
, with capitalized word "Class&quo
> I attach a patch based on the above idea.
Added trivial fix for coherency (provided -> match).
Bye,
Ikumi Keita
diff -r c52403a42881 latex.el
--- a/latex.el Wed Dec 21 22:58:09 2016 +0900
+++ b/latex.el Thu Feb 02 23:40:09 2017 +0900
@@ -1799,9 +1
%% End:
I checked with the given example. It seems that highlighting works as
expected. See the attached images, please.
Bye,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
>> I attach a patch based on the above idea.
> Added trivial fix for coherency (provided -> match).
Sorry for noise, I had to change "options" to "option", too.
Bye,
Ikumi Keita
diff -r c52403a42881 latex.el
--- a/latex.el Wed Dec 21 22:58:09 2016 +0900
+++
t; Tassilo
> BTW: You are a contributor since a very long time (12 years!) and I
> completely trust your ability to not mess up things beyond repair. So
> I'd happily give you push access to our repository if you want to.
> Interested?
Thank you very much. I would like to recieve t
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. In addition check if the bug is reproducable with an
up-to-date version of AUCTeX. So please upgrade to the version
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. In addition check if the bug is reproducable with an
up-to-date version of AUCTeX. So please upgrade to the version
ct the default value of
`TeX-japanese-process-output-coding-system' was changed to nil
recently.) Even my patch "preview-latex-fix" is not sufficient about
this point. The coding-system argument supplied to
`decode-coding-string' should not simply be `buffer-file-coding-system'.
I woul
ot;foo" LaTeX-fixme-active-region))
The idea is very crude and ad hoc, but it does the required job anyway,
at the cost that it looks as if the macro "foo" took only one argument.
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
suppose that comparing the `(current-column)' and
`beg-col' would be necessary. (Or just using `(max (- (current-column)
1) (+ 2 beg-col))' might be sufficient. I haven't considered the
situation in detail yet.)
Regards,
Ikumi Keita
___
bug-auctex mailing l
any other idea?
I think that the sign test can be omitted altogether if we use `max'.
That is, just
(max (+ 2 beg-col)
(- (current-column) 1)))
is enough. This code does the expected job on my machine.
Regards,
Ikumi Keita
___
Hi all,
I worked on to resolve the remaining problems with respect to the
incompatibility between preview-latex and Japanese LaTeX, and think that
I managed to sort out them. Please take a look at the attached patch.
My basic plan, in addtion to the part described before in
requires manual execution instead.
If someone finds difficulties with this commit, feel free to ask me.
Best regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
Remember to cover the basics. Including a minimal LaTeX example
file exhibiting the problem might help.
Preview-latex fails if the length of the file name or the amount of the
document is sufficiently large.
[How to reproduce]
(0) Enable preview-latex.
(1) Save the attached file
yet installed on your box. I
encountered similar fails with AUCTeX before the update. My tests only
pass with the updated codes.
Bye,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
; parameters for evince and atril (number of letters?
bytes in UTF8? or other?), so don't know how we should change this
part.)
Best,
Ikumi Keita
diff --git a/tex-buf.el b/tex-buf.el
--- a/tex-buf.el
+++ b/tex-buf.el
@@ -492,6 +492,11 @@
(setq TeX-current-process-region-p t))
((eq file
dd some comments above the
`current-column'.
And I noticed that `(TeX-line-number-at-pos)' should be replaced with
`(1+ (TeX-current-offset))' like `TeX-current-line' does, because the
former does not return the required value for the viewer when narrowing
is in effect.
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
does work as expected, at least for the
xemacs 21.5 binary I found and installed on my machine.
I tried applying the previous patch, and to my delight, it makes
preview-latex to cooperate with Japanese LaTeX on w32 xemacs, too.
Regards,
Ikumi Keita
diff --git a/prv-xemacs.el b/prv-xemacs.el
--- a/prv
Hi all,
At last I managed to figure out the roots of this wierd symptom. And it
also turned out that bug#20773 has the same origin, so I'm cc'ing to
20...@debbugs.gnu.org, too.
>>>>> Ikumi Keita <ik...@ikumi.que.jp> writes:
> Preview-latex fails if the length of the
you suggested as
option 2, though for `LaTeX-env-label' only.
I hope that anyone else makes out a comprehensive solution that covers
other functions as well...
Bye,
Ikumi Keita
--- latex.el~ 2017-09-10 03:04:17.265116000 +0900
+++ latex.el 2017-09-10 03:04:51.79808 +0900
@@ -1152,9 +1152,13 @@
lem. If you know
how to apply the patch the and re-build AUCTeX, the problem would go
away. If not, let us know and think together what to do.
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
latex process runs, but I suppose that doesn't matter for
most cases.
However, it is reported[1] that metapost in older TeX distribution does
not run correctly under "max_print_line=1000", so if you encounter this
trouble, you have to edit your file a bit further.
Regards,
Ikumi Keita
[1]
heuristic logic used there.
would not apply for non-preview-latex runs in AUCTeX. The heuristic
logic is still necessary due to MikTeX.
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
provide more detailed information so that we can examine the
problem? Please include the output of M-x TeX-submit-bug-report RET and
sample file which triggers the error. Also, the backtrace obtained by
enabling debug-on-error option as described on
https://www.gnu.org/software/auctex/manual/a
ew " pkg " &")
for my case. It seems that emacs grabs something of the subprocess of
the shell and does not release it until all(?) of subprocess terminate.
Regards,
Ikumi Keita
Emacs : GNU Emacs 25.3.1 (x86_64-unknown-freebsd11.1, GTK+ Version 3.22.15)
of 2017-09-13
Package: 11.
lready asked him and he answered that he is fine with giving over his
copyright, so could you please provide him instructions of necessary
procedure?
Best regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
s in
`preview-dvipng-color-string' choke dvipng on w32 platform because
single quotes are not consumed by w32 shell (cmd.exe).
Could you please test the following patch? (It is for preview.el.in in
the source files, not for preview.el.)
Regards,
Ikumi Keita
diff --git a/preview.el.in b/preview
Hi all,
>>>>> Ikumi Keita writes:
> Hi all,
> As discussed earlier in messages separately, I made out a fix much
> better than the previous proposal. Any opinions are welcome for this
> new proposal.
Since there were no objections, I commited the proposed patches alo
>>>>> Ikumi Keita writes:
>>>>> jfbu writes:
>> 1. the cached format can not be generated
[...]
> I combined the due change to cope with these issues and made up the
> attached patch.
The previous patch doesn't play nice with non-ascii characters
G' with ``dvipng -picky -noghostscript abc\ def\
> ghi.dvi -o "abc\ def\ ghi.prv/tmp14898GFt/prev%03d.png" -D186 ''
> Parser: End of Preview snippet 1 unexpected
> Preview-DviPNG killed: 9 at Sat Jun 2 14:03:07
Regards,
Ikumi Keita
luatex-preamble-cache.gz
Description: apply to
the users will be
able to put their own TeX codes through `TeX-command-extra-options' for
not only "LaTeX" but also "TeX" and "AmSTeX".
The third patch is a fix for preview-latex to support non-ascii file
names in TL2018. The TeX codes that enables preamble c
r not by the keyboard. I searched for a
> configuration but failed, so if anybody found a solution to that
> problem, I would love to hear about it because I could stay with
> evince, which I prefer.
I don't know about this, unfortunately.
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
>>>>> Uwe Brauer writes:
> git://git.savannah.gnu.org/git/auctex.git
> Gives me a time out response.
According to https://git.savannah.gnu.org/cgit/auctex.git, the current
repository is
git://git.savannah.gnu.org/auctex.git
. Try it inste
the default
entries in `TeX-view-program-list-builtin' must also be reviewed and
adapted.
2. If %b expansion is to be modified, it would be better to use
`shell-quote-argument' rather than simply adding double quotes around
it.
Best regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
t; I sincerely apologize for wasting your valuable time on the false
> alarm. Thank you so much for the kind help.
Glad to hear that. Cheers!
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
h (append '("C:/cygwin64/bin" "C:/cygwin64/lib") exec-path))
Maybe these lines still remain in your init.el.
And it seems that kpsewhich binary of cygwin discards ".." from the
output of "kpsewhich --expand-path {.,..}", unlike other OSes.
Best,
Ikumi Keit
Liyu, thank you very much.
>>>>> Liyu Gong <liyu.g...@uky.edu> writes:
> On Sun, Apr 8, 2018 at 8:35 AM, Ikumi Keita <ik...@ikumi.que.jp> wrote:
>>>>>>> Liyu Gong <liyu.g...@uky.edu> writes:
>>> Hi Ikumi,
>>> Sorry, I
dard-output nil) nil
"--expand-brace" "{.,..}")
(call-process "kpsewhich" nil (list standard-output nil) nil
"--expand-brace" "{.,./.}")
2. Could you issue the following command with windows command prompt?
kpsewhich --version
spect that it is ".:..", not ".;..". If this speculation is
correct, then cygwin version of kpsewhich is used at auto detection.
> Yes, I do have a cygwin version TeX distribution. But I just double
> checked. I didn't put th
Hi Liyu,
Could you tell me what the output of
(call-process "kpsewhich" nil (list standard-output nil) nil
"--expand-path" "{.,./.}")
is? If that is ".;./.", we can use it to know the right path
delimiter.
Reg
eX-style-cooked' and it does not use the right
separator.
I'll look into that from now on.
Could you provide the value of the elisp variable
`TeX-kpathsea-path-delimiter' ?
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
t;--expand-path" "{.,..}")
Regards,
Ikumi Keita
>>>>> Liyu Gong <liyu.g...@uky.edu> writes:
> Ahha,
> This is it. I customized the variable TeX-kpathsea-path-delimiter to
> ";", then the aa.tex file can be compiled smoothly.
> Thanks,
> Liyu
> On
matraPDF -reuse-instance"
> - (mode-io-correlate " -forward-search %b %n") " %o")
> + (mode-io-correlate " -forward-search \"%b\" %n") " %o")
> "SumatraPDF")
>("dvips and
> :group 'preview-gs
> :type 'string)
Thank you for your contribution, I incorporated the above change into
the git repository.
Best regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
lem again, it seems that I managed to
find out a solution. The patch listed below resolves the problem on my
environment. Could you please try it?
If it fixes the problem without harming other's environments, I'll
install this in the git repository.
Regards,
Ikumi Keita
diff --git a/tex.el
et a sensible message about not finding any documentation.
Thanks for confirmation. It works just as expectedly. How about you,
Mosè?
Best,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
>>>>> Florent Rougon writes:
> I confirm it fixes the problem, many thanks!
Thanks for confirmation, comitted!
Best,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
Hi Fran, Mosè and all,
>>>>> Ikumi Keita writes:
> Hi ,
>>>>> Mosè Giordano writes:
>> I didn't try the patch, just read it. The idea should be to launch an
>> asynchronous process and show its output, correct?
> Yes.
>> Only one c
t
`TeX-command-buffer' is set every time. Cound you test the patch listed
below? If it fixes your problem, I'll install in the git repository.
I know this patch introduces a small overhead, but I expect that's
negligibly tiny.
Regards,
Ikumi Keita
diff --git a/tex-buf.el b/tex-buf.el
index cc35938
d PATH of the invoked shell differ. If
one of them contains texdoc and other doesn't, calling texdoc might
success or not, accordingly.
Best,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
Hi Jean, sorry for very late reply.
I think that the attached patch will do the job. However it just resets
the "PDF from DVI" setting and doesn't restore it when you again change
the engine to, say, "default".
Is this what you wanted? If so, I'll install this change.
active region in "\hat{}", even when the
prefix C-u is given and the point is placed at the end of the active
region. (This issue is not a regression brought by me. It has been in
AUCTeX since long before.)
Regards,
Ikumi Keita
(defun LaTeX-math-insert (string dollar)
"Insert
Hi Jean,
Please consider customizing the option `LaTeX-insert-into-comments'.
You will get
\documentclass{article}
\begin{document}
\begin{verbatim}
% This is a comment
\def\foo#1{foo}
% another comment
\end{verbatim}
\end{document}
after the option is set to nil.
Regards,
Ikumi Keita
particular issue. However, the relevant codes must be
involved in a lot, lot of different cases, so it might not be valid for
some other cases. I'm not sure currently.
Regards,
Ikumi Keita
diff --git a/latex.el b/latex.el
index 898eec8d..58bf6157 100644
--- a/latex.el
+++ b/latex.el
@@ -699,6 +699,
o, I'll install this change.
> Sorry for late confirmation. Yes your attached patch works for me.
> Indeed it does not restore previous PDF from DVI setting when again
> changing to default engine, but that's fine with me.
Thanks for confirmation, commited. I'll close this bug.
Bye,
Ikumi
plicated and would be somewhat hard to fix.
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
>>>>> Ikumi Keita writes:
> It seems that the conflict between the two versions of AUCTeX still
> remains. It's rather strange. Even if the above two files are left
> behind, the old version of tex.el(c) should not be loaded since they are
> evacuated into si
auctex-info-2 and preview-latex.info. If they remain in
your PC, you might be presented with a bit old info file on some other
day, so I recommend to remove them, as well as to edit the "dir" file to
remove the entries of AUCTeX and preview-latex in it. The "dir" is
located in, probably,
c:/Program Files/GNU Emacs 25.2/share/info/
.
Best,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
>>>>> Ikumi Keita writes:
> Hi Arash,
>>>>> Arash Esbati writes:
>>> What way should we take? To partially revert the change discussed in
>>> [1]? Or to fix the style file each time similar problem occurs? Or
>>> somethig else?
&
>>>>> Arash Esbati writes:
> Ikumi Keita writes:
>> Since nobody opposed Arash's idea for this week, I think it's accepted.
>> Arash, do you commit it for yourself? Or should I do that?
> Change pushed. Best,
of gs needs `preview-pdf-color-string'.
Maybe we should not delete it and instead introduce a user option as a
flag whether to disable the function or not. What do others think?
Regards,
Ikumi Keita
>From 1523e06d83996aa020d842328bff4ad91a894c41 Mon Sep 17 00:00:00 2001
From: Ikumi Keita
Date: Tu
ou thinking that it isn't fruitful to follow up the development of
ghostscript every time incompatible change is introduced?
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
the latter commit, and it already had exactly the
same form as today at that time. I suppose the function has never
changed since then.
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
s kind of recurring API change.
I infer from what you wrote that you don't have intent to fix the
problem for yourself, at least for now. Right?
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
e not limited to the above three.
[1] https://www.ghostscript.com/doc/9.27/History9.htm
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
forwarded to
`TeX-strip-extension'. So the case that NONDIRECTORY is nil is not
relevant.
Best regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
(setq TeX-auto-save t) ; Enable parse on save.
|
|The latter command will make AUCTeX store the parsed information in
| an 'auto' subdirectory in the directory each time the TeX files are
| stored, *note Automatic Local::.
`
Regards,
Ikumi Keita
ster-file'
does not gurantee that it returns absolute path if NONDIRECTORY is nil.
It just states the case when NONDIRECTORY is non-nil, and nothing when
NONDIRECTORY is nil. I think `TeX-master-file' is designed so that
(TeX-master-file) returns "main" in the buffer of main.tex and
"
Hi all,
Now I have some spare time, so I'd like to continue to discuss what we
should do about this issue.
I'm now a bit inclined to take the option (2) and ask gs-devel to
provide suitable Postscript(?) code for preview-latex. What do others
think?
Regards,
Ikumi Keita
>>>>&
>>>>> David Kastrup writes:
> Ikumi Keita writes:
>> Hi all,
>>
>> Now I have some spare time, so I'd like to continue to discuss what we
>> should do about this issue.
>> I'm now a bit inclined to take the option (2) and ask gs-devel to
>>
variable `TeX-style-hook-dialect-weight-alist' is
overwritten for some reason.
Can you first try updating from ELPA again? If that doesn't resolve the
problem, please include the output of M-x TeX-submit-bug-report in your
reply.
Regards,
Ikumi Keita
___
sed in
[1]? Or to fix the style file each time similar problem occurs? Or
somethig else?
Regards,
Ikumi Keita
[1]
https://lists.gnu.org/archive/html/auctex/2018-11/msg00028.html
https://lists.gnu.org/archive/html/auctex/2018-11/msg00029.html
___
b
en from the git repository, after
installing unix-like shell on your windows.
The option 1 consists of removing all the AUCTeX-related files and the
activation codes quoted above from your PC.
Regards,
Ikumi Keita
[1]
https://gitlab.com/vigou3/e
sage. It tells that
"GS_PDF_ProcSet" caused the error and I found that the official
ghostscript document says "We eliminated GS_PDF_ProcSet" in [1].
Best regards,
Ikumi Keita
[1] https://www.ghostscript.com/doc/9.27/History9.htm
/usr/local/texlive/2019/bin/amd64-fre
96:
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35571
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=35696
, which are not yet resolved. Ghostscript 9.27 does not work with
preview-latex when the default face of emacs has non-trivial foreground
color.
Anyway, I close your original bug#35791.
Bes
w.
Maybe your rungs is confused by the two instances of the ghostscript
executables, namely the one under c:/texlive/2019/tlpkg/tlgs and
"mgs.exe".
Regards,
Ikumi Keita
Running `Preview-LaTeX' on `c:/Users/keita/Downloads/_region_' with ``pdflatex
-file-line-error
"\nonsto
cate the position in the buffer to
put the generated image.
If the preview-latex is vital for you, please consider to switch from
MiKTeX to TeXLive: https://tug.org/texlive/
If you have to continue to use MiKTeX, then please ask the developer of
MiKTeX not to alter th
from the user."
> + (TeX-load-style "hyperref")
>(TeX-read-key-val t '(("usepdftitle" ("false")) ("envcountsect")
> ("notheorems") ("noamsthm") ("compress") ("t") ("c")
&g
" error.
Thanks for your report. I have pushed fix to the git repository. I'll
close this bug.
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
on AUCTeX side
helps almost nothing, because it doesn't make MiKTeX to output the key
ingredients like
l.6 \begin{displaymath}
which preview-latex needs in order to locate the position in the latex
document buffer to put the generated image.
Best regards,
Ikumi Keita
>> -Origi
Maybe even simpler "solution" might be to switch from MiKTeX to
TeXLive...
Bye,
Ikumi Keita
>>>>> Bernt Guldbrandtsen writes:
> For what it's worth, activating the error reporting option (discussed at
> https://tex.stackexchange.com/questions/124246/uninfor
uot;^". However, the treatment
of comments of AUCTeX is rather regexp centric and slight in syntax, I
expect this change doesn't bring serious bad side effects at editing
docTeX documents such as filling and indenting.
How do you think about this idea? Any comments are appreciated.
Regards,
ent buffer, which is embedded in my log as the line
l.6 \begin{displaymath}
Due to these two, at least, reasons, preview-latex cannot pick up
necessary information from the log messages. I guess that MikTeX
costomizes the log output format of latex. If this guess is correct, it
would necessary for MikTeX to discard that customize in order to use
preview-latex with MikTeX.
Best regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
maintainer of compilation-mode (emacs-de...@gnu.org, according to the
header of compile.el) to accept file names with spaces.
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
https://www.ctan.org/pkg/luatex85
and install it in your personal texmf tree. Then preview-latex will
work well.
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
, but the number of them can be large instead, e.g., when the
opened LaTeX file uses quite many \usepackage's.)
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
st launching emacs makes no difference, even
if the default value of `TeX-parse-self' is t.
(The parsing of TeX directory does occur as well, but that is
independent of the value of `TeX-parse-self'.)
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-
signed to work with file names with
spaces, so it can work more coherently as a whole if compilation-mode is
aware of such file names as well.
Best regards,
Ikumi Keita
The original bug report follows below:
>>>>> Gustavo Barros writes:
> Currently 'lacheck' and 'chktex' resul
1 - 100 of 388 matches
Mail list logo