It seems that nobody will ever implement a shortcut for the lack of a good HTML entity name of the [ character and its mate. How about at least adding a comment as to what the numeric entity is, with the blerb of instructions under the posting box? That is, where it says "...care should be taken to ensure that their contents do not have long lines..." and other advice, it could point out how to type these.

20030518 Edit by Corion : Changed title

Replies are listed 'Best First'.
Re: Typing square brackets in the monastery
by PodMaster (Abbot) on May 17, 2003 at 08:41 UTC
Re: Typing square brackets in the monastery
by pzbagel (Chaplain) on May 16, 2003 at 22:50 UTC
    What is wrong with enclosing them in the code tags?
    #The following enclosed in code tags [ ] [] [1] ({[<=>]}) *<[:^[]

    Bye

      which makes it impossible for people who click the "d/l code" link on your post to run your code without first stripping off the superfulous square brakets before/after (and possibly in the middle if you code is split up into several chunks seperated by documentation)

        I'm sorry, but I don't understand your comment. If you are writing code(which is suppose is what you would need to use square brackets extensively for) it should appear in code tags which handles your square brackets fine. Am I missing the point of this thread?

Re: Typing square brackets in the monastery
by Anonymous Monk on May 16, 2003 at 22:43 UTC
Re: Typing square brackets in the monastery
by adrianh (Chancellor) on May 17, 2003 at 22:11 UTC
    How about at least adding a comment as to what the numeric entity is, with the blerb of instructions under the posting box?

    I'd vote yes since I can never remember the codes off the top of my head.

Re: Typing square brackets in the monastery
by halley (Prior) on May 17, 2003 at 15:02 UTC

    I guess I have a funny workaround to remembering the &#91; and &#93; values. Since my default .sig includes them, every new comment I create has them in plaintext already.

    I agree, though-- the stock Everything bracket-puffer could probably be a little smarter for PerlMonks. For example, m/ \[ \d+ \] /x probably should not get puffed, nor should m/ \[ \$ \w+ \] /x. That would avoid a large number of inadverent bracket problems when discussing Perl, but not hamper the rest of the cool bracket linking features.

    --
    [ e d @ h a l l e y . c c ]

Re: Typing square brackets in the monastery
by tilly (Archbishop) on May 17, 2003 at 20:15 UTC