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
showin
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
showin
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
showin
given escape syntax in texinfo-mode buffer, which should be
>> avoided in latex-mode buffer.
In other words, the function TeX-search-syntax-table should initialize
the variable every time if a single syntax table is to be shared between
all the buffers of dirrerent modes.
Regards,
"
(char-to-string (with-syntax-table foo (char-syntax ?\(
=> " "
(let ((foo (make-char-table 'syntax-table nil)))
(set-char-table-parent foo (make-char-table 'syntax-table nil))
(char-to-string (with-syntax-table foo (char-syntax ?\(
=> " &
Remember to cover the basics. Including a minimal LaTeX example
file exhibiting the problem might help.
When editing Japanese LaTeX document encoded in shift-jis, preview-latex
sometimes fails to place images on the right place (wrong place or no
image at all). Such cases are often accompanied
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
showin
;; (What about using `imenu--index-alist'?)
;; FIXME: Support multi-file documents.
==
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. In addition check if the bug is reproducable with an
up-to-date version of AUCTeX. So please upgrade to the version
av
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
av
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
av
on 'zmacs-activate-region))
...
... )
;;; Special support for GNU Emacs
(unless (featurep 'xemacs)
...
(defun TeX-activate-region ()
(setq deactivate-mark nil)
(activate-mark))
...
... )
-------
Regards,
Ikumi K
ones.
However, if you are afraid of undiscovered incompatibilities, I don't
adhere to changing `TeX-activate-region'. In that case, I hope the
attached patch which just changes `push-mark' to `set-mark' in
`TeX-insert-dollar' would be helpful.
Regards,
Ikumi Keita
diff --git
> 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
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
av
fter-load-alist'.
The advices are added through 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
t preview-latex uses the value of
`TeX-japanese-process-output-coding-system', but it is not sufficient to
rely on such constant value. In fact the default value of
`TeX-japanese-process-output-coding-system' was changed to nil
recently.) Even my patch "preview-latex-fix" i
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
av
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
av
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.
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@gn
st' contains lines
;; \LoadClass[]{}[]
("Load\\(Class\\)\\(\\[\\([^#\\.%]*?\\)\\]\\)?{\\([^#\\.\n\r]+?\\)}"
(3 4 1) LaTeX-auto-style)
;; \LoadClassWithOptions{}[]
("Load\\(Class\\)WithOptions\\(\\){\\([^#\\.\n\r]+?\\)}"
(2 3 1) LaTeX-auto-sty
%% 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).
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
>> 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
+++
ge?
OK, the patch is attached at the last of this mail.
> Bye,
> 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
?& (char-after))
(not (TeX-escaped-p)))
(current-column)
(or any-col
beg-col
Using `TeX-escaped-p' might be overkilling since we allow loose usages of
(looking-at &quo
Hi all,
> Alas, `wholenump' is not available in XEmacs.
In XEmacs, `natnump' is available. It is available in GNU Emacs, too,
and already used in latex.el and tex-buf.el.
Bye,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@
; is
negative or not. I 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
__
e 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
___
bug-auctex
eX-add-symbols '("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
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
http://lists.gnu.org/
takes care of that. With
this change, preview-latex 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 Kei
in batch mode.
Such tests 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 "preview-sectio
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
e beginning of a line. (I don't know what is the correct
"column" 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
+++
t.)
> I don't know, sorry.
No problem, thank you. Then I will add 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
Hi all,
Now I propose to apply the attached fix. This doesn't change the action
of "%b" and "%n". If no objection, I'll commit it soon.
Bye,
Ikumi Keita
diff --git a/preview.el.in b/preview.el.in
--- a/preview.el.in
+++ b/preview.el.in
@@ -1622,11 +1622,8 @@
Sorry, the previous patch contains a spurious ")" in it. Please dismiss
it and use the attached one instead.
Bye,
Ikumi Keita
diff --git a/preview.el.in b/preview.el.in
--- a/preview.el.in
+++ b/preview.el.in
@@ -1622,11 +1622,8 @@
(unless (eq preview-state 'disabled)
e 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/manua
on 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 @@
(defun LaTeX-env
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 writes:
> Preview-latex fails if the length of the file name or the
ply 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
r 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
ment. We can get rid of
> 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
wer is opened in the
background, the shell is free and the prompt readily appears, without
waiting for the viewer to be closed.
It doesn't help to change the part
(concat "texdoc --view " pkg)
in `TeX-documentation-texdoc' to
(concat "exec texdoc --view " pkg "
fied so that it gets quoted, 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;SumatraPDF -reuse-instance"
> - (mode-io-correlate " -forward-search %b %n") " %o")
> + (mode-io-correlate " -forward-search \"%b\" %n") " %o")
> "SumatraPDF")
>("dvips and start&
ersion dependency exists, since the
newest version 12.1.1 works without problem on my side.
Additional information might be helpful, e.g.
- The output of M-x TeX-submit-bug-report
- The content of the process buffer (displayed by C-c C-l)
- The path name of di
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 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 Sun, Apr 8, 2018 at 12
..", 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 the cygwin path in windows PATH, or in emacs
> exec-path.
Hmm.
from the output, even when the current
directory is the root directory. When the result doesn't contain
neither ":" nor ";", AUCTeX cannot know the right path delimiter.
Sorry, let me think for for a while.
Regards,
Ikumi Keita
>>
>> On Sun, Apr 8, 2018 at 1
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.
Regards,
Ikumi Kei
>> neither ":" nor ";", AUCTeX cannot know the right path delimiter.
>> Sorry, let me think for for a while.
> Perhaps related to the security settings of TeXlive?
Possibly. But I cannot find out such description in the kpathsea info
file yet.
Regards,
Ikumi Kei
"--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
Best regards,
Ikumi Keita
Liyu, thank you very much.
>>>>> Liyu Gong writes:
> On Sun, Apr 8, 2018 at 8:35 AM, Ikumi Keita wrote:
>>>>>>> Liyu Gong writes:
>>> Hi Ikumi,
>>> Sorry, I just got up. The results is the same: a dot followed with a
>>>
win64/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 Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
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
As a minor additional improvement, 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 T
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
bc def ghi.log".
Therefore dvipng fails:
> TeX Output exited as expected with code 1 at Sat Jun 2 14:03:07
> Running `Preview-DviPNG' with ``dvipng -picky -noghostscript abc\ def\
> ghi.dvi -o "abc\ def\ ghi.prv/tmp14898GFt/prev%03d.png" -D186 ''
> Parser:
>>>>> 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 character
ticed during test runs that single quotes 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,
Ikum
Hi Jean and all,
Thank you for confirmation. I think this change is small and rather
safe, so I'll commit it as soon as I finish some documentation.
Regards,
Ikumi Keita
>>>>> jfbu writes:
>> . They don't have quotes around %m except `preview-dvipng-command
---
(I am talking about the Japanese characters in the contents of the dvi
file, not in the file name). This is because (u)platex outputs dvi
files with slightly extented format and most of the dviwares including
dvipng cannot process this extended dvi. But anyway, the fallback run
of Preview-Dvips takes care of that failure, so the functionality of
preview-latex is kept.
Best regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
enerate-preview
I already 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
>>>>> Ikumi Keita writes:
> If other problems aren't found, I'll commit this in several days.
Done. The copyright assignment from Jean is in due process.
Best,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@g
nly done by the toolbar 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
s'."
> :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
problem 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
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
r directory" which the shell outputs.
(2) the values of `exec-path' and 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 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
t sure that
`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
>>>>> 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 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
the 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)
"I
>>>>> Todor Tsankov writes:
> The new function works for me. Thanks for the quick reaction and for the
> fix!
Thanks for confirmation. I installed the fix in the git repository.
Best,
Ikumi Keita
___
bug-auctex mailing li
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
e this 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
If so, 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 t
27;s rather complicated 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
d.
What do you mean by "Evince server"? If you are talking about the
"server" in `TeX-source-correlate-start-server', then it refers to
"emacs server", which accepts connection requests from emacsclient.
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
p anymore.
Are there anyone out there who knows dbus well and is willing to find
out what's going on?
Regards,
Ikumi Keita
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
Hi Cédric,
>>>>> Ikumi Keita writes:
>> I was using a script I found many years ago on the web but it stopped
>> working. I therefore changed to another script,
>> https://gist.github.com/dandrake/2297447, which didn't work either. It
>> gives me
>>>>> Cédric Martínez Campos writes:
> Solved. It seems some Ubuntu package installed Evince through Flatpak,
> which does not communicate with D-Bus.
> Thank you very much Ikumi for your insight.
You're welcome. I'll
e image in
the latex document 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
sed below, 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
>>
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/un
etween the first and second "^". 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
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
_
revert the change discussed 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
ions from the user."
> + (TeX-load-style "hyperref")
>(TeX-read-key-val t '(("usepdftitle" ("false")) ("envcountsect")
> ("notheorems") ("noamsthm") ("compress") ("t") ("c
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
,
auctex-info-1, 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:
> 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 site
>>>>> 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?
&
1 - 100 of 483 matches
Mail list logo
