Beefy Boxes and Bandwidth Generously Provided by pair Networks
Don't ask to ask, just ask

Using the Chatterbox: URLs, Special Characters, and Code

by SiteDocClan
on Jun 11, 2000 at 01:42 UTC ( #17544=sitefaqlet: print w/replies, xml ) Need Help??


Yes, you can create links in the CB!
See What shortcuts can I use for linking to other information?

Special Characters

Escaped HTML

Escaped HTML such as & or — will print differently depending on whether you are sending a public message or a private message. In public messages, the escaped HTML will be printed "as is". Private messages do accept escaped HTML though.

Angle brackets

The chatterbox attempts to parse things that look like HTML tags, and it generally does a pretty good job. If text surrounded by angle brackets looks like an HTML tag, the chatterbox will either:

  • leave it in the text stream, if it is allowed HTML;
  • remove it, if it is "unallowed"/pseudo HTML; or
  • replace it with something appropriate.
If the angle-enclosed text does not look like HTML, then the chatterbox leaves the text as you wrote it, except that the angle brackets themselves are converted to numeric entities, so that they render correctly in people's browsers.

Cases like these (allowed HTML or clearly not HTML) are rendered as expected:

  • <i><a href="">Perl</a></i> prints Perl in the chatterbox
  • if ( $a < $b && $c > $d ) ... - is rendered as shown
Cases like these (unallowed/pseudo HTML) are stripped from the text stream:
  • <hr>
  • <foo>

Square brackets

Because square brackets are used in the Everything code for easy linking between pages, you cannot use them to enclose anything you don't want linked. They may be used separately or inside out, however.

Valid cases:
[:) brrr!
who would ever use ][ in the chatterbox?
Invalid cases:
[login] prints login

As a quick work around you can type [[] and this will fool the chatterbox into creating a link to a node called [ so $arr[[]0] becomes $arr[0]

Other Special Characters

All other special characters may be typed as is. (Unicode??)


When you type code in the chatterbox, you should normally enclose it in <code> tags. This prevents the CB from possibly interpreting and changing your code. For example, if you want to type the following code:
and you don't put it in <code> tags, it will come out looking like this:
Even more drastic things can happen if your code contains angle brackets!
Back to the PerlMonks FAQ
Log In?

What's my password?
Create A New User
[oiskuu]: The useful bits that relate to your process can be found under /proc/self. What information are you thinking of? Tty name?
[tye]: I just daemonized and getlogin() still knew who I had been.
[tye]: perhaps loginuid ? Not that I concede that something not being in /proc means it is not useful.
[Corion]: tye: That's really interesting, but maybe it is because getlogin() returns the name, or the uid, so if that user has been replaced by another user with the same uid in the meantime, that's no problem to the system...
[davido]: or on ubuntu /var/run/utmp
[Corion]: Otherwise, I would imagine that a user with a process still alive would lock that information in memory.
[davido]: so last -f /var/run/utmp on ubuntu provides similar (though more verbose) info
[oiskuu]: glibc getlogin just does ttyname() and falls back on getutline(); it's not security related at all. (reminds me of sendmail and remote finger services of the naive early spam era)
[Corion]: But yes, "who started this process" is interesting information :)
[tye]: no, I really believe that "login user" was added as a fundamental bit of info about each process in order to enhance the usefulness of auditing

How do I use this? | Other CB clients
Other Users?
Others pondering the Monastery: (8)
As of 2017-06-23 19:36 GMT
Find Nodes?
    Voting Booth?
    How many monitors do you use while coding?

    Results (554 votes). Check out past polls.