Sed matches entire lines but doesn't include the newline, so a blank line will just be an empty string. You can use ^ to match the beginning of a line and $ to match the end, so ^$ matches a blank line. Just replace that with % ghi\n%:
sed 's/^$/% ghi\n%/'
The newline that already existed will remain, so you'll end up with % ghi on one line and % on the next
Edit: If it needs to only match once then the expression is a bit more complicated. The easiest way I know to do it in sed is:
sed '0,/^$/ s/^$/% ghi\n%/'
The replacement is wrapped in an address range 0,/^$/, which means "only apply the following to the lines between 0 and the first line that matches ^$". Since the replacement expression checks for ^$ as well, the only line that's actually going to change is the first that matches ^$ -- the first blank line
Just use awk directly:
awk '/\/g/ {
gsub(/\./, "", $2)
gsub(/../, "&:", $2)
sub(/:$/, "", $2)
print $2,$3
}'
With this solution you don't need grep nor sed.
Best Answer
The behavior of shell utilities does differ in minor ways between unix variants. There are many unix variants, with a complex history. There are standardisation efforts such as the POSIX standard and its superset the Single UNIX specification. Most systems nowadays implement POSIX:2001, also known as the Single UNIX Specification version 3, with minor deviations and many extensions. The Single Unix specification is not a tutorial, but version 3 is readable if you already have an idea of what a command is doing. You can consult it to know if some feature is standard or an extension of a particular system.
A majority of unix users use Linux and haven't used any other variant. Linux comes with GNU utilities, which often have many extensions to the standard. So you'll find quite a lot of code out there that works on Linux but not on other unices, because it relies on those extensions.
Regarding sed, consult the sed Single Unix specification for the minimum that every system is supposed to support, the man page on your system for what your implementation supports, and the GNU sed manual for what most people out there use.
One of the nonstandard extensions in GNU sed is supporting multiple commands run together. For example, this GNU sed program prints all lines containing an
a, but changesbintocfirst:{and}are actually separate commands, so for full portability, you need to specify them either on separate lines (in a file) or in separate-earguments (on the command line). The lack of a command separator after{and the use of;as a command separator are common extensions. The lack of a command separator before}is a less common extension. This is standard-compliant:This is nonstandard but commonly accepted:
Another nonstandard but common extension is the use of
\nto mean a newline in asreplacement text (the use in a regexp is standard). The portable method is to include backslash-newline in the sed script. Another common extension is\+,\?and\|in regexps to mean one or more, at most one and alternation; portable basic regular expressions have none of these. For example, the first command is a non-portable way of replacing contiguous sequences of whitespace by a newline; the second command is a standards-compliant equivalent.