too old.
Huh. I thought the idea behind snap packages was that they packaged
their library dependencies or something in order not to rely on the host
system details as much. Maybe there is a particular way in which one
needs to call the binary or set up its environment?
--
David Kastrup
))
(setenv "PATH" path)))
I call it as
M-x TeXlive RET
and it looks up the TeXlive versions (under /usr/local/texlive) that
have binaries installed and then asks which year to use, defaulting to
the newest. In case multiple architectures are installed (I had 32bit
and 64bit executables in parallel at some point of time) it also asks
for the architecture.
--
David Kastrup
Jan Braun writes:
>
> \newpage
> %\end{macrocode}
> % @
> %\begin{macrocode}
>
> I wrote myself a tiny lisp function, but this has still some bugs,
> which I wasn’t able to fix yet :-(
You can try
C-a C-o % C-u C-c ]
as a first approximation.
--
David Kastrup
branch: master
commit 2d0fdebac0ec12676545dd4197171575e7489f56
Author: David Kastrup
Commit: David Kastrup
Preserve braces after @TeX and similar macros.
---
doc/macros.texi | 30 +++---
1 file changed, 15 insertions(+), 15 deletions(-)
diff --git a/doc/macros.texi
Arash Esbati writes:
> David Kastrup writes:
>
>> Those were defensive changes intended to make fewer assumptions. I'd be
>> surprised if they didn't work with older Texinfo variants, but surprises
>> are not unheard of...
>
> I tried it with texinfo.tex 2021-04-2
Arash Esbati writes:
> David Kastrup writes:
>
>> That appears to be a different problem. Maybe
>
> Thanks, the last change works as expected. What do you think, is your
> suggestion safe enough to push? Otherwise, I will try to test with an
> older texinfo.tex before
Arash Esbati writes:
> David Kastrup writes:
>
>> Without too much of a clue and research, this appears to do the trick
>> for me:
>
> This is what I get:
>
> (./auctex.toc [-1]
> ! Missing control sequence inserted.
>
> @inaccessible
Arash Esbati writes:
> David Kastrup writes:
>
>> It needs to be written AUC@TeX{} . Maybe the toc code errouneously
>> strips the braces? ... Oops. In doc/macros.texi, we have
>>
>> \global\let\savedTeX\TeX
>> \gdef\TeX#1{\savedTeX#1}
>>
>>
e braces.
It would inhibit kerning after @TeX{}, like when writing @TeX{}O, but I
don't think that should be a relevant problem. Worth a try.
--
David Kastrup
David Kastrup writes:
>> The list-strings variable is let-bound around the complete defconst
>> LaTeX-symbols-toolbar-switch-contents. I guess it should become
>> (quote ("foo" "bar" "baz")) instead of (quote \, list-strings). Stefan,
>>
ess it should become
> (quote ("foo" "bar" "baz")) instead of (quote \, list-strings). Stefan,
> what's the issue here?
This looks like it should rather rely on lexical-binding being t and
write
:help (lambda ( _ignore)
(concat "Turn "
(if LaTeX-symbols-toolbar-visible-flag "off " "on ")
"the toolbar of LaTeX symbols (current class: "
(nth (1- LaTeX-symbols-active-menuitem)
list-strings)
")")))
--
David Kastrup
Uwe Brauer writes:
>>>> "DK" == David Kastrup writes:
>
>> Uwe Brauer writes:
>>> Hi
>>>
>>> A colleague of mine still sticks with xemacs21.4 and auctex 11.84.
>>>
>>>
>>> Now she is annoyed that every ti
Or you can just use
M-x customize-variable RET TeX-master RET
and have the meaning of the various settings explained.
--
David Kastrup
that I have renamed.
In Git it should work (if you _combine_ renaming a file with changing
its contents in a single commit, git blame may need additional options
to track this). In Hg it likely depends on whether you renamed using
the version control system or outside of it.
> Maybe this is impossible.
Unlikely...
--
David Kastrup
in other version control systems so that they
can track the ancestry of material, and moving material between files or
splitting or merging files generally leads to a loss of significant
amounts of information.
In Git you do not need to worry about losing that information because
Git does not store it in the first place.
--
David Kastrup
Ikumi Keita writes:
> Hi David and Tassilo,
>
>>>>>> David Kastrup writes:
>> As a note aside: we are using Git as version control system these days.
>> Git doesn't maintain change histories in the first place but computes
>> them on the fly when calli
version control system these days.
Git doesn't maintain change histories in the first place but computes
them on the fly when calling "git blame" or similar. It has various
options on how thoroughly it will track content moving across files.
"Losing" commit history is quite harder than you make it appear here.
So that particular point should not really be a consideration.
--
David Kastrup
pend LaTeX-math-list LaTeX-math-default))
>
> Or am I missing something?
Performance and memory churn? Appending two lists has to create a copy
of the first list.
--
David Kastrup
normal-normal-normal-*-15-*-*-*-d-0-iso10646-1 (#xDD12)
Character code properties: customize what to show
name: VARIATION SELECTOR-16
general-category: Mn (Mark, Nonspacing)
decomposition: (65039) ('️')
and that has no place in Elisp syntax when encountered on its own. If
you cannot get your input method to refrain from that insertion, instead
of ?☹ you could just write 9785 .
--
David Kastrup
es this point.
As I read the Elisp reference, it is pretty clear. What other
interpretation do you read into the text?
--
David Kastrup
Tassilo Horn writes:
> David Kastrup writes:
>
>>>> Tasillo, I would be grateful if you can pull those changes when you
>>>> get a chance.
>>>
>>> Done so, although I've had to delete and recreate the branch because
>>> apparen
there. And force-pushing on master at least is not something one should
do ever.
--
David Kastrup
Uwe Brauer writes:
>>>> "DK" == David Kastrup writes:
>
>> Uwe Brauer writes:
>>>> Pushed. Oops, sorry, I overlooked that new commits had come in. A non
>>>> fast-forward merge commit was produced on savannah. Not good...
>&
eloper, but certainly not on the reader.
--
David Kastrup
Arash Esbati writes:
> David Kastrup writes:
>
>> Arash Esbati writes:
>>
>>> I'm not sure but the entire (when (fboundp 'built-in-face-specifiers)
>>> clause is XEmacs related, right? Can someone with XEmacs installed on
>>> HD confirm?
h
+
+ * font-latex.el: Updated to V0.504 (Oct 20 97)
+
+ * bib-cite.el: Updated to 3.04 (Aug 25 97)
+
+ * hilit-LaTeX.el: Updated to V1.17 (Sep 06 95)
At this date, Emacs did not yet have its Emacs 21 display engine
released unless I am mistaken.
So pretty sure that in the context of XEmacs non-support this code
should be fine to remove.
--
David Kastrup
athtools package load amsmath? If it does, then maybe AUCTeX
should have an appropriate style file?
--
David Kastrup
else did while
retaining the braces?
Of course most of the time I try to deflect blame, it turns out I was
the culprit.
Also I don't quite know whether or not "preamble caching" in the form of
mylatex.ltx use could be relevant.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
Ikumi Keita writes:
>>>>>> David Kastrup writes:
>>>> The test would be something like
>>>
>>>> /GS_PDF_ProcSet where { pop [put old code here] } if
>>>
>>> Do you mean that the patch listed below should work?
>
Ikumi Keita writes:
>>>>>> David Kastrup writes:
>> I don't think that the drawback is necessary: in contrast to a working
>> DELAYBIND, it is easy to test for existence of the PDF dictionary at
>> runtime and use it if available.
>
>> The test would
lor of the generated images
> will just be white and no longer match with Emacs.
I don't think that the drawback is necessary: in contrast to a working
DELAYBIND, it is easy to test for existence of the PDF dictionary at
runtime and use it if available.
The test would be something like
/GS_PDF_Proc
Ikumi Keita writes:
> Hi David,
>
>>>>>> David Kastrup writes:
>> I'll probably pitch in from here (if nobody else does) and write code
>> that checks for the availability of any of these features and uses them.
>
> Do you have a plan to make a progr
ris, there is a possibility that we ask you (or the Ghostscript
> development team) to agree to transfer the copyright of the above
> PostScript code of several lines to Free Software Foundation. Are you
> fine to agree if that really happens?
>
> To project admin of AUCTeX (especially
of these features and uses them.
What will be the result of trying to use the broken DELAYBIND? Can I
check/use it in a manner where the worst that will happen is, well,
nothing?
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
Ikumi Keita writes:
> [ Recipient lists are trimmed. ]
>
>>>>>> David Kastrup writes:
>>> The links to the old archives of AUCTeX-related ML listed on
>>> https://www.gnu.org/software/auctex/mailing-lists.html
>>> are all dead (dir.
Ikumi Keita writes:
> Hi David,
>
>>>>>> David Kastrup writes:
>> Ikumi Keita writes:
>>> I hope that David comments on this issue. In particular, I'd like to
>>> know, or to know to how to judge, whether "the initial colors set up
>
the foreground and background colors
> are reflected in the outcome of preview-latex.
>
> However, these two lines in preview.sty (actually in preview.dtx) were
> commmented out at this commit:
> --
> 5dc76f79d0fff44794262037b93f0533af78f805
&
t be worth thinking about is linking to
>> (the latest?) news on AUCTeX's web page.
>
> That would be helpful.
AUCTeX's web page is not really a lot to write home about in its current
state, really. Linking to AUCTeX's news items might be a bit of
improvement.
--
David Kastrup
_
much success with that
approach for other software. The only thing that might be worth
thinking about is linking to (the latest?) news on AUCTeX's web page.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
ssages are _absolutely_ not the place for collecting
release-relevant information. They are supposed to describe the
particular changes affected by a particular commit, not changes by some
unspecific series of commits preceding it.
--
David Kastrup
___
auct
t; think?
Definitely worth a try, mentioning that this has to go through pdf2dsc .
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
-error-no-select)
(previous-error-no-select): Move from compile.el.
and in 2005 we certainly would not have wanted to depend on code
introduced as recently as 2004.
So the answer is very likely "historical".
--
David Kastrup
___
auctex-de
Ikumi Keita writes:
> Hi David,
>
>>>>>> David Kastrup writes:
>
>> Uh, preview-latex already _had_ code for doing that. Doesn't it work?
>
> No, the previous code excluded raw 8-bit bytes which already existed in
> the output of latex. It only proces
equences of control characters such as ^^I are left untouched.
preview.el.in: (preview--convert-^^ab
preview.el.in:(defun preview--convert-^^ab (string)
preview.el.in: "Convert ^^ sequences in STRING to raw 8bit.
preview.el.in:Sequences of control character
you get an Emacs installed and do
M-x package-list-packages RET
you should be able to find AUCTeX in that list and install it (using "i"
I think).
I don't think you should be experiencing problems under Windows; be sure
to report back either way.
--
David Kastrup
___
David Kastrup <d...@gnu.org> writes:
> Ikumi Keita <ik...@ikumi.que.jp> writes:
>
>> Hi Mosè and all,
>>
>>>>>>> Mosè Giordano <m...@gnu.org> writes:
>>> sorry for the late reply, these days I'm getting all @gnu.org emails
>&g
m of GNU mail list suffers severe
> trouble these days. No mails since Nov 30 are listed on
> https://lists.gnu.org/archive/html/auctex/
> https://lists.gnu.org/archive/html/auctex-devel/
> https://lists.gnu.org/archive/html/bug-auctex/
> at the time of writing this message.
>
>>
. There are three ways that we
>> can take.
>>
>> (1) Commit my pending patch proposed in
>> https://lists.gnu.org/archive/html/auctex-devel/2017-11/msg00030.html
>
> Braces + comma should be fine.
Unless there are directories co
t; Are the braces necessary?
Otherwise comma will not be special and could be part of a directory
name.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
Ikumi Keita <ik...@ikumi.que.jp> writes:
>>>>>> David Kastrup <d...@gnu.org> writes:
>
>> You know, it is not prohibited to actually test out such things.
>
>> dak@lola:/usr/local/tmp/lilypond$ kpsewhich --progname=latex --expand-path
>> &
Copyright 2017 Karl Berry & Olaf Weber.
License LGPLv2.1+: GNU Lesser GPL version 2.1 or later
<http://gnu.org/licenses/lgpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
What are you trying to fix here? T
David Kastrup <d...@gnu.org> writes:
> David Kastrup <d...@gnu.org> writes:
>
>>> (defun delete-dups (list)
>>> "Destructively remove `equal' duplicates from LIST.
>>> Store the result in LIST and return it. LIST must be a proper list.
>&g
David Kastrup <d...@gnu.org> writes:
>> (defun delete-dups (list)
>> "Destructively remove `equal' duplicates from LIST.
>> Store the result in LIST and return it. LIST must be a proper list.
>> Of several `equal' occurrences of an element in LIST, the f
Arash Esbati <ar...@gnu.org> writes:
> Mosè Giordano <m...@gnu.org> writes:
>
>> 2017-11-10 18:42 GMT+01:00 David Kastrup <d...@gnu.org>:
>>> Uwe Brauer <o...@mat.ucm.es> writes:
>>>
>>>> Ok, what's about styles? Could those
XEmacs to make unambiguously clear that the
AUCTeX developers are not responsible for working on an XEmacs version
any more.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
---
commit 837d590008c1dd4e92ffbce15008efb761d11f7c
Author: David Kastrup <d...@gnu.org>
Date: Mon Nov 6 23:58:23 2017 +0100
Remove use of .runandhide operator
Ghostscript bug 698680
<https://bugs.ghostscript.com/show_bug.cgi?id=698680> has been caused
by the removal of the .runandhide operat
TeX/LaTeX is also code, so why would
> not the same expectation apply? I apologise if I have misunderstood.
Well, your philosophy did not manage to prevent preview-latex.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
t" and "letting it take over focus" are two different things.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
ro*\footnote[{[]}][#1{}]|
> % \end{quote}
>
> I'm not a preview user, but I would have expected that \footnote comes
> last. Can someone confirms this?
>
> % \begin{quote}
> % |\PreviewMacro*[{[]}][#1{}]\footnote|
> % \end{quote}
The content of prfootnote.def appear
ly use them and get all the benefits.
>
> WDYT?
I think that the AUCTeX manual should start right away with suggesting
to _individually_ enable TeX-parse-self. Which it does as far as I
remember.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
distributed
packages are usually activated automatically when installed via the
package system). I don't think that AUCTeX documentation is the place
to suggest switching to Emacs. Nor should we specifically recommend the
use of unmaintained packages like X-Symbol.
--
David Kastrup
Uwe Brauer <o...@mat.ucm.es> writes:
[...]
Uwe's assignment is finally registered for Emacs with date 2016-8-22.
--
David Kastrup
signature.asc
Description: PGP signature
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.g
Uwe Brauer <o...@mat.ucm.es> writes:
> Hi
>
> Any news with my copyright assignment?
No. Have you received your copy signed by the FSF clerk? As long as
that is not the case, the assignment has not been processed anyway.
--
accessible list ends
with 2016-8-23 (about a week ago) so there might have been some work
queue or vacation that has interfered with the updates to current date.
Did you receive notice about the completion? If so, it usually takes
half a day until the results carry into the official lis
know how to proceed?
Wait some more days. For one thing: if you wrote yesterday, yesterday
was Sunday. Which is not a work day even in the U.S. (and Donald is an
actual employee). And Monday is not half over in the U.S. since there
is a timezone difference. And if he is
Uwe Brauer <o...@mat.ucm.es> writes:
>> On 28 Aug 2016, at 23:33, David Kastrup <d...@gnu.org> wrote:
>>
>> Of course, the circle of GNU maintainers is not exactly small, but
>> decidedly smaller than that of all GNU contributors, and many of those
&g
se, the circle of GNU maintainers is not exactly small, but
decidedly smaller than that of all GNU contributors, and many of those
maintainers are so because of being in a position of trust by several
others working on GNU. It's a reasonable compromise.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
Uwe Brauer <o...@mat.ucm.es> writes:
>>>> "David" == David Kastrup <d...@gnu.org> writes:
>
>> Uwe Brauer <o...@mat.ucm.es> writes:
>>> Hi
>>>
>>> I just received the copyright papers. It seems that
nderstand "AUCTeX/GNU Emacs".
What is the exact project listed in your copy of the PDF?
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
Mosè Giordano <m...@gnu.org> writes:
> 2016-07-17 19:28 GMT+02:00 David Kastrup <d...@gnu.org>:
>> Mosè Giordano <m...@gnu.org> writes:
>>
>>> It looks overall good to me, but note that error messages *do not* end
>>> with a period (see `error`'s
that error messages start with a capital
letter but *do not* end with a period. Please follow this convention
for the sake of consistency.
Note: (error "%s" VALUE) makes the message VALUE without
interpreting format characters like ‘%’, ‘`’, and ‘'’.
You don't want to ha
; "^(\\(def\\(alias\\|const\\|macro\\|subst\\|un\\|var\\)\\)\\>")
>
> Ok, fine.
>
>> Do you have any specific concern about using `eval-when-compile' here?
>
> I have the impression that currently AUCTeX doesn't require to be
> compiled. My understanding is that with this change compilation would
> become practically mandatory (at least in order to exploit this
> feature), is it correct?
No. It will interpret just fine, only slower. Which is basically the
expectation for loading uncompiled code anyway, though usually most of
the savings from compilation are expected more on run time than load
time.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
uld not couple the tests in that manner. Just do
\ifx\commondummies\undefined \else
[Fix \commondummies]
\fi
\ifx\definedummies\undefined \else
[Fix \definedummies]
\fi
It keeps the tests connected to the actual code and has fewer implied
assumptions.
--
David Kastrup
; Well, and in the concrete case, if one character in the ChangeLog
> shows up as \xxx or a box, I don't consider that a drama. :-)
ChangeLog is strictly a developer resource. No XEmacs developer will be
actively using XEmacs 21.4 no-mule. Trying to avoid utf-8 here is
nonsensical in my book.
--
e at least 6 AUCTeX
users all in all.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
nk that both memq and member would
>> work (with the former probably being a bit faster than the latter).
>
> I wasn't sure if two integers of the same value are always identical.
Emacs: yes so far. Lisp: not necessarily. That's why eql exists in the
first place.
I prefer pretend
shed. Thu Mar 3 05:54:48 2016
>
> I don't see any reason behind the "t" setting here; I've practically
> never wanted to insert a literal quote character in Polish TeX files.
So? In verbatim and/or code excerpts it's actually a rather likely
thing to insert.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
git-pull(1) for details. `
>
> Ok I can clone again, but I would love to know what is going on [1]
Whatever you did (git reflog should give you a good idea), you probably
can get back to normal using
git checkout master
--
David Kastrup
___
away from the master branch to an isolated commit rather
than a local branch head. And then to another isolated commit rather
than a local branch head.
Probably a bad use of "git checkout".
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
to.
Try
git diff
to see the changes you made to .gitignore without committing.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
displayed.
>
> I am puzzled since I think a
> (require 'my-change-prettify-list)
> would load the elc version.
>
> Any explanations?
Using desktop.el?
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
Uwe Brauer <o...@mat.ucm.es> writes:
>>>> "David" == David Kastrup <d...@gnu.org> writes:
>
>> Uwe Brauer <o...@mat.ucm.es> writes:
>>>>>> "Tassilo" == Tassilo Horn <t...@gnu.org> writes:
>>>
>>
Z" . ?\u2124)))
> | (add-to-list 'tex--prettify-symbols-alist el))
> |
> |
> |
> | (provide 'my-change-prettify-list)
> `
> again: \setR works, \setQ does not.
First try not to use Emacs' built-in TeX mode at the same time as using
AUCTeX, or any further analysis is likely a waste of time.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
. ?\u211d)
> ("\\setQ" . ?\u211A)
> ("\\setC" . ?\u2102)
> ("\\quad" . ?␣)
> ("\\qquad" . ?\u29e2)
> ("\\varrho" . ?ϱ)
> ("\\setZ" . ?\u2124)))
> (add-to-li
; bug, if exists, has anything to do with AUCTeX).
It very much depends on what "But I also have set" is supposed to mean.
If you add to LaTeX-mode-hook, of course this does not affect any
buffers which are already in LaTeX-mode (for example by having loaded
the desktop before setting up LaTeX-mode-hook).
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
.
Uh, correct? That's an error anyway. Are you talking about x^{y^z}
instead?
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
is recent enough?
I have my doubts that Tassilo would call an Emacs version from 12 years
ago very, very recent.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
(X)Emacs supposed to find this executable?
If you started (X)Emacs from the terminal application, yes. If you
didn't, it depends on how the environments of (X)Emacs and the terminal
application differ in their setup.
--
David Kastrup
___
auctex-devel
mail box.
If your user mail agent can work with NNTP, it will tend to be as simple
as reading a mailing list only without touching your mail box.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo
Marcin Borkowski mb...@mbork.pl writes:
On 2015-04-12, at 20:04, David Kastrup d...@gnu.org wrote:
Marcin Borkowski mb...@mbork.pl writes:
Oh. This probably settles the thing. I had some hope that AUCTeX is
outside the scope of this FSF-papers insanity. I don't have those
papers signed
to hand over. It only concerns material you wittingly
contribute to the AUCTeX/Emacs repositories.
So it may make sense to consider whether the consequences of making your
point against the FSF are actually effective in promoting your ethics.
--
David Kastrup
not sensibly be done in
other ways) more or less as well, but we need to keep track of any
actually copyrightable contributions even when they are smaller than the
size we need for copyright assignments since the overall number of
contribution counts towards when we need an assignment.
--
David
name for
.pdf/.dvi as it does for its .tex file, and the .tex file of an included
file cannot be run through LaTeX without change.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
see what harm it could cause? I don't
see what it could overwrite? what do I miss?
test1.aux for example.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
this reroute TeX-command-buffer etc as
the user interface, but I don't think that the code is reasonably
prepared to do this.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
.
You really should only start improvising things after you've exhausted
the instructions and are quite sure there is nothing relevant left in
them that you overlooked.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https
-default TeX-master nil)
right on the first page.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
into a valid package
directory (which is the default), then this should work out of the box.
What you did instead does not appear to match those instructions.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org
Frankenstein installation in between will not likely
work.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
1 - 100 of 965 matches
Mail list logo
