TAB completion is not happy on OSX

[samoht]

Sometime I got some weird error messages when a TAB-complete the opam command-line (I'm on head).

 opam list<TAB> sed: 1: "/^\.SH COMMANDS$/,/^\.S ...": bad flag in substitute command: '}'

I think I've updated the autocomplete script recently to use the new ones, but maybe I did something wrong.

[AltGr]

If you could find the OSX - sed syntax for

/^\.SH COMMANDS$/,/^\.SH/ { s#\\-#-#g; s#^\\fB\([^,= ]*\)\\fR.*#\1#p }

I'd be grateful. Maybe just a ; after the last p ? Don't think I used any gsed specifics (but I may be wrong)

[samoht]

On http://stackoverflow.com/questions/4904225/need-help-porting-a-sed-command-from-debian-to-osx

OS X sed doesn't like multiple commands run together using semicolons or grouped in curly braces. If you have a sed script that consists of multiple commands, you'll have to break them up using -e

[AltGr]

(source here and here)

[AltGr]

graaah

Of course the best solution would be to have cmdliner output this directly :)

Maybe this could do the trick:

sed -e '/^\.SH COMMANDS$/,/^\.SH/ s#^\\fB\([^,= ]*\)\\fR.*#\1#p' -e 's#\\-#-#g'

[samoht]

For completion, @AltGr found the magic runes:

opam config --help=groff 2>/dev/null | sed -n -e 's%\\-%-%g' -e '/^\.SH COMMANDS$/,/^\.SH/ s%^\\fB\([^,= ]*\)\\fR.*%\1%p'

[AltGr]

#1739

[samoht]

If you have an idea on how to handle that properly in cmdliner, I'm sure you are aware of dbuenzli/cmdliner#1 :p