From: Dylan Whyte <d.whyte@proxmox.com>
To: Dietmar Maurer <dietmar@proxmox.com>,
Proxmox Backup Server development discussion
<pbs-devel@lists.proxmox.com>
Subject: Re: [pbs-devel] [PATCH docs] move custom.css from 'docs/' to 'docs/_static/'
Date: Mon, 14 Sep 2020 08:40:34 +0200 (CEST) [thread overview]
Message-ID: <2078084101.1497.1600065634210@webmail.proxmox.com> (raw)
In-Reply-To: <1612959834.1463.1599834117011@webmail.proxmox.com>
Oh yeah, it seems you're right.. I was using sphinx-build directly when
testing all this and didn't think to check how the Makefile actually
manages things.. my bad..
Thanks for pointing that out!
Dylan
> On 11.09.2020 16:21 Dietmar Maurer <dietmar@proxmox.com> wrote:
>
>
> I think _static is dynamically allocated.
>
> also, the Makefile contains:
>
> cp custom.css $(BUILDDIR)/html/_static/
>
> confused!?
>
> > On 09/11/2020 4:08 PM Dylan Whyte <d.whyte@proxmox.com> wrote:
> >
> >
> > conf.py sets the variable html_static_path to a folder
> > named '_static'. This is where sphinx searches for custom
> > stylesheets, so before this change, custom.css had no effect.
> >
> > Signed-off-by: Dylan Whyte <d.whyte@proxmox.com>
> > ---
> > docs/{ => _static}/custom.css | 0
> > 1 file changed, 0 insertions(+), 0 deletions(-)
> > rename docs/{ => _static}/custom.css (100%)
> >
> > diff --git a/docs/custom.css b/docs/_static/custom.css
> > similarity index 100%
> > rename from docs/custom.css
> > rename to docs/_static/custom.css
> > --
> > 2.20.1
> >
> >
> >
> > _______________________________________________
> > pbs-devel mailing list
> > pbs-devel@lists.proxmox.com
> > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2020-09-14 6:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 14:08 Dylan Whyte
2020-09-11 14:21 ` Dietmar Maurer
2020-09-14 6:40 ` Dylan Whyte [this message]
2020-09-14 7:32 ` Thomas Lamprecht
2020-09-14 7:51 ` Dylan Whyte
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2078084101.1497.1600065634210@webmail.proxmox.com \
--to=d.whyte@proxmox.com \
--cc=dietmar@proxmox.com \
--cc=pbs-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal