On Mon, Nov 02, 2020 at 12:30:18AM +0100, Patrice Dumas wrote:
> On Sun, Nov 01, 2020 at 07:26:52PM +0100, Patrice Dumas wrote:
> > On Sun, Nov 01, 2020 at 11:40:56AM +, Gavin Smith wrote:
> > > On Sun, Nov 01, 2020 at 01:37:04AM +0100, Patrice Dumas wrote:
> >
> > > In that case,
> > > > _
On Sun, Nov 01, 2020 at 07:26:52PM +0100, Patrice Dumas wrote:
> On Sun, Nov 01, 2020 at 11:40:56AM +, Gavin Smith wrote:
> > On Sun, Nov 01, 2020 at 01:37:04AM +0100, Patrice Dumas wrote:
>
> > In that case,
> > > _default_node_direction() should probably be changed, to give something
> >
On Sun, Nov 01, 2020 at 11:07:48PM +0100, Patrice Dumas wrote:
> On Sun, Nov 01, 2020 at 03:46:23PM +, jai-bholeki wrote:
> >
> > > But this would be an argument against changing USE_NODES to 0,
> >
> > It would mess up the cross references. @node is used to make new
> > pages in info. Thus
On Sun, Nov 01, 2020 at 03:46:23PM +, jai-bholeki wrote:
>
> > But this would be an argument against changing USE_NODES to 0,
>
> It would mess up the cross references. @node is used to make new
> pages in info. Thusly, when I want a reference without having info
> make a new page, I use @a
On Sun, Nov 01, 2020 at 12:30:35PM +, Gavin Smith wrote:
> On Sun, Nov 01, 2020 at 12:13:12PM +, jai-bholeki wrote:
> >
> > > I'm not sure how sensible it is to use @section without a @node or vice
> > > versa. A @node without a section wouldn't be in the section toc anyway,
> > > if I und
On Sun, Nov 01, 2020 at 09:04:02PM +, Gavin Smith wrote:
> On Sun, Nov 01, 2020 at 09:02:55PM +, Gavin Smith wrote:
> > I've gone and implemented it anyway (in commit b9920b16), because I
> > wanted to see what it would be like. It is for @def* commands only
> > at the moment, not for @anc
On Sun, Nov 01, 2020 at 09:02:55PM +, Gavin Smith wrote:
> I've gone and implemented it anyway (in commit b9920b16), because I
> wanted to see what it would be like. It is for @def* commands only
> at the moment, not for @anchor or for section headings. Turn it off
> with the -c PERMALINKS=0
On Sun, Nov 01, 2020 at 05:18:24PM +, Gavin Smith wrote:
> On Sat, Oct 31, 2020 at 03:16:26PM -0700, Per Bothner wrote:
> > On 10/31/20 2:26 PM, Gavin Smith wrote:
> > > Feel free not to consider it if you find implementing your desired
> > > functionality enough, but there has also been discus
On Sun, Nov 01, 2020 at 07:01:05PM +, Gavin Smith wrote:
> >
> > Ok, but then this means that there should be a sectiontoc if there is no
> > @shortcontents nor @contents.
>
> Yes, I agree.
I will commit a fix.
> Also, I wonder if the contents and shortcontents should
> be output after th
On Sun, Nov 01, 2020 at 07:26:52PM +0100, Patrice Dumas wrote:
> On Sun, Nov 01, 2020 at 11:40:56AM +, Gavin Smith wrote:
> > On Sun, Nov 01, 2020 at 01:37:04AM +0100, Patrice Dumas wrote:
> > > Hello,
> > >
> > > Why is there no sectiontoc for the @top?
> >
> > Because the index.html file us
On Sun, Nov 01, 2020 at 08:37:48AM -0800, Per Bothner wrote:
> On 11/1/20 7:10 AM, Gavin Smith wrote:
> > The colon is still present in the category, as I mentioned in
> > my other message.
>
> That colon is way ugly, but it seems easy to fix - see attachment.
The result cannot really be translat
On Sun, Nov 01, 2020 at 11:40:56AM +, Gavin Smith wrote:
> On Sun, Nov 01, 2020 at 01:37:04AM +0100, Patrice Dumas wrote:
> > Hello,
> >
> > Why is there no sectiontoc for the @top?
>
> Because the index.html file usually has @contents or @shortcontents
> as well as the Top node.
>
> At http
On Sun, Nov 01, 2020 at 08:53:41AM +, Gavin Smith wrote:
> On Sat, Oct 31, 2020 at 11:07:18PM +0100, Patrice Dumas wrote:
> > > Using all words would be better. I had been concerned about backwards
> > > compatibility. Maybe changing it to FORMAT_MENU would be better to
> > > avoid confusion w
On 11/1/20 9:40 AM, Gavin Smith wrote:
On Sun, Nov 01, 2020 at 08:37:48AM -0800, Per Bothner wrote:
On 11/1/20 7:10 AM, Gavin Smith wrote:
The colon is still present in the category, as I mentioned in
my other message.
That colon is way ugly, but it seems easy to fix - see attachment.
I gue
On Sat, Oct 31, 2020 at 09:26:30PM +, Gavin Smith wrote:
> I read an explanation online of how it worked a few days ago; unfortunately
> I cannot find it again now.
Found it:
https://django-sphinxdoc.readthedocs.io/en/latest/change_appearance.html
> To only show the headings’ “¶” sign if you
On Sun, Nov 01, 2020 at 08:37:48AM -0800, Per Bothner wrote:
> On 11/1/20 7:10 AM, Gavin Smith wrote:
> > The colon is still present in the category, as I mentioned in
> > my other message.
>
> That colon is way ugly, but it seems easy to fix - see attachment.
I guess so, although it makes the HT
On Sat, Oct 31, 2020 at 03:16:26PM -0700, Per Bothner wrote:
> On 10/31/20 2:26 PM, Gavin Smith wrote:
> > Feel free not to consider it if you find implementing your desired
> > functionality enough, but there has also been discussion of outputting
> > an "anchor" at def items to provide a link tha
On 11/1/20 7:10 AM, Gavin Smith wrote:
The colon is still present in the category, as I mentioned in
my other message.
That colon is way ugly, but it seems easy to fix - see attachment.
Note I prefer rather than because it helps makes the output
well-formed XML, which I think is useful. (Th
> But this would be an argument against changing USE_NODES to 0,
It would mess up the cross references. @node is used to make new
pages in info. Thusly, when I want a reference without having info
make a new page, I use @anchor. Having @node use as cross reference
is much more useful than jus
On Fri, Oct 30, 2020 at 05:05:28AM -0700, Per Bothner wrote:
> dt.synopsis span.category { float: right; padding-left: 2em; }
> dt.synopsis span.category:before { content: "[" }
> dt.synopsis span.category:after { content: "]" }
> dt.synopsis span.category-suffix { display: none }
As of commit 2d2
> I'm not sure how sensible it is to use @section without a @node or vice
> versa. A @node without a section wouldn't be in the section toc anyway,
> if I understand correctly.
@node makes a separate page. If your sections are small, by simply
removing @node, you can get the sections together.
> I don't have a strong opinion about it, but I feel that the primary
> meaning of @node is to define a named unit of the manual, rather than
> define a cross-reference target. This would mean that each node
> would be in a separate HTML file when output is split, which means
> that USE_NODES shoul
On Thu, Oct 29, 2020 at 03:46:23PM -0700, Per Bothner wrote:
> The html output for definitions only allows for very limited css styling.
>
> As an example of the kind of styling it would be nice to enable, in my Kawa
> and
> DomTerm manuals I move the "category" to the right margin,
> as you can
On Sun, Nov 01, 2020 at 12:13:12PM +, jai-bholeki wrote:
>
> > I'm not sure how sensible it is to use @section without a @node or vice
> > versa. A @node without a section wouldn't be in the section toc anyway,
> > if I understand correctly.
>
> @node makes a separate page. If your sections
On Sun, Nov 01, 2020 at 01:37:04AM +0100, Patrice Dumas wrote:
> Hello,
>
> Why is there no sectiontoc for the @top?
Because the index.html file usually has @contents or @shortcontents
as well as the Top node.
At https://www.gnu.org/software/texinfo/manual/texinfo/html_node/index.html
there are
On Sat, Oct 31, 2020 at 11:07:18PM +0100, Patrice Dumas wrote:
> > Using all words would be better. I had been concerned about backwards
> > compatibility. Maybe changing it to FORMAT_MENU would be better to
> > avoid confusion with the old meaning.
>
> I agree. Do you want that we keep a SHOW_M
26 matches
Mail list logo
