Not signed in (Sign In)

Not signed in

Want to take part in these discussions? Sign in if you have an account, or apply for one below

  • Sign in using OpenID

Site Tag Cloud

2-category 2-category-theory abelian-categories adjoint algebra algebraic algebraic-geometry algebraic-topology analysis analytic-geometry arithmetic arithmetic-geometry bundles calculus categorical categories category category-theory chern-weil-theory cohesion cohesive-homotopy-type-theory cohomology colimits combinatorics complex-geometry computable-mathematics computer-science constructive cosmology deformation-theory descent diagrams differential differential-cohomology differential-equations differential-geometry digraphs duality elliptic-cohomology enriched fibration finite foundations functional-analysis functor galois-theory gauge-theory gebra geometric-quantization geometry graph graphs gravity grothendieck group group-theory harmonic-analysis higher higher-algebra higher-category-theory higher-differential-geometry higher-geometry higher-lie-theory higher-topos-theory homological homological-algebra homotopy homotopy-theory homotopy-type-theory index-theory integration integration-theory internal-categories k-theory lie lie-theory limit limits linear linear-algebra locale localization logic manifolds mathematics measure-theory modal modal-logic model model-category-theory monads monoidal monoidal-category-theory morphism motives motivic-cohomology nforum nlab noncommutative noncommutative-geometry number number-theory of operads operator operator-algebra order-theory pages pasting philosophy physics pro-object probability probability-theory quantization quantum quantum-field quantum-field-theory quantum-mechanics quantum-physics quantum-theory question representation representation-theory riemannian-geometry scheme schemes set set-theory sheaf simplicial space spin-geometry stable-homotopy-theory string string-theory superalgebra supergeometry svg symplectic-geometry synthetic-differential-geometry terminology theory topology topos topos-theory type type-theory universal variational-calculus

Vanilla 1.1.10 is a product of Lussumo. More Information: Documentation, Community Support.

Welcome to nForum
If you want to take part in these discussions either sign in now (if you have an account), apply for one now (if you don't).
    • CommentRowNumber1.
    • CommentAuthorTobyBartels
    • CommentTimeFeb 11th 2009
    This comment is invalid XHTML+MathML+SVG; displaying source. <div> This is a bit small to put in a forum post, but it would be confusing to put it in the relevant page, and at least I know that Andrew will see it here. (^_^)<p>Andrew, I reverted your edit to the explanation on query boxes. The reason is to remove the space from the explanation, which can cause formatting problems. I think it best to keep technical explanations as legible as possible. Of course, there's nothing wrong with the other way, which (as you know) is how they give it in the Maruku documentation, except that it would be harder for a novice to read about.<p>Incidentally, I checked that they produce identical compiled XHTML.</p></p> </div>
    • CommentRowNumber2.
    • CommentAuthorAndrew Stacey
    • CommentTimeFeb 11th 2009

    Screen size!

    The original was +--{.query} with no spaces. This ensured that there was no problem with word-wrap. Putting the spaces in, particularly where this is on the line, does create a word-wrap problem I admit. I would rather solve it with non-breaking spaces though than removing the spaces. I note that you only removed one of the spaces, though. Maybe that fixed it for your browser but it still wraps on mine.

    The reason for making it correct syntax is to ensure that it is supported in all further upgrades. For all we know, the maintainer of maruku may decide to tighten up the support for these blocks and remove the sloppy syntax. Once that perpetuates downstream, all the blocks suddenly fail. However, the maintainer of maruku is unlikely to change the syntax which is stated on the maruku webpage so to be safe we ought to use correct syntax.

    I have no wish to start a wiki-war, especially over such a small matter, so I'll wait until we've reached a consensus here before editing the HowTo again. My vote is for correct syntax with non-breaking spaces. If that proves tricky (or looks horrendous) we could just remove the inline example and only have the displayed one (after all, what does the inline example do that the displayed one doesn't?).

    • CommentRowNumber3.
    • CommentAuthorAndrew Stacey
    • CommentTimeFeb 11th 2009

    Just checked on the Sandbox. Non-breaking spaces work correctly within inline code so that would eliminate the word-wrap whilst keeping the correct syntax.

    • CommentRowNumber4.
    • CommentAuthorTobyBartels
    • CommentTimeFeb 11th 2009
    Only removing one space this time was a typo (I forgot or didn't notice that there were two).

    OK, you have a point about the documentation. I don't like using nonbreaking spaces, since someone might pick that up with cut-and-paste and put such a space into the query box syntax, which doesn't work. (Actually, when I tested this in the Sandbox, it refused to accept my submission, returning me to the edit screen with no explanation!) OK, most software won't let you cut an paste a nonbreaking space, but really, isn't that a bug?

    • CommentRowNumber5.
    • CommentAuthorMike Shulman
    • CommentTimeFeb 11th 2009

    I'm in favor of using officially supported syntax.

    As for the HowTo, I think removing the inline code would be the simplest way to resolve the issue.

    • CommentRowNumber6.
    • CommentAuthorTobyBartels
    • CommentTimeFeb 11th 2009
    OK, you all've convinced me.