# Ansible 1.6.9-10 line break issue

**URL:** <https://forum.ansible.com/t/ansible-1-6-9-10-line-break-issue/15863>\
**Category:** Ansible Project\
**Created:** [August 5, 2014, 11:16pm UTC](https://forum.ansible.com/t/ansible-1-6-9-10-line-break-issue/15863 "2014-08-05T23:16:54Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Patrick\_Heeney](https://avatars.discourse-cdn.com/v4/letter/p/f475e1/32.png) [@Patrick\_Heeney](https://forum.ansible.com/u/Patrick_Heeney)\
**Post date:** [August 5, 2014, 11:16pm UTC](https://forum.ansible.com/t/ansible-1-6-9-10-line-break-issue/15863/1 "2014-08-05T23:16:54Z")

</div>

Hello, I have a bunch of plabyooks with tasks that look like this:

- name: xdebug | set ini  
template: \>  
src=xdebug.ini.j2  
dest=/etc/php5/mods-available/xdebug-options.ini

- name: xdebug | add xdebug cli  
template: \>  
src=cli\_alias.j2  
dest={{ path\_php\_xdebug }}  
owner=root  
group=root  
mode=0755

However, the destination filename ends up with:

-rw-r–r-- 1 root root 143 Aug 5 23:10 apc.ini?

-rw-r–r-- 1 root root 143 Aug 5 23:10 xdebug-options.ini?

It adds the question mark due to including the line break in the filename. Previously all these tasks used to work. I believe I have other issues due to the tasks being structured this way. Is this a breaking change?

According to the code format guide, it suggested that long tasks be broken into multiple lines like this for better readability. It would be a pain to have a one-liner for every task.

Should this be reported as a bug since its a regression of behavior?

---

<div class="post-metadata">

**Author:** ![Michael\_DeHaan1](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@Michael\_DeHaan1](https://forum.ansible.com/u/Michael_DeHaan1)\
**Post date:** [August 5, 2014, 11:36pm UTC](https://forum.ansible.com/t/ansible-1-6-9-10-line-break-issue/15863/2 "2014-08-05T23:36:58Z")

</div>

Hi Patrick,

We’ve already had reports of these actually (very very recently) and fixed them and added tests to cover these cases.

We’re dropping Ansible 1.7 really really soon (this week) and these will be included as fixes.

Stay tuned or feel free to test against the devel branch now if you like.

Thank you!

–Michael