Ken Sharp writes:
> On 17/03/2025 16:43, David Kastrup wrote:
>
>>> Well nothing ever is, is it ? On-going maintenance is part of the
>>> deal. The problem here is that you want us to take on that task.
>>
>> That is the point of an API: provide a stable i
Ken Sharp writes:
> On 17/03/2025 15:20, David Kastrup wrote:
>>
>> The problem is that judging from previous experience with Ghostscript
>> development, this would not be a one-time task.
>
> Well nothing ever is, is it ? On-going maintenance is part of the
> deal
Ken Sharp writes:
> On 17/03/2025 13:16, David Kastrup wrote:
>
>> The interaction with GhostScript involves "please render now page xxx
>> into a PNG file". This interaction is done in a pipe, the order is not
>> known in advance but depends on the viewin
have not found
anything in GhostScript that provides similar (and documented!)
stability for PDF processing of individual pages efficiently and in
dynamically determined order.
--
David Kastrup
imply 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
ot; path
(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
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}
>>
>>
would not strip but retain the 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
some exotic configs, of course, but I feel like in the long run it
> might be worth it.
>
> WDYT?
Doesn't really seem to fit the conventions for major and minor mode
keybindings.
--
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,
>>
e 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,
> what's the issue here?
This looks like it should rather rely on lexical-binding being t and
write
:help (lambda (&rest _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
t this time it was not.
You have a menu of what to do with the change, and you want the "Set For
Future Sessions" item in this case.
--
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
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
it?
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 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
e (append 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
ode)
ftcrhb:-PfEd-Unifont-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
Yeah, I'd appreciate if someone clarifies 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
>>> apparently s
went
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...
>>
oper, 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 confir
+Mon Oct 20 10:15:42 1997 Peter S Galbraith
+
+ * 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
omebody 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
t case, the background color 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 b
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 pr
ted.
>
> Chris, 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 o
f 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.gma
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
&g
both 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:
> --
> 5dc76f79d0fff44794262037b93f0533af78f
might 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.
e 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
Commit messages 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
others
> 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
(next-error, previous-error, first-error, next-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
___
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 p
.in:Sequences 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 char
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 writes:
> Ikumi Keita writes:
>
>> Hi Mosè and all,
>>
>>>>>>> Mosè Giordano writes:
>>> sorry for the late reply, these days I'm getting all @gnu.org emails
>>> with huge delay.
>>
>> It seems that the
e 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.
>
>> 2017-12-01 23:34 GMT+01:00 David
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 containing comma itself in the PATH. Is
that an allowed character in
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 writes:
>>>>>> David Kastrup writes:
>
>> You know, it is not prohibited to actually test out such things.
>
>> dak@lola:/usr/local/tmp/lilypond$ kpsewhich --progname=latex --expand-path
>> "/home/dak/tex/india/:/tmp"
>> /h
David Kastrup writes:
> "Ikumi Keita" writes:
>
>> This is an automated email from the git hooks/post-receive script. It was
>> generated because a ref change was pushed to the repository containing
>> the project "GNU AUCTeX".
>>
&g
se 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? The code you replaced was not an
accident.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
David Kastrup writes:
> David Kastrup 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' occ
David Kastrup 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 first
>
Arash Esbati writes:
> Mosè Giordano writes:
>
>> 2017-11-10 18:42 GMT+01:00 David Kastrup :
>>> Uwe Brauer writes:
>>>
>>>> Ok, what's about styles? Could those go in the future in both branches,
>>>> in master in the 11.92-old or wha
nambiguously 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
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 operator in Ghostscript 9
---
commit 837d590008c1dd4e92ffbce15008efb761d11f7c
Author: David Kastrup
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 operator in Ghostscript 9
't expect to view the output of the compilation as
> you enter the code. You might look at an initial output but then you
> would concentrate on the code before compiling again - you surely
> wouldn't do both simultaneously. TeX/LaTeX is also
view the document? If
> you only want to sync the viewer, you should define a custom command
> that does that, why hijacking a command that is supposed to do
> something else? In addition, what's the point of syncing the viewer
> without viewing it?
"Viewing it"
|
> % \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 appears
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
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 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.gnu.org/mailman/lis
Uwe Brauer 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.
--
David Kastrup
___
auctex-deve
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 list.
--
ne 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 not paid for mostly idling,
he'll be working off a task queue.
Uwe Brauer writes:
>> On 28 Aug 2016, at 23:33, David Kastrup 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
>> maintainers are so because of being in
hat 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 writes:
>>>> "David" == David Kastrup writes:
>
>> Uwe Brauer writes:
>>> Hi
>>>
>>> I just received the copyright papers. It seems that the clerk put in
>>> only GNU auctex, which I interpret as
CTeX/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 writes:
> 2016-07-17 19:28 GMT+02:00 David Kastrup :
>> Mosè Giordano writes:
>>
>>> It looks overall good to me, but note that error messages *do not* end
>>> with a period (see `error`'s docstring) and you should replace the
>>>
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
uot;)
>
> 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
ner. 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
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
nd 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.
t 6 AUCTeX
users all in all.
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
ember 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 pr
ff finished. 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
it 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
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
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
e translation at work? Are you using some sort of a
network drive and some Windows/UNIX mixture making use of it?
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
ase_11_89 -> release_11_89
> Updating b072f9c..15ebec9
> error: Your local changes to '.gitignore' would be overwritten by
> merge. Aborting.
> Please, commit your changes or stash them before you can merge.
>
> I don't know which changes git is referring to.
Try
> the same as
>>
>> heading
>>
>> ?
>
> As always, thanks for your comments. You are right, of course,
Only if (stringp heading) => t and possibly some other conditions. %s
converts also non-strings.
--
David Kastrup
___
k 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
uot; . ?\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
Uwe Brauer writes:
>>>> "David" == David Kastrup writes:
>
>> Uwe Brauer writes:
>>>>>> "Tassilo" == Tassilo Horn writes:
>>>
>>> > Uwe Brauer writes:
>>> > Hi Uwe,
>>>
>>>
("\\setC" . ?\u2102)
> ("\\quad" . ?␣)
> ("\\qquad" . ?\u29e2)
> ("\\varrho" . ?ϱ)
> ("\\setZ" . ?\u2124)))
> (add-to-list 'tex--prettify-symbols-alist el))
>
> But it does not work what do I miss?
_Where_ do you have that?
--
David Kastrup
___
auctex-devel mailing list
auctex-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex-devel
this
> 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
ve some spurious ^ or _
> somewhere in your text (not in some math) you won't see it at all. And
> AUCTeX's font-latex does not raise/lower scripts on multiple levels,
> e.g., with x^y^z the y and the z have the same size and are equally
> raised.
Uh, correct? That's an
CTeX using
>
> 21.4.1 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
which I think is a
> bash shell) and it returns
>
> /usr/texbin/xdvi
>
> Isn't (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
applicatio
og your 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/auctex-devel
Marcin Borkowski writes:
> On 2015-04-12, at 20:04, David Kastrup wrote:
>
>> Marcin Borkowski 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
&g
1 - 100 of 1490 matches
Mail list logo
