Aloha D. C.,
"D. C. Toedt" writes:
> I also see that there now seems to be some reluctance by the maintainers to
> accept donations. (See http://comments.gmane.org/gmane.emacs.orgmode/83318).
> Has that been resolved? I'd like to do a donation.
I think that was just Carsten's reluctance as he
Hi,
"D. C. Toedt" writes:
> I see this feature is now in the beta of Org-Mode 8.3. Excellent! I'm
> doing several things with it in the forthcoming release of the Common Draft
> contract clause library (linked below).
>
> I also see that there now seems to be some reluctance by the maintainer
I see this feature is now in the beta of Org-Mode 8.3. Excellent! I'm
doing several things with it in the forthcoming release of the Common Draft
contract clause library (linked below).
I also see that there now seems to be some reluctance by the maintainers to
accept donations. (See http://com
Rasmus writes:
>> As you pointed out already, moving hyperref after all other header lines
>> introduces problems with another set of packages. Therefore, we could
>> end up with package combinations that this variable couldn't handle.
>
> Of which we do not rely at the moment.
Of course, but I'
Nicolas Goaziou writes:
> Rasmus writes:
>
>> I was putting this to further support another solution, namely moving
>> hyperref to a single defcustom, allowing hyperref to be inserted after all
>> other header-lines.
>
> As you pointed out already, moving hyperref after all other header lines
>
Rasmus writes:
> I was putting this to further support another solution, namely moving
> hyperref to a single defcustom, allowing hyperref to be inserted after all
> other header-lines.
As you pointed out already, moving hyperref after all other header lines
introduces problems with another set
Nicolas Goaziou writes:
> Rasmus writes:
>
>> As said, I'd prefer load hyperref via org-latex-hyperref-template, but
>> it's probably too big a change too late. Though, it would resolve the
>> "issue" that if I do
>>
>>(setq org-latex-default-packages-alist
>> (delete '("" "hyperre
Rasmus writes:
> As said, I'd prefer load hyperref via org-latex-hyperref-template, but
> it's probably too big a change too late. Though, it would resolve the
> "issue" that if I do
>
>(setq org-latex-default-packages-alist
> (delete '("" "hyperref" nil)
> org-late
Hi,
Nicolas Goaziou writes:
> AFAIU, this is the only solution since we do not support titletoc in
> core.
As said, I'd prefer load hyperref via org-latex-hyperref-template, but
it's probably too big a change too late. Though, it would resolve the
"issue" that if I do
(setq org-latex-defa
Rasmus writes:
> I can add documentation, but please reconfirm that you find the above
> limitations acceptable and want to see suggestions of modifying
> org-latex-packages-alist in the manual!
AFAIU, this is the only solution since we do not support titletoc in
core. The modification is pretty
Hi,
Nicolas Goaziou writes:
>> One more thing. For LaTeX, *we must load titletoc before hyperref*.
>
> Requiring packages is not our problem.
For titletoc, you can only enable it by either
1. adding a new org-latex-class
2. insert titletoc in org-latex-default-packages-alist manually.
Rasmus writes:
> One more thing. For LaTeX, *we must load titletoc before hyperref*.
Requiring packages is not our problem.
> 3. Or we can add to the manual this deficit and advice how to solve it
> "manually".
I don't mind updating the footnote relative to titletoc package in the
manual. Do
Nicolas Goaziou writes:
> Hello,
>
> Rasmus writes:
>
>> Ah, it's much easier to use \stopcontents[level-i] to end contents
>> collection. Revising the example:
>>
>> \documentclass{book}
>> \usepackage{titletoc}
>> \begin{document}
>> \part{p1}
>> \startcontents[level-
Hello,
Rasmus writes:
> Ah, it's much easier to use \stopcontents[level-i] to end contents
> collection. Revising the example:
>
> \documentclass{book}
> \usepackage{titletoc}
> \begin{document}
> \part{p1}
> \startcontents[level-0]
> \printcontents[level-0]{}{0}{\
Rasmus writes:
>> I also note that these tocs do not have any title. Would it make sense
>> to remove title from local tocs in other back-ends too?
>
> No idea. Both makes sense, but maybe including the TOC-title is too
> verbose? In any case, I think it's easy to add a title if you. Based
> o
Hi,
Nicolas Goaziou writes:
> Rasmus writes:
>
>> I think we can do it with titletoc. I have used other functionality
>> of titletoc, and it 'doesn't sucks'ᵀᴹ. Below is an example. The
>> output is more inline with normal tocs, but you can also style it
>> [I've used this for making paragrap
Hello,
Rasmus writes:
> I think we can do it with titletoc. I have used other functionality
> of titletoc, and it 'doesn't sucks'ᵀᴹ. Below is an example. The
> output is more inline with normal tocs, but you can also style it
> [I've used this for making paragraph-TOCs in the past].
>
> So ox
Hi,
Nicolas Goaziou writes:
> I skipped latex because using minitoc looks too tricky to
> automate.
Sorry, I didn't see this when I posted my other post.
I think we can do it with titletoc. I have used other functionality
of titletoc, and it 'doesn't sucks'ᵀᴹ. Below is an example. The
outpu
Many thanks! I'll wait till this shows up in the package updater (I've
toyed with Git only enough to be dangerous) but am eagerly looking forward
to trying it.
D. C. (Dell Charles) Toedt III *(my** last name is pronounced "Tate") *
Attorney and neutral arbitrator -- tech contracts and intellec
Nicolas Goaziou writes:
> Hello,
>
> "D. C. Toedt" writes:
>
>> I'd like to do sub-TOCs for individual sections and subsections.
>
> We could add a "local" keyword to TOC lines, e.g.,
>
> #+TOC: headlines 1 local
>
> would mean only top level children in current headline.
>
> This feature is t
Hello,
"D. C. Toedt" writes:
> The local keyword would be great.
The following patch implements local tocs for ascii, html and odt export
back-ends. I skipped latex because using minitoc looks too tricky to
automate.
Feedback welcome.
Regards,
--
Nicolas Goaziou
>From 56e720f11c172b16a72fb
The local keyword would be great.
Right now I'm interested only in HTML export -- I can use Pandoc to convert
to anything else.
Thanks!
D. C. (Dell Charles) Toedt III *(my** last name is pronounced "Tate") *
Attorney and neutral arbitrator -- tech contracts and intellectual property
Lecturer,
Hello,
"D. C. Toedt" writes:
> I'd like to do sub-TOCs for individual sections and subsections.
We could add a "local" keyword to TOC lines, e.g.,
#+TOC: headlines 1 local
would mean only top level children in current headline.
This feature is trivial to add to ox-ascii, probably easy for
I'd like to do sub-TOCs for individual sections and subsections.
EXAMPLE
*#+TOC: headlines 1*
** Business operations*
{{{SUBTOC}}} # Inserts just the level-2 headings for this level-1
section
*** Services*
{{{SUBTOC}}} # Shows just the level-3 headings for this level-2
secti
24 matches
Mail list logo
