Blog Terminal
Blog Terminal generates a terminal-like box that you can use to demonstrate terminal output or show the entry of terminal/console commands in a manner that is more demonstrative of actually using a Linux/Unix terminal or Windows cmd shell.
The code is a fork of Post Terminal, which is a fork of WP-Terminal which in turn is a modification of WP-Syntax, a source code highlighter plugin for WordPress.
Unlike Post terminal, it uses [terminal] shorthand for the terminal box. It also shows prompt only on lines explitly set to do that.
Basic Usage
The most basic usage is to wrap your terminal blocks with [terminal][/terminal] tags. If no further options are defined within the tag a generic prompt is generated using ‘user@computer’ with no working directory shown. This is similar to exporting PS1=”\u@\h:$ ” in sh(1), setting prompt=”%n@%m:$ ” in csh(1), etc.
Other options available within the tag are user=”user”, computer=”computer”, and cwd=”/path/to/directory”. These allow you to override the generic user@computer settings as well as provide a ‘current working directory’.
The prompt is only shown on the lines starting with ‘$ ‘. So you can mix commands with simulated terminal output.
Usage
Wrap terminal blocks with [terminal user="username" computer="computername" cwd="/path/to/directory"] and [\terminal]. They are all optional. “user” and “computer” will be shown if you don’t provide them, cwd is purely optional.
Example 1: No customized command
[terminal]
$ ls -a
[/terminal]
Example 2: User and computer customizations
[terminal user="tux" computer="linux"]
$ ls -a
[/terminal]
Example 3: Customizing just the user
[terminal user="dak"]
$ ls -a
[/terminal]
Example 4: Customizing user, computer and displaying a working directory
[terminal user="root" computer="linuxserver" cwd="/usr/src/linux"]
$ make mrproper
...
...
[/terminal]
| Domain | Exposures | Headers | Last Checked |
|---|---|---|---|
| k*1*e*.com (WP 6.8.5) | F | 2026-05-23 04:08:11 | |
| k*5*p*.com (WP 6.8.5) | F | 2026-05-23 03:03:16 | |
| s*y*a*k.org (WP 6.5.2) | F | 2026-05-21 21:36:44 | |
| k*t*e*k*m*l*.com | A | 2026-05-21 07:11:14 | |
| m*n*f*a*h.org (WP 6.9.4) | F | 2026-05-18 17:38:55 | |
| z*i*o*f*c*a*.com (WP 4.9.5) | F | 2026-05-17 12:27:34 | |
| n*w*g*d*e*.com | F | 2026-05-17 03:04:49 | |
| s*y*a*k*a*v*a.com (WP 6.5.2) | F | 2026-05-16 02:18:59 | |
| w*r*w*b.at | D | 2026-05-12 04:08:20 | |
| g*l*i*e*h*n*l*y.com | F | 2026-05-11 12:21:18 | |
| b*o*.d*c*a*y.org (WP 5.7.14) | F | 2026-05-11 09:20:39 | |
| c*r*i*n*e*h.com (WP 6.6.1) | F | 2026-05-10 18:24:30 | |
| b*o*.f*l*x*s*i*e*t.com (WP 6.9.4) | F | 2026-05-10 08:34:59 | |
| c*d*m*n*t*a.com (WP 6.9.4) | F | 2026-05-09 03:02:32 | |
| s*c*i*p*o*.com (WP 6.9.4) | F | 2026-05-08 22:34:22 | |
| c*b*t*r*s.com (WP 6.9) | F | 2026-05-08 17:05:37 | |
| b*e*b*o*c*m*u*e*.com (WP 6.6.5) | F | 2026-05-08 14:51:31 | |
| b*-*i*e.com (WP 6.8.5) | F | 2026-05-06 22:25:39 | |
| a*e*h*a*k.de (WP 6.9.4) | B | 2026-05-06 20:57:40 | |
| c*m*u*e*m*s*e*s.it | F | 2026-05-01 08:08:12 | |
| g*.a*e*h*a*k.de (WP 6.9.4) | B | 2026-04-29 17:23:25 | |
| f*o*c*i*d.com | A | 2026-04-27 23:49:57 | |
| t*e*i*u*l*b.com | F | 2026-04-27 20:40:59 | |
| f*l*x*s*i*e*t.com (WP 6.9.4) | F | 2026-04-19 13:53:00 | |
| s*a*o*i*n*.com | F | 2026-04-18 18:34:39 |