<p>Some escaping characters allowing to do seems reasonable:</p>
<pre><code>cat << EOF >> fooscript
\#!%{_bindir}/python
EOF
</code></pre>
<p>or</p>
<pre><code>%define SHARP #
cat << EOF >> fooscript
%{sharp}!%{_bindir}/python
EOF
</code></pre>
<p>However, if people has been using what <a href="https://github.com/pmatilai" class="user-mention">@pmatilai</a> has said, it is appropriate not to break the old working codes.</p>
<p>Then, what about emitting ERRORS when we meet multiline (\n in macro) macro inside comments?<br>
If that's fine with you, I'm willing to resubmit a commit.</p>
<p>E.g.,</p>
<pre><code>%define a blah
#%a
</code></pre>
<p>does not give an error.</p>
<p>However,</p>
<pre><code>%define a make \
  -DABC=abc
#%make
</code></pre>
<p>gives an error.</p>

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">—<br />You are receiving this because you are subscribed to this thread.<br />Reply to this email directly, <a href="https://github.com/rpm-software-management/rpm/pull/123#issuecomment-272134248">view it on GitHub</a>, or <a href="https://github.com/notifications/unsubscribe-auth/ANb80z9c6p3DNBnzYinJ5Rlui5Ocmd3Gks5rRgbHgaJpZM4LhkCf">mute the thread</a>.<img alt="" height="1" src="https://github.com/notifications/beacon/ANb80w-F2PyJ1-lTe9AlQKUuRCVnuKKZks5rRgbHgaJpZM4LhkCf.gif" width="1" /></p>
<div itemscope itemtype="http://schema.org/EmailMessage">
<div itemprop="action" itemscope itemtype="http://schema.org/ViewAction">
  <link itemprop="url" href="https://github.com/rpm-software-management/rpm/pull/123#issuecomment-272134248"></link>
  <meta itemprop="name" content="View Pull Request"></meta>
</div>
<meta itemprop="description" content="View this Pull Request on GitHub"></meta>
</div>

<script type="application/json" data-scope="inboxmarkup">{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/rpm-software-management/rpm","title":"rpm-software-management/rpm","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/rpm-software-management/rpm"}},"updates":{"snippets":[{"icon":"PERSON","message":"@myungjoo in #123: Some escaping characters allowing to do seems reasonable:\r\n```\r\ncat \u003c\u003c EOF \u003e\u003e fooscript\r\n\\#!%{_bindir}/python\r\nEOF\r\n```\r\nor\r\n```\r\n%define SHARP #\r\ncat \u003c\u003c EOF \u003e\u003e fooscript\r\n%{sharp}!%{_bindir}/python\r\nEOF\r\n```\r\n\r\nHowever, if people has been using what @pmatilai has said, it is appropriate not to break the old working codes.\r\n\r\nThen, what about emitting ERRORS when we meet multiline (\\n in macro) macro inside comments?\r\nIf that's fine with you, I'm willing to resubmit a commit.\r\n\r\nE.g.,\r\n```\r\n%define a blah\r\n#%a\r\n```\r\ndoes not give an error.\r\n\r\nHowever,\r\n```\r\n%define a make \\\r\n  -DABC=abc\r\n#%make\r\n```\r\ngives an error.\r\n\r\n"}],"action":{"name":"View Pull Request","url":"https://github.com/rpm-software-management/rpm/pull/123#issuecomment-272134248"}}}</script>