All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Quentin Schulz" <foss@0leil.net>
To: Quentin Schulz <quentin.schulz@streamunlimited.com>
Cc: Nicolas Dechesne <nicolas.dechesne@linaro.org>,
	docs@lists.yoctoproject.org
Subject: Re: [docs] [PATCH 1/2] docs: static: theme_overrides.css: fix responsive design on <640px screens
Date: Mon, 26 Oct 2020 18:47:33 +0100	[thread overview]
Message-ID: <91be94be029787448f6fb8c43eba8525@0leil.net> (raw)
In-Reply-To: <20200918081406.zr6u2evo55tfmgvz@qschulz>

Hi all,

On 2020-09-18 10:14, Quentin Schulz wrote:
[...]
> Also, I've spent an hour or sotrying to find a solution to make sphinx 
> detect
> static files changes but couldn't figure anything out.
> Beware, removing the _build/html directory isn't even enough to copy
> newly changed static files. I had to remove the whole _build directory
> to make it rebuild. There's probably a smarter way to do it but for
> automation you might to know what does not work well for now.
> 
> c.f.: https://github.com/sphinx-doc/sphinx/issues/2090
> 
> I didn't want to go the route of the last comment which is ALWAYS
> rebuilding index.rst and didn't want to hack to much.
> 
> So, static_css_files and static_js_files are copied only on the first
> build but not later on.
> 

Just to update on this, css/js files aren't watched over. However I 
believe this
is not an issue since css/js files are **always** copied when at least 
one page
is being regenerated. They are just not copied over when they're the 
only files
changed. This basically makes css/js development/debugging much more 
cumbersome
but it's fine for production since there's probably always going to be a 
commit
changing at least one doc page soon after a css/js change?

Quentin

  reply	other threads:[~2020-10-26 17:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17 21:09 [PATCH 1/2] docs: static: theme_overrides.css: fix responsive design on <640px screens Quentin Schulz
2020-09-17 21:09 ` [PATCH 2/2] docs: fix broken links Quentin Schulz
2020-09-18  8:22   ` [docs] " Quentin Schulz
2020-09-18  8:59     ` Nicolas Dechesne
2020-09-17 21:47 ` [docs] [PATCH 1/2] docs: static: theme_overrides.css: fix responsive design on <640px screens Nicolas Dechesne
2020-09-18  8:14   ` Quentin Schulz
2020-10-26 17:47     ` Quentin Schulz [this message]
2020-10-26 18:00       ` Nicolas Dechesne

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=91be94be029787448f6fb8c43eba8525@0leil.net \
    --to=foss@0leil.net \
    --cc=docs@lists.yoctoproject.org \
    --cc=nicolas.dechesne@linaro.org \
    --cc=quentin.schulz@streamunlimited.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.