ticket	summary	type	release	owner	status	created	modified	_description	_reporter
11322	Add support for program stdin reads, by allowing $$ in the middle of a line and format first part as output and second part as user input.	enhancement		Nathaniel Madura	new	2013-09-16T12:21:22+02:00	2013-09-16T12:21:22+02:00	"Sometimes you run a program or command, which prompts for some information in an interactive way.

Currently, you can only add two dollar signs ($$) at the start, which causes the full line to be put in prompt format. By allowing to add $$ in the middle of the line, you make such stdin reads possible. 

For example:
{{{
$ copy tftp file
(user is asked for an ip, so part of line is output, part of line is input!!)
TFTP server IP address:$$ {tftp_ip}
Choose file type:
1. config: 2. opcode: <1-2>:$$ 2
Source file name:$$ smcFirmware/latest.bix
Destination file name:$$ latest.bix
Processing...
Success!
}}}

The first part of the interactive lines should be formatted as output. The last part of the interactive lines should be formatted as user input. The `{tftp_ip}` would also be parsed as a variable in the user input."	anonymous
10111	output with special characters (help or feature request)	enhancement	0.11	Nathaniel Madura	new	2012-06-20T18:20:14+02:00	2012-06-20T21:45:10+02:00	"Love the plug-in, helps my documentation a lot.  I have run into the situation where the output of a command contains hits for the regexes.  I took a quick look at the code and it doesn't look like there is a way of escaping it.  If I missed something, drop me a line, if I'm right, this would be a nice feature.

For example:

{{{
{{{
#!ShellExample
$ git status
# On branch develop
# Changes to be committed:
#   (use ""git reset HEAD <file>..."" to unstage)
#
#       modified:   one
}}}
}}}

doesn't see the lines beginning with ""#"" as output.  I tried putting spaces in, or using the ""$$"".  Interestingly, prefixing it with ""!"" works but then the ""!"" symbols are included in the output.  So, maybe the feature could be, ""if starts with '!' and not '!!' treat as output -- but don't show the '!'.  With '!!' process as normal for the rare case of a non-output line beginning with '!'."	ctrudeau chr(64) arsensa.com