emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Giacomo M <jackjackk@gmail.com>
To: Kaushal Modi <kaushal.modi@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: Controlling new line characters during tangle
Date: Wed, 21 Jun 2017 13:22:23 +0200	[thread overview]
Message-ID: <CA+GKSr5u3RjTcN+xa1dF3y8t1FX=WDBUiUDRnK3Fs03YW7SRbw@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY3=p5T-NZG6woVt+hhm2z=RbBmthS8d8MHojib+pr4f4g@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]

Dear Kashual,

1. I visit a (Unix EOL[1]) org file on Windows.
2. I write a shell script in a shell source block to be tangled.
3. I tangle it.
4. As a result, I get a (Windows EOL) shell script, while I would like a
Unix EOL shell script.

Thanks,

Giacomo

[1] End Of Line convention

On Jun 21, 2017 13:02, "Kaushal Modi" <kaushal.modi@gmail.com> wrote:

> On Wed, Jun 21, 2017, 5:21 AM Giacomo M <jackjackk@gmail.com> wrote:
>
>> Hi all,
>>
>> I'm using emacs also under Windows, and would need to tangle
>> scripts/config files to be used under Unix.
>
>
> Is there any header argument
>> to enforce the desired new line characters in the tangled files?
>>
>
> At which point would you like to enforce the new line characters?
>
> Can you post a MWE and explain what that it tangles to vs what you'd
> actually like to see in the tangled file?
>
>> --
>
> Kaushal Modi
>

[-- Attachment #2: Type: text/html, Size: 2073 bytes --]

  reply	other threads:[~2017-06-21 11:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21  9:19 Controlling new line characters during tangle Giacomo M
2017-06-21 11:02 ` Kaushal Modi
2017-06-21 11:22   ` Giacomo M [this message]
2017-06-22  9:40   ` Giacomo M
2017-07-01 12:35     ` Nicolas Goaziou

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+GKSr5u3RjTcN+xa1dF3y8t1FX=WDBUiUDRnK3Fs03YW7SRbw@mail.gmail.com' \
    --to=jackjackk@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=kaushal.modi@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).