Stefan Monnier writes:
Hi Stefan,
> FWIW, the `elpa-admin.el` code needs to do something similar and it
> asks Git a bit more directly (i.e. with the generating the diff):
>
>(elpaa--call
> (current-buffer)
> "git" "log" "-n1" "--oneline" "--no-pat
branch: main
commit b582fc13c6831193eab9b6838b7ceee2d2bb227e
Author: Tassilo Horn
Commit: Tassilo Horn
Add tex-site.el and doc/dir to .gitignore
---
.gitignore | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/.gitignore b/.gitignore
index ac530538..f68e38a5 100644
--- a
branch: main
commit 68bf115399403f41556f375e0a5c1c15ae78a787
Author: Tassilo Horn
Commit: Tassilo Horn
Delete top-level dir file
---
dir | 25 -
1 file changed, 25 deletions(-)
diff --git a/dir b/dir
deleted file mode 100644
index 0b85f603..
--- a/dir
+++ /d
> 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, which opens certain fil
>>> "PN" == Paul Nelson writes:
> 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.
Great, I just tested it, I will clone your repository by the way why to
you call i
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
Description: Binary da
>>> "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 the
> 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 for
>>> "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 functionalit
> 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 is
>>> "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 17:
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 func
> Alright, I've had some time to do some fiddling. In the auctex
> repository, there's some new main branch (based on externals/auctex)
> where I've changed how AUCTEXVERSION and AUCTEXDATE are determined.
> Instead of looking at specially formatted lines in ChangeLog, it just
> looks at the git d
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 functionality from
AUCTeX.
For some people, t
Uwe Brauer writes:
> I most likely did not get the point. I just saw the mail concerning
> Tassilos «mega» commit, which created a new branch called main.
It's just 2 small changes to GNUMakefile. However, it's based on the
externals/auctex branch of elpa which we didn't have in our repository
Stefan Monnier writes:
Hi Stefan,
> Well, not for `make auctex.tar` where it's built from whatever is HEAD
> in `packages/auctex`. But in `elpa.gnu.git` HEAD is indeed pointing
> to `externals/`.
Alright, I've had some time to do some fiddling. In the auctex
repository, there's some new main
Hi
I most likely did not get the point. I just saw the mail concerning
Tassilos «mega» commit, which created a new branch called main.
So where will the main development take place either on
1. The new main branch?
2. Or the old master branch?
Thanks
Uwe Braure
--
I strongly cond
18 matches
Mail list logo
