>> Duh: it's `:doc`, not `:manual`!
>> Sorry!
> Haha, and then it works just fine. ;-)
Yay!
Stefan
Stefan Monnier writes:
>>> [ This assumes that the `:manual ...` thingy does
>>> successfully build the docs. ]
>>
>> This is where I'm not sure. At least it doesn't seem to have an effect
>> when running "make auctex.tar" locally (as said in my other mail). The
>> tar file only contains
Here are a couple further packages I'm hoping to submit (after
14.0.5), this time related to preview.
* preview-auto requires the latest master
(4731168eca3f103732a026f70912597faef8bd99). It adds a keybinding "C-c
C-p C-a" that activates a minor mode in which previews automatically
generate near
> Yes, it is. But I need the distinction if the current version got
> there just now (in HEAD) or previously.
So just a "yes/no" kind of information? I wonder what you use it for.
>> [ This assumes that the `:manual ...` thingy does
>> successfully build the docs. ]
>
> This is where I'm
Stefan Monnier writes:
>>> Why do you need to look at diffs?
>> In order to extract the version number.
>
> I don't understand: it's right there in the file, you don't need the
> diffs to extract it, no?
Yes, it is. But I need the distinction if the current version got there
just now (in HEAD)
>> Why do you need to look at diffs?
> In order to extract the version number.
I don't understand: it's right there in the file, you don't need
the diffs to extract it, no?
> Does :manual ("doc/auctex.texi" "doc/preview-latex.texi") tell elpa to
> build the docs again although the recipe's :make
branch: master
commit 4731168eca3f103732a026f70912597faef8bd99
Author: Paul Nelson
Commit: Arash Esbati
Allow opened previews to remain visible
* preview.el.in (preview-leave-open-previews-visible): New user
option.
(preview-gs-place, preview-disable,
Tassilo Horn writes:
>> Our tarball build scripts can take care of building the Info files
>> and the `dir` (and moving them as needed), so maybe you can just add
>>
>> :manual ("doc/auctex.texi" "doc/preview-latex.texi")
>>
>> to the spec and that'll do the trick (with the advantage that
Stefan Monnier writes:
>> Why would I need the date of the last release?
>
> Don't know. I guess I misundersood what you meant by:
>
> Instead of looking at specially formatted lines in ChangeLog, it
> just looks at the git diffs to check when there was a "+;;
> Version: ..."
