Nicolas Goaziou writes:
> Hello,
>
> Carsten Dominik writes:
>
>> yes, I am aware that LaTeX does use unnumbered for this, but this is
>> backend specific implementation, and not an argument about the logic of
>> this approach.
>
> Fair enough. I reverted the commit.
>
> I think a :NOTOC: proper
Hi Nicolas,
thanks!
Carsten
On Thu, Sep 21, 2017 at 9:21 PM, Nicolas Goaziou
wrote:
> Hello,
>
> Carsten Dominik writes:
>
> > yes, I am aware that LaTeX does use unnumbered for this, but this is
> > backend specific implementation, and not an argument about the logic of
> > this approach.
>
On Thu, Sep 21, 2017 at 3:23 PM Nicolas Goaziou
wrote:
> Fair enough. I reverted the commit.
>
Thanks!
> I think a :NOTOC: property to ignore headlines from TOC is an acceptable
> solution, even though it add yet another property.
>
+1 for :NOTOC:
With that it will be very clear what to expec
Hello,
Carsten Dominik writes:
> yes, I am aware that LaTeX does use unnumbered for this, but this is
> backend specific implementation, and not an argument about the logic of
> this approach.
Fair enough. I reverted the commit.
I think a :NOTOC: property to ignore headlines from TOC is an acc
On 09/20/2017 07:16 PM, Kaushal Modi wrote:
> I have to agree with Carsten. I use unnumbered table of contents all the
>> time in web pages. Almost all of my Org files that generate web pages have
>> the following:
>>
>> #+options: num:nil toc:t
>>
>
> @Scott Please see that other thread[1]. I ha
On Thu, Sep 21, 2017 at 11:39 AM, Rasmus wrote:
> Carsten Dominik writes:
>
> >> I believe this change was made to fix the case of mixed numbered and
> >> unnumbered headings in the TOC.
> >>
> >> Please see the other thread[1] where I suggest supporting the "case 3"
> >> where we want TOC where
Carsten Dominik writes:
>> I believe this change was made to fix the case of mixed numbered and
>> unnumbered headings in the TOC.
>>
>> Please see the other thread[1] where I suggest supporting the "case 3"
>> where we want TOC where all headings are numbered i.e. the case of num:nil.
>
> This w
Hi everyone,
On Thu, Sep 21, 2017 at 1:16 AM, Kaushal Modi
wrote:
> On Wed, Sep 20, 2017, 2:43 PM Scott Randby wrote:
>
>>
>>
>> On 09/20/2017 12:17 PM, Carsten Dominik wrote:
>> > On Thu, Sep 7, 2017 at 5:01 PM, Eric Abrahamsen <
>> e...@ericabrahamsen.net>
>> > wrote:
>> > I do object to re
On Wednesday, 20 Sep 2017 at 14:42, Scott Randby wrote:
[...]
> I have to agree with Carsten. I use unnumbered table of contents all
> the time in web pages. Almost all of my Org files that generate web
> pages have the following:
>
> #+options: num:nil toc:t
Ditto. I find a short TOC for web p
On Wed, Sep 20, 2017, 2:43 PM Scott Randby wrote:
>
>
> On 09/20/2017 12:17 PM, Carsten Dominik wrote:
> > On Thu, Sep 7, 2017 at 5:01 PM, Eric Abrahamsen >
> > wrote:
> > I do object to removing unnumbered headers from the toc.
I believe this change was made to fix the case of mixed numbered
On 09/20/2017 12:17 PM, Carsten Dominik wrote:
> On Thu, Sep 7, 2017 at 5:01 PM, Eric Abrahamsen
> wrote:
>
>> Nicolas Goaziou writes:
>>
>>
>> [...]
>>
>>> So, any objection to have all major back-ends ignoring unnumbered trees
>>> from TOC, and make that an Org specificity?
>>
>
>
> Hi Nic
On Thu, Sep 7, 2017 at 5:01 PM, Eric Abrahamsen
wrote:
> Nicolas Goaziou writes:
>
>
> [...]
>
> > So, any objection to have all major back-ends ignoring unnumbered trees
> > from TOC, and make that an Org specificity?
>
Hi Nicolas,
OK, now I have read this thread.
I do object to removing un
Hello,
Eric Abrahamsen writes:
> Nicolas Goaziou writes:
>
>> So, any objection to have all major back-ends ignoring unnumbered trees
>> from TOC, and make that an Org specificity?
>
> Sounds good!
Done in master.
Thank you for the feedback.
Regards,
--
Nicolas Goaziou
Nicolas Goaziou writes:
[...]
> So, any objection to have all major back-ends ignoring unnumbered trees
> from TOC, and make that an Org specificity?
Sounds good!
Hello,
Rasmus writes:
> Speaking of LaTeX: not-in-toc and unnumbered is easy enough in LaTeX
> as it’s just section*.
Great.
> ox-odt, ox-html and ox-ascii all seem to add unnumbered headings to the
> toc.
These are trivial to handle, since they use
`org-export-collect-headlines' to build TOC
Nicolas Goaziou writes:
> Maybe UNNUMBERED property could imply a "not in TOC" clause in every
> back-end (I assume this is difficult to implement for LaTeX, though). In
> that case, UNNUMBERED would be a generic answer the problem.
Speaking of LaTeX: not-in-toc and unnumbered is easy enough in
Nicolas Goaziou writes:
> Eric Abrahamsen writes:
>
>> I think I ran into trouble just doing a simple `org-store-link' from an
>> Info file, then `org-insert-link' in the Org mode manual.
>>
>> That produced:
>>
>> [[info:org#Installation][info:org#Installation]] -->
>> @ref{Installation,@ref{In
Eric Abrahamsen writes:
> I think I ran into trouble just doing a simple `org-store-link' from an
> Info file, then `org-insert-link' in the Org mode manual.
>
> That produced:
>
> [[info:org#Installation][info:org#Installation]] -->
> @ref{Installation,@ref{Installation,,,org,},,org,} -->
> *not
Nicolas Goaziou writes:
> Rasmus writes:
>
>> I could not get it to work. I tried stuff like "[[(org) Tables]]",
>> "[[*(org) Tables]]" and , [[texinfo:(org) tables]].
>
> You are talking about a special case for cross-referencing (which could
> include internal reference, URL referencess). Thi
Rasmus writes:
> I could not get it to work. I tried stuff like "[[(org) Tables]]",
> "[[*(org) Tables]]" and , [[texinfo:(org) tables]].
You are talking about a special case for cross-referencing (which could
include internal reference, URL referencess). This is the job of
"org-info.el":
[[
Hi,
Nicolas Goaziou writes:
> Rasmus writes:
>
>> Eric Abrahamsen writes:
>>
>>> The only real problem I encountered was that links to external Info
>>> manuals did not export correctly, and couldn't be followed. I gave up on
>>> learning the exact syntax of texinfo's @[px]ref commands because
Hello,
Rasmus writes:
> Eric Abrahamsen writes:
>
>> The only real problem I encountered was that links to external Info
>> manuals did not export correctly, and couldn't be followed. I gave up on
>> learning the exact syntax of texinfo's @[px]ref commands because it was
>> dinnertime, but I ca
Eric Abrahamsen writes:
> The only real problem I encountered was that links to external Info
> manuals did not export correctly, and couldn't be followed. I gave up on
> learning the exact syntax of texinfo's @[px]ref commands because it was
> dinnertime, but I can figure out what went wrong and
Rasmus writes:
> Hi,
>
> (Sorry for replying to this old thread which I am only reading now)
>
> Eric Abrahamsen writes:
>
I'm writing an Emacs manual in Org, using
https://github.com/tarsius/ox-texinfo-plus to make things a bit
easier.
>>>
>>> I don't know that library, but as a
Hi,
(Sorry for replying to this old thread which I am only reading now)
Eric Abrahamsen writes:
>>> I'm writing an Emacs manual in Org, using
>>> https://github.com/tarsius/ox-texinfo-plus to make things a bit
>>> easier.
>>
>> I don't know that library, but as a biased POV, it would be nice to
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> For example, the below looks like something you'd find in an Emacs
>> manual.
>>
>> #+BEGIN_SRC texinfo
>> @table @kbd
>> @item C-x C-f
>> @kindex C-x C-f
>> @findex find-file
>> Visit a file (@code{find-file}).
>> @it
Hello,
Eric Abrahamsen writes:
> For example, the below looks like something you'd find in an Emacs
> manual.
>
> #+BEGIN_SRC texinfo
> @table @kbd
> @item C-x C-f
> @kindex C-x C-f
> @findex find-file
> Visit a file (@code{find-file}).
> @item C-x C-r
> @kindex C-x C-r
> @findex
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> And regarding the lists of commands and keys, what would be the
>> recommended way of making a list of @deffns and corresponding index
>> entries?
>
> I don't know what is a list of @deffns. In any case, you can something
> like t
Hello,
Eric Abrahamsen writes:
> And regarding the lists of commands and keys, what would be the
> recommended way of making a list of @deffns and corresponding index
> entries?
I don't know what is a list of @deffns. In any case, you can something
like this:
#+attr_texinfo: :options categor
Eric Abrahamsen writes:
> Nicolas Goaziou writes:
>
>> Eric Abrahamsen writes:
>>
>>> Oh I don't think it's about shortcomings, just about having a version
>>> that's tweaked specifically for writing Emacs manuals. I _really_ want
>>> my packages to have info manuals, and I _really_ don't want
Nicolas Goaziou writes:
> Eric Abrahamsen writes:
>
>> Oh I don't think it's about shortcomings, just about having a version
>> that's tweaked specifically for writing Emacs manuals. I _really_ want
>> my packages to have info manuals, and I _really_ don't want to learn how
>> to write texinfo.
Eric Abrahamsen writes:
> Oh I don't think it's about shortcomings, just about having a version
> that's tweaked specifically for writing Emacs manuals. I _really_ want
> my packages to have info manuals, and I _really_ don't want to learn how
> to write texinfo. I saw Rasmus' Org manual in org,
Nicolas Goaziou writes:
> Hello,
>
> Eric Abrahamsen writes:
>
>> I'm writing an Emacs manual in Org, using
>> https://github.com/tarsius/ox-texinfo-plus to make things a bit
>> easier.
>
> I don't know that library, but as a biased POV, it would be nice to use
> "ox-texinfo" and let us know abo
Hello,
Eric Abrahamsen writes:
> I'm writing an Emacs manual in Org, using
> https://github.com/tarsius/ox-texinfo-plus to make things a bit
> easier.
I don't know that library, but as a biased POV, it would be nice to use
"ox-texinfo" and let us know about its shortcomings. Just saying.
Regar
Kaushal Modi writes:
> On Wed, Aug 2, 2017, 5:54 PM Eric Abrahamsen wrote:
>
> I'm trying to locally set `sentence-end-double-space' to t, to conform
> to the Emacs manual style. If I set it at the top of the file with:
>
> -*- sentence-end-double-space: t -*-
>
> It should be the very first
On Wed, Aug 2, 2017, 5:54 PM Eric Abrahamsen
wrote:
>
> I'm trying to locally set `sentence-end-double-space' to t, to conform
> to the Emacs manual style. If I set it at the top of the file with:
>
> -*- sentence-end-double-space: t -*-
>
It should be the very first line and prefixed with Org c
Hi there,
I'm writing an Emacs manual in Org, using
https://github.com/tarsius/ox-texinfo-plus to make things a bit easier.
I'm trying to locally set `sentence-end-double-space' to t, to conform
to the Emacs manual style. If I set it at the top of the file with:
-*- sentence-end-double-space: t
37 matches
Mail list logo
