# OOD as a teaching tool

**URL:** <https://discourse.openondemand.org/t/ood-as-a-teaching-tool/1401>\
**Category:** Get Help\
**Created:** [March 25, 2021, 5:40pm UTC](https://discourse.openondemand.org/t/ood-as-a-teaching-tool/1401 "2021-03-25T17:40:30Z")\
**Posts on this page:** 1\
**Showing post:** 12

<div class="post-metadata">

**Author:** ![jeff.ohrstrom](https://sea1.discourse-cdn.com/flex015/user_avatar/discourse.openondemand.org/jeff.ohrstrom/32/136_2.png) [@jeff.ohrstrom](https://discourse.openondemand.org/u/jeff.ohrstrom)\
**Post date:** [March 29, 2021, 7:26pm UTC](https://discourse.openondemand.org/t/ood-as-a-teaching-tool/1401/12 "2021-03-29T19:26:43Z")

</div>

OK I made a version of tmux 2.7 and was able to replicate this issue. Apparently it doesn’t like that field seperator and instead prints underscores. So even though we say one thing, it prints another and therefore can’t parse it. I’m submitting a patch shortly, but you should be able to edit this line and use a comma instead. I need to sort out what will be more reliable, but I don’t believe offhand bash (or any other shell) interprets commas as anything important.

> <https://github.com/OSC/ood_core/blob/e8d004b4fd464c193e9aa86e346b437dbef2ba65/lib/ood_core/job/adapters/linux_host/launcher.rb#L19>

---

_[View the full topic](https://discourse.openondemand.org/t/ood-as-a-teaching-tool/1401)._
