git/list[1] front-page[2] threads[3] people[4] search[5] about
 

t9401 fails with OS X sed

From
Brian Gernhardt <brian@gernhardtsoftware.com>
Date
Oct 25, 2012, 03:54 UTC
Message-ID
<609AC6E7-45CD-4472-B1DC-FBB785D6B815@gernhardtsoftware.com>
I seem to write these kinds of e-mails fairly regularly...
When running t9401-git-cvsserver-crlf:
expecting success: 
    check_status_options cvswork2 textfile.c "" &&
    check_status_options cvswork2 binfile.bin -kb &&
    check_status_options cvswork2 .gitattributes "" &&
    check_status_options cvswork2 mixedUp.c -kb &&
    check_status_options cvswork2 multiline.c -kb &&
    check_status_options cvswork2 multilineTxt.c "" &&
    check_status_options cvswork2/subdir withCr.bin -kb &&
    check_status_options cvswork2 subdir/withCr.bin -kb &&
    check_status_options cvswork2/subdir file.h "" &&
    check_status_options cvswork2 subdir/file.h "" &&
    check_status_options cvswork2/subdir unspecified.other "" &&
    check_status_options cvswork2/subdir newfile.bin "" &&
    check_status_options cvswork2/subdir newfile.c ""
not ok - 12 cvs status - sticky options
I have tracked it down to a sed expression that is parsing the output of cvs status:
49:    got="$(sed -n -e 's/^\s*Sticky Options:\s*//p' "${WORKDIR}/status.out")"
The problem is that cvs outputs "Sticky Options:\t\t(none)\n", but OS X's sed doesn't recognize the \s shortcut.  (According to re_format(5), \s is part of the "enhanced" regex format, which sed doesn't use.)  
It works if I change \s to [[:space:]], but I don't know how portable that is.
~~ Brian Gernhardt
Next: Geert Bosch
Message 1 of 10 in “t9401 fails with OS X sed”
  1. Brian GernhardtOct 25, 2012
  2. Geert BoschOct 25, 2012
  3. Jeff KingOct 25, 2012
  4. Torsten BögershausenOct 25, 2012
  5. Use character class for sed expression instead of \sBen Walton, Oct 25, 2012
  6. Brian GernhardtOct 25, 2012
  7. Torsten BögershausenOct 25, 2012
  8. Ben WaltonOct 25, 2012
  9. Torsten BögershausenOct 25, 2012
  10. Jeff KingOct 26, 2012

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.