Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: \r\n or \n line endings in make.bat?
Date: Tue, 22 Apr 2003 20:28:30 +0200	[thread overview]
Message-ID: <v9he8qs7xt.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <u65p9kamc.fsf@xpediantsolutions.com>

On Sun, Apr 20 2003, Kevin Greiner wrote:

> Frank Schmitt <usereplyto@Frank-Schmitt.net> writes:
>> Graham Murray <graham@gmurray.org.uk> writes:
>>> Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
>>>
>>>> What happens if Lars builds the nightly snapshot *.tar.gz or a
>>>> release on his Unix box with make.bat included with Unix line
>>>> terminators?  Will a windows user be able to execute make.bat
>>>> successfully?
>>>
>>> Windows should have no problem with unix line endings in make.bat

Probably you tried with cmd.exe (or however it's called) and not with
command.com.

>> Just tested it and it has problems. (It just doesn't work, because the
>> interpreter of Win 9x, command.com, thinks the file is one long line).
>> Make.bat _must_ be dos mode, and I'd also vote for flagging it binary.

[X] Done.

JFTR, this is what I did (I hope it's correct):

- $ cvs admin -kb make.bat
  $ cvs update -A make.bat

- Convert to DOS line terminators

- Do some (whitespace) changes (else CVS doesn't notice the change).

- Commit the file.

Frank, could you verify if it works for Win 9x (command.com) again?

> My concern was that I've run into more than one file with newlines
> applied inconsistently. [...]  We'll have to simply be diligent
> about correcting any errors that creep in.

When flagged as binary, Emacs should treat it as a DOS file and insert
the appropriate line terminators.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/




  reply	other threads:[~2003-04-22 18:28 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-16  6:36 [PATCH] Building in a cleaner environment for XEmacs Steve Youngs
2003-04-16  9:30 ` Frank Schmitt
2003-04-16 10:37   ` Steve Youngs
2003-04-16 13:54     ` [Patch] XEmacs args in make.bat (was: [PATCH] Building in a cleaner environment for XEmacs.) Frank Schmitt
2003-04-16 14:57       ` [Patch] XEmacs args in make.bat Reiner Steib
2003-04-16 21:43       ` Steve Youngs
2003-04-16 23:55         ` Kevin Greiner
2003-04-17 15:14           ` Reiner Steib
2003-04-18 13:36             ` Kevin Greiner
2003-04-18 20:48               ` \r\n or \n line endings in make.bat? (was: [Patch] XEmacs args in make.bat) Reiner Steib
2003-04-18 22:53                 ` \r\n or \n line endings in make.bat? Graham Murray
2003-04-19 20:10                   ` Frank Schmitt
2003-04-20  5:20                     ` Kevin Greiner
2003-04-22 18:28                       ` Reiner Steib [this message]
2003-04-23  4:27                         ` Kevin Greiner
2003-04-17  0:40 ` [PATCH] Building in a cleaner environment for XEmacs Katsumi Yamaoka
2003-04-17  7:45   ` Steve Youngs
2003-04-17  9:07     ` Katsumi Yamaoka

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

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

  git send-email \
    --in-reply-to=v9he8qs7xt.fsf@marauder.physik.uni-ulm.de \
    --to=4.uce.03.r.s@nurfuerspam.de \
    --cc=reiner.steib@gmx.de \
    /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.
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 NNTP newsgroup(s).