How to Customize Firefox’s User Interface With userChrome.css

Today I read How to Customize Firefox’s User Interface With userChrome.css. You may need to enable with e.g. Firefox 69: userChrome.css and userContent.css disabled by default. If you change userContent.css you need to open your page in a new tab to force an update. I would guess that if you change userChrome.css you will need to restart Firefox (I don’t know I’ve only been using userContent.css).

I should be clear: there are two files: userChrome.css (which affects Firefox features like toolbars and tabs etc) and userContent.css (which affects web pages loaded in Firefox).

I’ve been using userContent.css to fixup CSS on various websites. You can limit your changes to a particular domain in this way:

/* 2020-07-01 jj5 - SEE: https://exploringjs.com/impatient-js/toc.html */
@-moz-document domain(exploringjs.com) {
  a:visited { color: purple !important; }
}

Konsole column width

So after having read this I was trying to configure Konsole by editing my config files under

~/.local/share/konsole

and I couldn’t get my column width config to apply.

The problem was that I was configuring column width with the TerminalCols setting, but the correct setting is actually TerminalColumns, which was difficult to figure out! Not sure how I managed to get that wrong in the first place, but it’s fixed now.

My new Konsole dimension settings are:

TerminalColumns=100
TerminalRows=42

How to clear dashed lines from LibreOffice Calc

I don’t know how it happened but suddenly I found I had this annoying situation in LibreOffice Calc whereby there were “dashed lines” repeating regularly throughout my sheets. Turns out it was display of page breaks. Anyway I found this and the solution was:

Tools ▸ Options ▸ LibreOffice Calc ▸ View ▸ Visual Aids ▸ Page breaks

Apache2 RewriteCond %{REQUEST_FILENAME} !-f not working

I was having an issue with my Apache2 config not matching files with:

RewriteCond %{REQUEST_FILENAME} !-f

I didn’t really get to the bottom of the problem, but I found that prefixing with the document root solved my issue:

RewriteCond %{DOCUMENT_ROOT}%{REQUEST_FILENAME} !-f

I have no idea why Apache wasn’t resolving %{REQUEST_FILENAME} relative to the project root, but I have a solution, so I have moved on.