Hi Keita
Le 25/05/2018 à 06:59, Ikumi Keita a écrit :
Hi Jean,
jfbu writes:
(b.t.w. I also git cloned the savannah, and
https://git.savannah.gnu.org/cgit/auctex.git has a typo it should be
https://git.savannah.gnu.org/git/auctex.git
)
Ah, sorry. The former URL is for
Hi Jean,
> jfbu writes:
> (b.t.w. I also git cloned the savannah, and
> https://git.savannah.gnu.org/cgit/auctex.git has a typo it should be
> https://git.savannah.gnu.org/git/auctex.git
> )
Ah, sorry. The former URL is for usual web browsers, e.g. firefox.
That gives
Le 24/05/2018 à 20:03, jfbu a écrit :
Le 24/05/2018 à 19:39, jfbu a écrit :
Hi Keita
I have applied your patch (with diff of preview.el.in
transferred to preview.el) to my elpa installed 12.1.0
(later I
saw I had 12.1.1 on another computer and that preview.el
had changed a bit. As the elpa
Le 24/05/2018 à 19:39, jfbu a écrit :
Hi Keita
I have applied your patch (with diff of preview.el.in
transferred to preview.el) to my elpa installed 12.1.0
(later I
saw I had 12.1.1 on another computer and that preview.el
had changed a bit. As the elpa comes with .gitignore
which by bad luck
Hi Keita
I have applied your patch (with diff of preview.el.in
transferred to preview.el) to my elpa installed 12.1.0
(later I
saw I had 12.1.1 on another computer and that preview.el
had changed a bit. As the elpa comes with .gitignore
which by bad luck for me has /preview.el, my initial
Hi Jean and all,
The proposed method, with slight modification explained below, works for
all the cases I tested. Thank you again!
For now, I attach the patch for preview-latex part only so that the
reader can concentrate on the relavant changes.
> jfbu writes:
>>
Hi Keita,
Le 24/05/2018 à 12:44, Ikumi Keita a écrit :
Hi Jean,
Thanks a lot again, the proposed method works on the command line! I'll
implement it in the actual preview-latex code.
By the way, if I remember correctly, filenames with multiple contiguous
spaces are not supported by TeX,
Hi Jean,
Thanks a lot again, the proposed method works on the command line! I'll
implement it in the actual preview-latex code.
By the way, if I remember correctly, filenames with multiple contiguous
spaces are not supported by TeX, aren't they? Standard pdflatex just
fails for such file
Hi Jean,
Thanks a lot again, the proposed method works on the command line! I'll
implement it in the actual preview-latex code.
By the way, if I remember correctly, filenames with multiple contiguous
spaces are not supported by TeX, aren't they? Standard pdflatex just
fails for such file
Hi again (!!!)
better approach using the format with & syntax at bottom
Le 24/05/2018 à 11:52, jfbu a écrit :
Hi Keita
ARRGH filenames with multiple contiguous spaces are a challenge
Because TeX coalesces multiples spaces into a single one.
The ini file can be modified simply but it is
Hi Keita
ARRGH filenames with multiple contiguous spaces are a challenge
Because TeX coalesces multiples spaces into a single one.
The ini file can be modified simply but it is more complicated
for the generation of the format itself.
See at bottom of post.
Le 24/05/2018 à 10:46, jfbu a
Le 24/05/2018 à 10:46, jfbu a écrit :
Notice that when ##1 (i.e. the filename) will be grabbed) the / is of
catcode 0, so ##1 is tokenized accordingly. Which in principle could
perhaps cause an issue \detokenize{aaa/b23} would give aaa/b123
but as / is not legal in filenames in contexts I know
Hi Keita
Le 24/05/2018 à 09:24, Ikumi Keita a écrit :
Hi Jean,
Ikumi Keita writes:
Thank you very much for your all valuable works! I'll test this with
other cases (TL2017, file names with space, on w32 platform) and propose
to commit again.
Unfortunately, it seems
Hi Keita
Le 24/05/2018 à 09:24, Ikumi Keita a écrit :
Hi Jean,
Ikumi Keita writes:
Thank you very much for your all valuable works! I'll test this with
other cases (TL2017, file names with space, on w32 platform) and propose
to commit again.
Unfortunately, it seems
Hi Jean,
> Ikumi Keita writes:
> Thank you very much for your all valuable works! I'll test this with
> other cases (TL2017, file names with space, on w32 platform) and propose
> to commit again.
Unfortunately, it seems that the proposed method using /AUCTEXINPUT does
Hi Jean, thanks a lot, your advice led me to the success!
> jfbu writes:
> Putting altogether :
> 1. We need file prv_testmylátex.ini to be
> \ifx\pdfoutput\undefined\else\let\PREVIEWdump\dump\def\dump{%
> \edef\next{{\catcode`\ 9
Hi Jean, thanks a lot, your advice led me to the success!
> jfbu writes:
> Putting altogether :
> 1. We need file prv_testmylátex.ini to be
> \ifx\pdfoutput\undefined\else\let\PREVIEWdump\dump\def\dump{%
> \edef\next{{\catcode`\ 9
Hi Keita
(still top-posting)
I have an "in principle" solution, although it will look a bit complicated.
First I will explain proof of principle, then concrete implementation.
I hope you can incorporate that in AUCTeX.
STEP I: generation of format.
I will explain first the proof of principle
Le 23/05/2018 à 21:38, jfbu a écrit :
Hi Keita
first-off let me apologize for my numerous posts,
originating from someone like myself who
- does not know preview,
- does not know elisp,
- does not know auctex,
- does not know mylatex.ltx...
- ... and is going to top-post
I appreciate a lot
Hi Keita
first-off let me apologize for my numerous posts,
originating from someone like myself who
- does not know preview,
- does not know elisp,
- does not know auctex,
- does not know mylatex.ltx...
- ... and is going to top-post
I appreciate a lot your detailed explanations,
which avoid
Hi Jean,
> jfbu writes:
> no bothering at all!
>> Perhaps I should give up this particular case (non-ascii file name +
>> preview-latex preamble cache) and commit the patch which fixes other
>> issues.
> surely not!
Thank you!
> What would helped me is to see the exact
Hi Jean,
> jfbu writes:
> no bothering at all!
>> Perhaps I should give up this particular case (non-ascii file name +
>> preview-latex preamble cache) and commit the patch which fixes other
>> issues.
> surely not!
Thank you!
> What would helped me is to see the exact
Ah, I understand better some errors reported by Keita :
Le 23/05/2018 à 15:39, Ikumi Keita a écrit :
(1) Add prv_primárias.ini argument to creat .fmt file.
etex -ini -interaction=nonstopmode -jobname prv_prim\árias "" prv_primárias.ini
Hi again Keita
Le 23/05/2018 à 15:39, Ikumi Keita a écrit :
Hi Jean,
[...]
The literally same commands succeed here as well on xterm. However,
after modifying seemingly to coordinate the actual preview-latex
commands, the latter fails.
(1) Add prv_primárias.ini argument to creat .fmt file.
Hi Keita,
Le 23/05/2018 à 15:39, Ikumi Keita a écrit :
Hi Jean,
jfbu writes:
It is not easy for me to try out any patch to official AUCTeX
(does it have a github repo?)
It has savannah git repository:
https://git.savannah.gnu.org/cgit/auctex.git
Unfortunately, it doesn't
Hi Jean,
> jfbu writes:
> It is not easy for me to try out any patch to official AUCTeX
> (does it have a github repo?)
It has savannah git repository:
https://git.savannah.gnu.org/cgit/auctex.git
Unfortunately, it doesn't on github.
> I gave it a try with a creating a
Hi Ikumi
I had not read your initial message closely enough.
Le 23/05/2018 à 13:34, Ikumi Keita a écrit :
> Thank you very much, Jean,
>
>> jfbu writes:
>>>
>>> On emacs invoked on UTF-8 locale, when I open the test file and type C-c
>>> C-p C-d, answering with y to "Cache
> jfbu writes:
> If filename is containing # or ~ it must have them like \string# and \string~
> in the above
> (I made a brief test with file primárias~.tex and the above with
> \input{primárias\string~.tex} worked on command line)
Thanks, I think we don't have to care
Thank you very much, Jean,
> jfbu writes:
>>
>> On emacs invoked on UTF-8 locale, when I open the test file and type C-c
>> C-p C-d, answering with y to "Cache preamble?", pdflatex succeeds to
>> dump prv_primárias.fmt. However, the run of pdflatex to generate actual
>> image
You can replace \begingroup by { and \endgroup by }
pdflatex -file-line-error
Le 23/05/2018 à 12:46, jfbu a écrit :
Le 23/05/2018 à 12:33, jfbu a écrit :
Hi Keita
Can you please configure AUCTeX to issue this instead (I hope my mailer does
not add linebreaks)
pdflatex -file-line-error
Le 23/05/2018 à 12:33, jfbu a écrit :
Hi Keita
Can you please configure AUCTeX to issue this instead (I hope my mailer does
not add linebreaks)
pdflatex -file-line-error
Hi Keita
Le 23/05/2018 à 12:03, Ikumi Keita a écrit :
Hi Jean and all,
I could sort out most of the problem by a new approach attached with this
message, but am having difficulty with enabling preamble cache on
preview-latex when the document has non-ascii file name. Could you help
me get
Hi Jean and all,
I could sort out most of the problem by a new approach attached with this
message, but am having difficulty with enabling preamble cache on
preview-latex when the document has non-ascii file name. Could you help
me get out of this trouble if possible?
I'm using a test file
Le 21/05/2018 à 11:34, jfbu a écrit :
Le 21/05/2018 à 11:04, jfbu a écrit :
If AUCTeX provides a user-interface for extra TeX commands on
command-line, via some variable, couldn't it check for that
variable being or not nil. If nil, do not use \input, if not
nil, use the \input with whatever
Le 21/05/2018 à 11:04, jfbu a écrit :
If AUCTeX provides a user-interface for extra TeX commands on
command-line, via some variable, couldn't it check for that
variable being or not nil. If nil, do not use \input, if not
nil, use the \input with whatever extra measures are needed
from the fact
Hi Ikumi
Le 18/05/2018 à 08:36, Ikumi Keita a écrit :
Regarding your problem with \message{...}. Perhaps
\unexpanded will help you, as this shows (with April 2018 LaTeX)
\documentclass{article}
\begin{document}
\message{éàù}% gives about 72 macros
\message{\unexpanded{éàù}}% just displays
Hi Jean, thank you very much for clarifying!
First of all, my thought about the behavior of \message was wrong. I
wrote
> The output of \message{...} also changed in TeXLive 2018. If
> non-ascii characters are in \message{...}, they are output in
> tokenized form by default in TL 2018.
before,
Le 17/05/2018 à 10:16, jfbu a écrit :
Perhaps you can use this mouthful
pdflatex -file-line-error -interaction=nonstopmode
"\begingroup\ifdefined\UseRawInputEncoding\UseRawInputEncoding\fi\edef\x{\noexpand\input{\string#éàè\string~\string#.tex}}\expandafter\endgroup\x"
The above uses
Hi Ikumi
thanks a lot for tackling this,
Le 15 mai 2018 à 08:35, Ikumi Keita a écrit :
> Hi all,
>
>> (1) The output of \message{...} also changed in TeXLive 2018. If
>> non-ascii characters are in \message{...}, they are output in tokenized
>> form by default in TL 2018.
Hi all,
> (1) The output of \message{...} also changed in TeXLive 2018. If
> non-ascii characters are in \message{...}, they are output in tokenized
> form by default in TL 2018. This makes partial typset, such as C-c C-r,
> C-c C-s and so on, to fail to recognize the right file name when
Hi Mosè and David,
> David Kastrup writes:
> Mosè Giordano writes:
>> I seem to remember David explained that "\input" was used to make
>> something work (region-compilation?). I looked for this explanation
>> in my inbox but I can't find it, hopefully David
Mosè Giordano writes:
> Hi Keita,
>
> 2018-05-06 8:52 GMT+02:00 Ikumi Keita :
>> Thus I think it is basically unnecessary to adhere using \input and now
>> we can do just
>> latex -interaction=nonstopmode FILENAME
>> instead.
>
> I seem to remember David
Hi Keita,
2018-05-06 8:52 GMT+02:00 Ikumi Keita :
> Thus I think it is basically unnecessary to adhere using \input and now
> we can do just
> latex -interaction=nonstopmode FILENAME
> instead.
I seem to remember David explained that "\input" was used to make
Hi all,
> My current impression is that it would be fine to change
> TeX-command-list so that tex command issued explicitly by C-c C-c, C-c
> C-r and so becomes like
> latex -interaction=nonstopmode FILENAME
> while internal call by preview-latex continues to use \input and
> incorporate
Hi Jean and all,
> jfbu writes:
>> this is to draw attention to this
>> https://tex.stackexchange.com/questions/429869/emacs-auctex-tl-2018-problems-with-non-ascii-characters-in-the-file-name
Thank you for report. It seems that AUCTeX has to be fixed with the
change in
Le 03/05/2018 à 17:56, jfbu a écrit :
Hi,
this is to draw attention to this
https://tex.stackexchange.com/questions/429869/emacs-auctex-tl-2018-problems-with-non-ascii-characters-in-the-file-name
By the way, why does AucTeX use `\input` ? It creates another problem,
which is that the LaTeX
Hi,
this is to draw attention to this
https://tex.stackexchange.com/questions/429869/emacs-auctex-tl-2018-problems-with-non-ascii-characters-in-the-file-name
By the way, why does AucTeX use `\input` ? It creates another problem,
which is that the LaTeX version banner (not the engine banner, I
48 matches
Mail list logo