[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fIkeh5fT7fD6jstCzwiVIr8L7GVHq5RX0W_TNz34_j00":3},{"slug":4,"display_name":4,"profile_url":5,"plugin_count":6,"total_installs":7,"avg_security_score":8,"avg_patch_time_days":9,"trust_score":10,"computed_at":11,"plugins":12},"rsprta","https:\u002F\u002Fprofiles.wordpress.org\u002Frsprta\u002F",1,100,85,30,84,"2026-04-06T09:27:08.462Z",[13],{"slug":14,"name":15,"version":16,"author":4,"author_profile":5,"description":17,"short_description":18,"active_installs":7,"downloaded":19,"rating":20,"num_ratings":20,"last_updated":21,"tested_up_to":22,"requires_at_least":23,"requires_php":24,"tags":25,"homepage":31,"download_link":32,"security_score":8,"vuln_count":20,"unpatched_count":20,"last_vuln_date":33,"fetched_at":34},"blog-terminal","Blog Terminal","0.2.1","\u003Cp>Blog Terminal generates a terminal-like box that you can use to demonstrate terminal output or show the entry of terminal\u002Fconsole commands in a manner that is more demonstrative of actually using a Linux\u002FUnix terminal or Windows cmd shell.\u003C\u002Fp>\n\u003Cp>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.\u003C\u002Fp>\n\u003Cp>Unlike Post terminal, it uses \u003Ccode>[terminal]\u003C\u002Fcode> shorthand for the terminal box. It also shows prompt only on lines explitly set to do that.\u003C\u002Fp>\n\u003Ch4>Basic Usage\u003C\u002Fh4>\n\u003Cp>The most basic usage is to wrap your terminal blocks with \u003Ccode>[terminal][\u002Fterminal]\u003C\u002Fcode> 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.\u003Cbr \u002F>\nOther options available within the tag are user=”user”, computer=”computer”, and  cwd=”\u002Fpath\u002Fto\u002Fdirectory”. These allow you to override the generic user@computer settings as well as provide a ‘current working directory’.\u003Cbr \u002F>\nThe prompt is only shown on the lines starting with ‘$ ‘. So you can mix commands with simulated terminal output.\u003C\u002Fp>\n\u003Ch3>Usage\u003C\u002Fh3>\n\u003Cp>Wrap terminal blocks with \u003Ccode>[terminal user=\"username\" computer=\"computername\" cwd=\"\u002Fpath\u002Fto\u002Fdirectory\"]\u003C\u002Fcode> and \u003Ccode>[\\terminal]\u003C\u002Fcode>. They are all optional. “user” and “computer” will be shown if you don’t provide them, cwd is purely optional.\u003C\u002Fp>\n\u003Cp>\u003Cstrong>Example 1: No customized command\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[terminal]\n$ ls -a\n[\u002Fterminal]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Example 2: User and computer customizations\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[terminal user=\"tux\" computer=\"linux\"]\n$ ls -a\n[\u002Fterminal]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Example 3: Customizing just the user\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[terminal user=\"dak\"]\n$ ls -a\n[\u002Fterminal]\n\u003C\u002Fcode>\u003C\u002Fpre>\n\u003Cp>\u003Cstrong>Example 4: Customizing user, computer and displaying a working directory\u003C\u002Fstrong>\u003C\u002Fp>\n\u003Cpre>\u003Ccode>[terminal user=\"root\" computer=\"linuxserver\" cwd=\"\u002Fusr\u002Fsrc\u002Flinux\"]\n$ make mrproper\n ...\n ... \n[\u002Fterminal]\n\u003C\u002Fcode>\u003C\u002Fpre>\n","Blog Terminal provides a terminal-like box for embedding terminal commands within pages or posts.",3958,0,"2021-08-11T14:47:00.000Z","5.8.13","2.5","5.4",[26,27,28,29,30],"cmd","console","terminal","unix","xterm","https:\u002F\u002Fradeksprta.eu\u002Fprojects\u002Fterminal","https:\u002F\u002Fdownloads.wordpress.org\u002Fplugin\u002Fblog-terminal.0.2.1.zip",null,"2026-03-15T15:16:48.613Z"]