Hi
A couple of days ago Paul posted about a new (at least for me) package,
that allows via latexmk to actualise the generated pdf file, if the
corresponding LateX source file is saved.
I tested it in the last days and like it quite a bit. Preview.el is also
part of auctex, so the question is,
Hi Paul,
Paul Nelson writes:
> I thought I'd share a package I'm hoping to eventually submit to ELPA.
> It may be topical in view of the recent discussion here concerning
> latexmk. I would appreciate any advice or suggestions, particularly
> on ways that I could better leverage existing
> Great, I just tested it, I will clone your repository by the way why to
> you call it https://github.com/ultronozm/tex-continuous.el ?? Couldn't
> you drop the .el?
>
> The .el sometimes causes problems when opening the directory in dired
> mode I use the extview package, w
y by the way why to
you call it https://github.com/ultronozm/tex-continuous.el ?? Couldn't
you drop the .el?
The .el sometimes causes problems when opening the directory in dired
mode I use the extview package, which opens certain files in dired with
external programs.
> I might also st
The attached version (also updated at the github link) seems to work
for me with a custom build directory specified by TeX-output-dir. Let
me know if you run into any issues.
I might also start using this "build directory" approach -- thanks for the tip!
tex-continuous.el
Descripti
>>> "UB" == Uwe Brauer writes:
>>> "PN" == Paul Nelson writes:
>>> But more than a year ago Al Haji-Ali provided a functionality which
>>> allows to configure a build directory in which all files dwell that are
>>> generated by a LaTeX compilation. So TeX-view looks then there and not
>>> in
> Thanks for you quick reply. It seems that the code was added already 3
> years ago. I recall a series of patches and test in which I
> participated (and I forgot some details).
> According to the documentation, finally the behavior is controlled by
> setting the variable TeX-output-dir
I
>>> "PN" == Paul Nelson writes:
>> But more than a year ago Al Haji-Ali provided a functionality which
>> allows to configure a build directory in which all files dwell that are
>> generated by a LaTeX compilation. So TeX-view looks then there and not
>> in the main directory if that
> But more than a year ago Al Haji-Ali provided a functionality which
> allows to configure a build directory in which all files dwell that are
> generated by a LaTeX compilation. So TeX-view looks then there and not
> in the main directory if that functionality is enabled.
>
>
> So the question
>>> "PN" == Paul Nelson writes:
> The process output is contained in a buffer name *pvc-your-file-name*.
> Could you share what that says?
It says it compiles and I think I know what the problem is.
Have a look at the directory in question
,
|
| -rw-r--r-- 1 oub oub 9,9K abr 20
The process output is contained in a buffer name *pvc-your-file-name*.
Could you share what that says?
>>> "PN" == Paul Nelson writes:
> I thought I'd share a package I'm hoping to eventually submit to ELPA.
> It may be topical in view of the recent discussion here concerning
> latexmk. I would appreciate any advice or suggestions, particularly
> on ways that I could better leverage existing
with AUCTeX's error handling, which
also seems to be the case for the preliminary latexmk support recently
added to master.
See attached, or https://github.com/ultronozm/tex-continuous.el.
Thanks, best,
Paul
tex-continuous.el
Description: Binary data
13 matches
Mail list logo
