int in finding external
support for providing and supporting document classes implementing your
particular layout.
All the best
--
David Kastrup
don't include an example, so how are we supposed to tell?
--
David Kastrup
Arash Esbati writes:
> David Kastrup writes:
>
>> The question is whether this should be enough of a worry to stop such
>> settings to take effect automatically. I am not saying that it should,
>> just that this is the metric for making this change.
>
> Thanks fo
Arash Esbati writes:
> David Kastrup writes:
>
>> Arash Esbati writes:
>>
>>> I think this is a reasonable change. What do others think?
>>
>> Iam not sure what happens if you put, say, 1 in there.
>
> Maybe I'm missing the point, but how
is a reasonable change. What do others think?
Iam not sure what happens if you put, say, 1 in there.
--
David Kastrup
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
45678901234546789012.tex" "}"''
Probably exceeding a total command line length of 256 characters or some
similar Windows restriction. I also seem to remember that some Windows
file system or API limited the length of absolute filenames you could
access even when only using relative filen
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
this command also inserts a space
before and after, depending on the surrounding characters.
If region is active, insert enclosing characters at region boundaries.
This command assumes point is not in a string or comment.
--
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
eems that fewer
>> candidates are returned.
>
> The upside is that you don't get candidates like \begin which is
> nonsense in inline math.
Huh? Things like \begin{smallmatrix} are certainly useful in inline
math. They make it hard to pick a good way of formatting the _source_,
but the output is certainly fine.
--
David Kastrup
t get some details reported.
--
David Kastrup
You're in trouble here. Try typingto proceed.
> If that doesn't work, type X to quit.
>
> But I really can't find a way to solve this problem gracefully. Any
> tips will be appreciated.
Complain to the author of the iucr document class.
--
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
Snippet 1 ended.(282168+0x374556).
> <-><->
>
> l.5 $x$
>
> #+end_quote
>
>
> The issue here is that there's not enough context for
> ~preview-parse-messages~ to determine which $x$ to overlay.
I'd just add -file-line-error to the options you are calling TeX with.
C-n?
>>
>> I occasionally need to do that to get AUCTeX to prompt me for the
>> frametitle of beamer frames, it could be a similar problem here.
>
> Thanks for the suggestions, yes I have done it and no luck.
Which lines in the document are responsible for pulling in graphics.sty
or graphicx.sty ?
--
David Kastrup
k M-x list-load-path-shadows RET to see if you have an old auctex
> version somewhere messing things up.
Not to mention the settings for document parsing. \includegraphics is
only available via packages.
--
David Kastrup
; %%% mode: latex
> %%% TeX-master: "master"
> %%% TeX-master: "master"
> %%% TeX-master: t
> %%% End:
That's an accumulation of variable settings overwriting one another.
Remove the last two TeX-master lines.
--
David Kastrup
s transmogrified into en em-dash here, probably by your mailer)
>
> works for me after moving the `\special{background White}` inside the
> preview environment
>
> I tried with Red too to confirm
The proper way to get it into every output file is by using
\AtBeginDvi{\special{background White}}
--
David Kastrup
mmand line. That should
at least carry around some of the environment that
TeX-documentation-texdoc is working with. If it fails, you'll probably
get some info in the Emacs buffer used as terminal.
--
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
orted to its
developer list at dev-lua...@ntg.nl .
--
David Kastrup
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
s?
It's conceivable that one could improve on that particular example by
trying to limit context searches to start after the last completed
search in that line. But that could spell trouble for including the
same file several times.
--
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
David Kastrup writes:
> Denis Bitouzé writes:
>
>> Le 30/01/22 à 15h52, David Kastrup a écrit :
>>
>>> That would be pretty annoying for people working with any Latin-x
>>> encoding other than Latin-1 (or in general, any encoding not in Emacs
>>&
Denis Bitouzé writes:
> Le 30/01/22 à 15h52, David Kastrup a écrit :
>
>> That would be pretty annoying for people working with any Latin-x
>> encoding other than Latin-1 (or in general, any encoding not in Emacs
>> default autodetection set).
>
> In case of encodi
gt; package option, but rather on the Emacs heuristics and that, in case of
> discrepancy between the two, it issues a warning?
That would be pretty annoying for people working with any Latin-x
encoding other than Latin-1 (or in general, any encoding not in Emacs
default autodetection set).
Emacs showed you what LaTeX would have shown you.
--
David Kastrup
hooks, so one needs to hone in on some particular LaTeX
version for getting this under control.
Thanks for testing.
--
David Kastrup
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
t;>> accounting.
>>
>> Unfortunately, we could not find an agreement. If I understand well,
>> David Kastrup you are willing to do the job if paid by individuals,
>> but you refuse to edit a proper bill to be paid by organizations.
>
> AFAIK, editing a proper bill a
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
Hugo Raguet writes:
> Dear David Kastrup
>
> I have encountered a problem involving the latex package preview. If I
> understand well it is due to "a change in the latex shipout routine"
> in the last versions. I read the threads on the GNU bug reports 44578
>
ivated by the entitlement attitude that demanded
he be happy to invest work, time and energy that was more than the
complainant was willing to invest.
And I cannot really say that the continued abuse and entitlement is
doing a particularly swell job of raising motiv
C-x C-e' the
> following code in *scratch* buffer:
>
> (let ((default-directory "~/auctex"))
> (call-process "ls ~/auctex/configure" nil "*configure-output*" t))
That's not more simple but more complex. call-process requires an
_executable_ filename as argument, not a shell command.
--
David Kastrup
Tassilo Horn writes:
> David Kastrup writes:
>
>> You can preview $...$ just fine, you just don't get to call it an
>> environment.
>
> Yes, you are right. C-c C-p C-p on the example works with $...$.
>
>> C-c C-p C-p inside of an already existing (but
y established boundaries I think.
Assuming that I remember this detail correctly.
--
David Kastrup
It also means that LISP programs without a good
indentation strategy are inordinately harder to read for humans than
unformatted input in other languages.
As sort of a counterthesis, an indentation-sensitive language like
Python makes it in contrast quite hard to write (and parse) programs
correctly from within code.
--
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
is people thinking they are entitled to it
and argue you should do more for them.
There are times when this motivational framework does not work all that
well for me.
--
David Kastrup
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
here's no pathway and this toolchain is dead forever?
>
> Thanks for your appreciated comment,
So what are you willing to invest to avert the catastrophe? In terms of
procuring code or paying for the time of those who do?
--
David Kastrup
__
ding
another mode as a major mode is a mistake. It probably now causes the
local variable block to be reloaded, with obvious results.
--
David Kastrup
ps://github.com/latex3/hyperref/issues/166> pdfLaTeX fails on
>> pstool when hyperref is included · Issue #166 · latex3/hyperref
>> (github.com). The original bug report, a minimum example and all
>> needed files are posted there.
>
>> I would be absolutely willing to support the clarification of the issue.
>> Please inform me how to formally submit the bug report.
>
>> Thanks and best wishes,
>
>> Tobias Bruckmann
>
--
David Kastrup
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
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
color command" means in the context of fragments
displayed in an editor window with a different color scheme.
Sometimes, you can configure preview-reference-face but it's unlikely
that the customisation will make you happy for more than one document.
--
David Kastrup
stack (which is where PostScript passes data
around). I don't think that this should regularly be the case.
--
David Kastrup
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
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
e" nil] 4)
>TeX-master-file-ask()
>TeX-master-file(nil nil t)
>TeX-command-master()
>TeX-command-menu("LaTeX")
>eval((TeX-command-menu "LaTeX"))
That kind of error would happen when you are in the minibuffer when
trying to split a window. A
etting up the autoloads is pretty
small.
> (The elisp files loaded when `TeX-parse-self' is t are not so big in
> general, but the number of them can be large instead, e.g., when the
> opened LaTeX file uses quite many \usepackage's.)
AUCTeX searches around a whole lot for finding associated aut
Ryo Furue writes:
> Dear David and others,
>
> On Fri, Jun 28, 2019 at 6:04 PM David Kastrup wrote:
>
>> If you use ELPA for installing it, it is enabled by default. If we
>> would aim for AUCTeX only being used as a consequence of deliberate user
>> action rat
Ryo Furue writes:
> Dear David and others,
>
> On Fri, Jun 28, 2019 at 4:16 PM David Kastrup wrote:
>
>>
>> > Thinking more about this issue, I would argue that TeX-parse-self should
>> be
>> > set to t by default, because
>> >
>>
ould be hard to scan the LaTeX directory tree once for
> index search?)
> Just my two cents.
Have you bothered looking at the dozens of dollars already spent on that
issue? It is not a new discussion. If you want to change the outcome,
you need to bring a substantially new argument.
--
Da
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
___
bug-auctex mailing list
bug-auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-auctex
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
Ikumi Keita writes:
>>>>>> David Kastrup writes:
>>> Thanks for your advice, the attached patch works well. The foreground
>>> color of the generated image matches with the default face of emacs
>>> without `preview-pdf-color-string', at least
Ikumi Keita writes:
>>>>>> David Kastrup writes:
>> The current code is already a sledgehammer that looks like a "not again"
>> approach of evading yet another changed API. Looking at the history of
>> the recommended replacements, I see that
Ikumi Keita writes:
> [Adding auctex-de...@gnu.org in To: field may result in too many
> duplicated delivery of this message, so I refrain from doing so.]
>
> Hi David and all,
>
>>>>>> David Kastrup writes:
>
>> It never was a problem for
Ikumi Keita writes:
>>>>>> David Kastrup writes:
>>> Are you thinking that it isn't fruitful to follow up the development of
>>> ghostscript every time incompatible change is introduced?
>
>> No since the changes tend to be completely arbitrary. It'
Ikumi Keita writes:
> Hi David,
>
>>>>>> David Kastrup writes:
>> The usual "oh, we decided change is good and clobbered over the previous
>> API." Presumably one of the listed hooks can be used instead, possibly
>> mimicking what the
ures.
We eliminated GS_PDF_ProcSet and pdfdict, but runpdfbegin, dopdfpages,
and runpdfend are still available.
lib/pdf2dsc.ps
The usual "oh, we decided change is good and clobbered over the previous
API." Presum
variables prop line would have to have been added in the
lexical binding _branch_ already before getting folded into Emacs
proper. But 7 years is short in Emacs development times. I don't think
it's been much younger since it was all-in.
--
David Kastrup
___
-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
Joost Kremers writes:
> On Thu, Sep 13 2018, David Kastrup wrote:
>> Joost Kremers writes:
>>> Really? I mean, true, I see it a lot in (mostly older) config
>>> snippets Google spits up, but I thought it was generally discouraged
>>> to use a hook if
Joost Kremers writes:
> On Thu, Sep 13 2018, David Kastrup wrote:
>> Joost Kremers writes:
>>
>>> (add-to-list 'TeX-view-program-selection '((output-pdf "Zathura")))
>>>
>>> in your init file.
>>
>> Ah, but that depends on TeX-vie
fter-load incantation or
similar for this to work reliably.
> Doing it in LaTeX-mode-hook means it's executed each time you open a
> LaTeX file, which is harmless but unnecessary.
But the usual way to do such stuff.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
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
___
Rodolfo Medina writes:
> David Kastrup writes:
>
>> With regard to functions: instead of using keyboard macros, you can
>> first call some complex command like query-replace-regexp, then use
>>
>> C-x ESC ESC (translated from C-x ) runs the command
>> rep
Rodolfo Medina writes:
> David Kastrup writes:
>
>> Joost Kremers writes:
>>
>>> On Fri, Aug 24 2018, Rodolfo Medina wrote:
>>>> Hi all...
>>>>
>>>> In a MusiXTeX document, you insert several \bar(s) TeX commands,
>>>>
0
(unless they are already occupied), you can use
M-x replace-regexp ^.\{0,72\}$
\,(format "%-72sABC%05d" \& \#)
which is a bit tongue-in-cheek since it refers to conventions used for
mitigating the damage from dropping stacks of punch cards.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
s putting line breaks in the middle of multibyte
characters or ^^-quoting only some of them.
It would likely be possible to teach it to also deal with the
XeTeX-specific current situation, but it would likely end up being a
nightmare to maintain.
--
David Kastrup
_
1 - 100 of 1632 matches
Mail list logo
