matting, there may be a point in finding external
support for providing and supporting document classes implementing your
particular layout.
All the best
--
David Kastrup
tly?
You don't include an example, so how are we supposed to tell?
--
David Kastrup
‘parens-require-spaces’ is non-nil, 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
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
c 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
t; check 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
ansmogrified 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
_that_ command 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
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
ption, 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
simple test, i.e., `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
view would just use the already established boundaries I think.
Assuming that I remember this detail correctly.
--
David Kastrup
tself for generating
and analysing programs. 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
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
"respecting the pagecolor 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
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 ther
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
;d have to put this into an eval-after-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
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,
>>>>
columns 73 to 80
(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
when
> calling TeX is a good solution.
I think it was for setting interaction mode in a reasonably portable
way. At the current point of time, we likely just have to deal with
MikTeX and TeXlive.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
to post actual content, there is no point in
bothering the list until you do.
That may not work for list managers themselves since they may depend on
the outcome of their experiments for juggling with posts that keep
incoming from other people.
--
David Kast
d not admit more than 8.3. Even then, one could have
substructured this into CLS\8.3 PKG\8.3 and so on.
> And things get even worse when those files have the same basename, as
> in this case.
Well, it's not exactly cast in stone. One can still substructu
ll, I've installed it from ELPA.
>
> The problem still occurs.
>
>> That being said, our prerequisites in doc/install.texi do list Emacs 24
>> as requirement.
>
> So?
Your complaint would have been valid even when using 24. I do think
that your problem has already b
09-12 on hullmann, modified by Debian
24.5? 25 came out in 2014.
That being said, our prerequisites in doc/install.texi do list Emacs 24
as requirement.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
the sequence.
>
>
> even pdflatex does with option -8bit
>
> file test.tex
> \documentclass{article}
> \begin{document}
> \typeout{éàù}
> \end{document}
>
Lines are still getting wrapped after 79 bytes.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
utput thus relies on the output
actually being interpretable in the given encoding. We might have a bit
more leeway here with XEmacs out of the race (XEmacs' utf-8 encoding and
reencoding was not round-trippable).
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
Ikumi Keita writes:
>>>>>> David Kastrup writes:
>
>> The Emacs application type has nothing to do with the kpathsea
>> separator.
>
> Yes, of course. The Emacs application type only comes into play when
> it is intended to take the default value of
e kpathsea
separator. And the preferred shell can be different, too. That's why
there was a separate test and configuration variable in the first place.
> I will elaborate the method to determine the path separator in AUCTeX.
> Please wait for a while.
What was the commit removing all that functionality intended to fix?
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
ssional-service-pack-1
Looks to me like
commit 370a4b92155aebf3d0860c1211617d14d8e7951c
Author: Ikumi Keita
Date: Fri May 26 22:29:59 2017 +0900
Resolve preview-latex incompatibility with Japanese TeX (Bug#25322)
[...]
is responsible here. It adds the line
(TeX-command-expand "%(latex)" nil)
which is an invalid use of TeX-command-expand (I have no idea how this
could have ever worked).
I have no idea what the intent of that line ever was. "nil" probably
needs to be some file expansion function.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
Ralf Angeli writes:
> On 2017-10-22 19:55, David Kastrup wrote:
>
>> More of a problem of how Ghostscript works. It has a safer mode, and
>> for interactive mode, it must be possible to enter and exit it in
>> some manner. Ghostscript changes the details every few re
script works. It has a safer mode, and
for interactive mode, it must be possible to enter and exit it in some
manner. Ghostscript changes the details every few releases. I think
that the last few changes had been tracked and fixed by Ralf.
--
David Kastrup
___
entering
>> \includegraphics[]{test.eps}
>> \caption[]{Caption}
>> \end{figure}
>> \end{document}
>
> Why do you give dvipdfmx option to documentclass? I suppose you are
> using pdflatex.
While including test.eps? Unlikely.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
one to search.
Have you tried just hitting RET ? An empty string is a regexp matching
everything.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
Denis Bitouzé writes:
> Le 14/06/17 à 08h54, David Kastrup a écrit :
>
>> Frankly, I never use anything but a U.S. keyboard layout (with
>> whatever actual keyboard layout may be printed on the keys themselves)
>> with some mode shift or whatever else prov
. I don't get that but probably playing
around with keyboard layouts is beyond her comprehension. And she does
need to write in German occasionally and probably would not get the hang
of a Compose key or other contraption not printed on the keyboard.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
Marcin Borkowski writes:
> On 2017-05-01, at 15:46, David Kastrup wrote:
>
>> Marcin Borkowski writes:
>>
>>> Hi all,
>>>
>>> a friend of mine has this problem: he does not want $, & and % to have
>>> special meaning to (La)TeX, so
ould be a serious upstream battle. Language-specific editing
support relies on assumptions. That is one reason that LaTeX has
several editors catering to it pretty well while plain TeX (which does
not really provide much in the line of document structuring) doesn't.
I don't think tha
nd what's causing it. Try setting environment variable
>>> G_SLICE=always-malloc before evince runs and see if that stops the
>>> crashes.
>>
>> How to set the variable for evince started by AUC-TeX?
>
> Doesn't setting the environment variable in
ne with
> at most whitespace in front of it anymore. I hope it doesn't have any
> negative consequences, though. Well, and if it has, I guess _you_ will
> tell me. :-)
You'll probably want to see how verbatim.dtx behaves when describing
verbatim-like environments...
--
David Kas
r, it consists in telling people
what they should _not_ be doing since it would be detrimental to the
code base or project targets.
> And popularity plays a certain role. But such projects succeeded not
> least because of the ravages of time, being up-the-date also with
> modern---not
will switch anytime soon.
The first LaTeX2e release news dates from 1994, 22 years ago. If that
feels old, the first AUCTeX version is from 1991.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
d on. What would happen to Context if Hans did
the same?
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
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.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
tes-list call but have no
idea how its reliability or usefulness might differ.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
box, I see again the patch as a bug fix, not a
> new feature, I don't know how it could be seen otherwise in this case.
Have you actually looked at the code? I don't think it makes sense
discussing it without knowing what it does.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
David Kastrup writes:
> Konstantinos Theofilis writes:
>
>> On May 19, 2016, at 4:22 PM, David Kastrup wrote:
>>>
>>> Konstantinos Theofilis writes:
>>>
>>>> I cannot see why Mitsuharu’s suggestion contravenes with previously
>>>&
Konstantinos Theofilis writes:
> On May 19, 2016, at 4:22 PM, David Kastrup wrote:
>>
>> Konstantinos Theofilis writes:
>>
>>> I cannot see why Mitsuharu’s suggestion contravenes with previously
>>> followed policy.
>>
>> Feel free to
Konstantinos Theofilis writes:
> I have been following the discussion with a lot of interest as
> High-DPI in embedded previews affects me too.
>
>
>> On May 19, 2016, at 2:11 PM, David Kastrup wrote:
>> Your thoughts about my understanding are wrong but that doesn'
YAMAMOTO Mitsuharu writes:
>>>>>> On Wed, 18 May 2016 16:46:05 +0200, David Kastrup said:
>
>> Feel free to work out a framework where rerendering for changed
>> geometry (like for changing the size of a frame's default font)
>> provides benefits fo
ng MacOSX-only benefits, the GNU project
is the wrong place to provide them. That's one of the reasons that
there are several separate feature-enhanced forks for Mac (I haven't
kept track/count of them) and Windows that cater specifically for
features only implemented on those platforms.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
YAMAMOTO Mitsuharu writes:
>>>>>> On Wed, 18 May 2016 11:42:34 +0200, David Kastrup said:
>
>>> So they are always magnified and look blurry. This cannot be
>>> solved at the Lisp level.
>
>> That does not make a lot of sense: preview-latex queri
here, possibly going through some
widgetry.
That's a worthwhile project. If it's done modular enough, it might be
feasible even to put something based on PDFKit or so as an equivalent
renderer for Macs without having to create a separate framework/codepath
for it.
But a Mac-only soluti
s...well, more suitable.
Maybe meet in the middle? A roaring GNU?
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
as it includes features not fully supported by older browsers).
That being said, I consider animated logos highly rude. They distract
from the content.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
to do the expected thing in cases like
\ifpdfmodeorwhatever
\usepackage{pdftricks}
\else
\usepackage{pstricks}
\fi
...
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
rmanently? Something in .emacs file?
M-x customize-variable RET TeX-PDF-mode RET
Set the variable appropriately. Don't forget to save for future
sessions.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
José Carlos Santos writes:
> On 25-11-2015 1:53, David Kastrup wrote:
>
>>> No. :-( I use the 64 bit version of Ghostscript and it looks like
>>> preview.el only works with 32 bit Ghostscript.
>>
>> All of the respective executable names can be customized (by
ew-gs-command" with a value
>>
>> c:\PROGRA~1\GS\BIN\GSWIN32C.EXE
>>
>>
>> Try doing something similar in your case. Does that solve the problem?
>
> No. :-( I use the 64 bit version of Ghostscript and it looks like
> preview.el only works
about that. I'm currently in a bind regarding tax
deadlines so I cannot really start investigating. But I'm pretty sure
that something in either Emacs or AUCTeX must have significantly
changed.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
Mosè Giordano writes:
> 2015-11-04 13:45 GMT+01:00 David Kastrup :
>> Mosè Giordano writes:
>>
>>> 2015-11-04 11:13 GMT+01:00 David Kastrup :
>>>> Mosè Giordano writes:
>>>>
>>>>> 2015-11-04 10:27 GMT+01:00 Uwe Siart :
>>
David Kastrup writes:
> Mosè Giordano writes:
>
>> 2015-11-04 11:13 GMT+01:00 David Kastrup :
>>> Mosè Giordano writes:
>>>
>>>> 2015-11-04 10:27 GMT+01:00 Uwe Siart :
>>>>> On 4 Nov 2015 at 10:07, Mosè Giordano wrote:
>>>>&g
Mosè Giordano writes:
> 2015-11-04 11:13 GMT+01:00 David Kastrup :
>> Mosè Giordano writes:
>>
>>> 2015-11-04 10:27 GMT+01:00 Uwe Siart :
>>>> On 4 Nov 2015 at 10:07, Mosè Giordano wrote:
>>>>
>>>>> any objection against relea
ult, making it mostly accessible to
experts (namely avid manual readers and customizers) rather than people
who prefer to have things "just work" out of the box.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
rs in order. The "in
order" criterion does not make a whole lot of sense to me really since
the order of parameters is often determined by technical considerations
rather than how one would like to arrange a DOC string grammatically,
but there you are.
--
David Kastrup
__
(not (executable-find ...))
(error ...))
Since "when" only has a single clause, the two would be equivalent even
if error did return.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
r confirming, that means I at least don't have to dig any
> further for conflicting Emacs options.
>
>>> Anyway, I hope you can reproduce the problem now and can figure out
>>> what's going on. Thanks!
>>
>> I can reproduce it but preview is some kind of bl
ture wouldn't be useful,
particularly for a keyboard-centric workflow.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
goj...@gmail.com writes:
> On 150820 Thu 9:00, David Kastrup wrote:
>
>> I tend to right-click on the preview, copy the preview content and paste
>> it above where I am editing. Cleaning up afterwards is also easy with
>> the mouse (two right mouse clicks in a row
does not start off right with that
information. So in general we expect people to find that before they
find the bug reporting instructions...
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
Lars Madsen writes:
> I do not recall having problems with Evince on Ubuntu 12.04.
It's been more like 14.04 when they started for me: before that Xpdf was
the troublemaker. Haven't tried on 15.04 yet.
--
David Kastrup
___
auctex
to have a problem.
But so far, it's always been one _or_ the other.
Xpdf's crashes were some Poppler library version incompatibility.
Evince has some Dbus problem I think. At some point of time, it took
about 10 starts of Evince to have one succeed.
--
David Kastrup
_
Mosè Giordano writes:
> 2015-05-02 21:04 GMT+02:00 David Kastrup :
>> Mosè Giordano writes:
>>
>>> 2015-05-02 8:53 GMT+02:00 Tassilo Horn :
>>>> Mosè Giordano writes:
>>>>
>>>>> Reading more thoroughly `TeX-search-files-kpaths
Ken Brown writes:
> On 5/2/2015 3:04 PM, David Kastrup wrote:
>> Mosè Giordano writes:
>>> Are there notable corner cases (I don't know what may happen when
>>> running Emacs under Cygwin, for one)?
>>
>> Cygwin tends to have : as path separator an
e corner cases (I don't know what may happen when
> running Emacs under Cygwin, for one)?
Cygwin tends to have : as path separator and / as directory separator.
So if you are running a Cygwin Emacs with Mingw32 TeX or vice versa, you
don't get the paths to match. And Kpathsea may be independently
reconfigured regarding its path separator IIRC.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
jfbu writes:
> Le 30/04/2015 10:35, David Kastrup a écrit :
>>
>>> But with the syntax
>>>
>>> kpsewhich --progname latex --expand-path $SYSTEXMF
>>>
>>> $SYSTEXMF is not there as a path element
>>
>> If it weren't, your logg
STEXMF
>
> $SYSTEXMF is not there as a path element
If it weren't, your logging program would have had a hard time showing
its name, wouldn't it?
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
r{Chapter 1}{
>> \section{A section}{
>> Text in section.
>> }
>> }
>
> Yes, that would probably work.
More like %{ and %} I guess since a lot of commands and font changes in
LaTeX take up "save stack" when issued in a group.
--
David Kastrup
_
st to
preview-latex. preview-latex is only interesting for a limited number
of constructs (math ranks rather high there), but for those cases, it
tends to be very nice.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
n a way yes. What a stupid naming scheme. Maybe one should look
for gswin32c before gswin64c in case both are installed in a 32 bit
system. But I don't have an actual clue about Windows systems.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
ason preview-latex derives its column information from error
messages. The column information is not accessible at the TeX
programming layer.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
a literal copy&paste, try fixing the misspelling "Locall".
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
his is morally equivalent to (setf PLACE (cons NEWELT PLACE)),
except that PLACE is only evaluated once (after NEWELT).
[back]
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
jfbu writes:
> 29 nov. 2014 at 09:45, David Kastrup wrote :
>
>>>
>>> Makes me think that there could be a one-time-only
>>> parsing of the .emacs and customization files when
>>> a new Emacs major release is first executed by the
>>&g
lf.
This includes new user options and faces, and new customization
groups, as well as older options and faces whose meanings or
default values have changed since the previous major Emacs
release.
With argument SINCE-VERSION (a string), customize all settings
that were added or redefined since that
;> Perhaps preview-latex needs fixing in this area ? I don't know.
>
> Me neither. Maybe David can have a look at this issue.
Well, if tikz tries to fix the combination of preview and everyshi and
fails, I think it would be wrong to try fixing the failed fix from
outside of tikz. The o
is copyright.
Again: I don't know the history of the patch and what was discussed in
detail and what not.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
ab any code of his and declare it contributed to AUCTeX. He has
to submit it himself.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
n my local machine
> which has an ext3/4 file system. Only the *.tex files of the document
> (and all the *.log, *.bib etc) files are on a remote samba share.
You are contradicting yourself here since "." _is_ the directory of the
*.tex files
able to understand the idiosyncratic default output of
TeX are special TeX shells (like AUCTeX) and those should be able to get
along with file_line_error_style by now and be more reliable when using
it.
All non-TeX specific compilation tools will far
o in the
> ChangeLogs because that's the address that's registered with the FSF for
> your copyright assignment. But of course you can write the copyright
> clerk to add whatever address you like to your record.
Git knows how to correlate several mail addresses using a .mailmap file.
I think it is described in the manual page for git-shortlog.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
g this
problem tackled independently.
This code duplication would also explain my recurring eerie "didn't
I fix this already" feeling.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
s where the display property
is placed on text.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
likely be simpler. Don't have a
working TeXlive2013 right now, so cannot test.
--
David Kastrup
___
auctex mailing list
auctex@gnu.org
https://lists.gnu.org/mailman/listinfo/auctex
1 - 100 of 716 matches
Mail list logo