The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: davida@pobox.com (David Arnold)
Subject: [TUHS] Windows Notepad to support Unix line endings
Date: Fri, 11 May 2018 12:16:26 +1000	[thread overview]
Message-ID: <303AF181-6500-4ECC-BAE8-4D839D6CB8CF@pobox.com> (raw)
In-Reply-To: <1cfffd7b-4490-7ebc-d892-b603d8312f9d@spamtrap.tnetconsulting.net>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1172 bytes --]

The upside for me as someone who packages software for Windows is that I can have README.txt, LICENSE.txt, etc, files in the Windows package and they’ll work out of the box for people who haven’t done the reconfiguration dance you describe.

Previously, I’ve had to run unix2dos on all the text files in the Windows package.

So in a few years when I stop supporting anything older than Windows-10.whatever-this-one-is-called, I’ll be able to simplify my packaging scripts slightly.

As you say … not really worthy of the hype.



d


> On 10 May 2018, at 08:23, Grant Taylor via TUHS <tuhs at minnie.tuhs.org> wrote:
> 
> On 05/09/2018 03:57 PM, David Arnold wrote:
>> Double-click on a .txt file will invoke Notepad, unless you’ve reconfigured things.
> 
> Right-click on a .txt file
> Left-click on Open With
> Left-click on Wordpad
> (Optionally) Left-click on "always use this program…"
> 
> Sure, it's a preference change.  But it's a user level preference.
> 
> Is it nice that Notepad will now open files with unix new lines?  Sure.
> 
> Do I think it's worth some of the hype that I'm seeing?  Nope.
> 
> 
> 
> -- 
> Grant. . . .
> unix || die
> 



  parent reply	other threads:[~2018-05-11  2:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-09 20:15 Robert Diamond
2018-05-09 21:54 ` Grant Taylor
2018-05-09 21:57   ` David Arnold
2018-05-09 22:23     ` Grant Taylor
2018-05-09 23:08       ` Nemo
2018-05-09 23:10         ` Nemo
2018-05-09 23:28         ` Grant Taylor
2018-05-10 13:34           ` Nemo
2018-05-10 15:24             ` Grant Taylor
2018-05-11  2:16       ` David Arnold [this message]
2018-05-11  2:21         ` Grant Taylor
2018-05-09 22:30   ` Arthur Krewat
2018-05-09 22:54     ` Larry McVoy
2018-05-10 21:09     ` Dave Horsfall
2018-05-10 21:21       ` arnold
2018-05-10 21:47       ` Harald Arnesen
2018-05-10 21:49       ` Clem Cole
2018-05-10 22:59         ` Grant Taylor
2018-05-11  0:35           ` Warner Losh
2018-05-11  1:29           ` Theodore Y. Ts'o
2018-05-11 13:09             ` Clem Cole
2018-05-10 23:13         ` Wesley Parish
2018-05-09 22:41   ` Tim Bradshaw
2018-05-10  0:32 Norman Wilson
2018-05-10  1:10 ` Grant Taylor
2018-05-12 11:51 Rudi Blom

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=303AF181-6500-4ECC-BAE8-4D839D6CB8CF@pobox.com \
    --to=davida@pobox.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.
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).