Hi, intrigeri <[email protected]> (2017-12-08): > Cyril Brulebois: > > Fix veing/being, and fix extraneous newline inside a `code` fragment. > > Thanks, applied!
\o/ > What's the problem with this "extraneous newline" by the way? > AFAIK this change is a no-op and the previous version worked perfectly > fine (except perhaps wrt. syntax highlighting in some editors?) Here's the rendering in Firefox and in Chromium without the patch: | If Vagrant failed to start the Tails builder VM the first time (e.g. because of permission issues | or the kvm module not veing loaded) it will not automatically run the provisioning script, so | you must run rake vm:provision yourself before attempting your first rake build. If that | fails, run rake vm:destroy, which removes this half-broken VM, and then start from scratch | with rake | build or similar. Of course that depends on screen width, fonts, zoom levels, etc., so you might not have seen it. Anyway, if there's a newline within the <code> tag, it's displayed as a line break because of this CSS property: white-space: pre; Cheers, -- Cyril Brulebois -- Debian Consultant @ DEBAMAX -- https://debamax.com/
signature.asc
Description: PGP signature
_______________________________________________ Tails-dev mailing list [email protected] https://mailman.boum.org/listinfo/tails-dev To unsubscribe from this list, send an empty email to [email protected].
