Path: csiph.com!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Robert Elz <kre@munnari.OZ.AU>
Newsgroups: gnu.bash.bug
Subject: Re: Unicode range and enumeration support.
Date: Tue, 24 Dec 2019 21:21:22 +0700
Lines: 19
Approved: bug-bash@gnu.org
Message-ID: <mailman.1366.1577203281.1979.bug-bash@gnu.org>
References: <217b4a75-b79e-dc2a-a2b2-cc5133d7cbef@archlinux.org> <0ff3a920-94c2-b0c9-5631-0964955657aa@archlinux.org> <5DF3D78B.4090208@tlinx.org> <20191213184213.GO851@eeg.ccf.org> <5DF4BDF0.6000402@tlinx.org> <20191216163906.GV851@eeg.ccf.org> <5DFA7AE2.2060504@tlinx.org> <20191218194651.GH851@eeg.ccf.org> <5DFD68B9.3050202@tlinx.org> <2334eff4-8a88-18ee-b086-4ba4e80af01b@archlinux.org> <5E0128F0.5000901@tlinx.org> <20191223205826.GY851@eeg.ccf.org> <5E01A380.8000706@tlinx.org> <16043.1577197282@jinx.noi.kre.to>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
X-Trace: usenet.stanford.edu 1577203282 12856 209.51.188.17 (24 Dec 2019 16:01:22 GMT)
X-Complaints-To: action@cs.stanford.edu
Cc: bug-bash@gnu.org
To: Eli Schwartz <eschwartz@archlinux.org>
Envelope-to: bug-bash@gnu.org
In-Reply-To: <217b4a75-b79e-dc2a-a2b2-cc5133d7cbef@archlinux.org>
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic]
X-Received-From: 2001:3c8:9009:181::2
X-BeenThere: bug-bash@gnu.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports for the GNU Bourne Again SHell <bug-bash.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/bug-bash>
List-Post: <mailto:bug-bash@gnu.org>
List-Help: <mailto:bug-bash-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/bug-bash>, <mailto:bug-bash-request@gnu.org?subject=subscribe>
X-Mailman-Original-Message-ID: <16043.1577197282@jinx.noi.kre.to>
X-Mailman-Original-References: <217b4a75-b79e-dc2a-a2b2-cc5133d7cbef@archlinux.org> <0ff3a920-94c2-b0c9-5631-0964955657aa@archlinux.org> <5DF3D78B.4090208@tlinx.org> <20191213184213.GO851@eeg.ccf.org> <5DF4BDF0.6000402@tlinx.org> <20191216163906.GV851@eeg.ccf.org> <5DFA7AE2.2060504@tlinx.org> <20191218194651.GH851@eeg.ccf.org> <5DFD68B9.3050202@tlinx.org> <2334eff4-8a88-18ee-b086-4ba4e80af01b@archlinux.org> <5E0128F0.5000901@tlinx.org> <20191223205826.GY851@eeg.ccf.org> <5E01A380.8000706@tlinx.org>
Xref: csiph.com gnu.bash.bug:15776

    Date:        Tue, 24 Dec 2019 00:47:40 -0500
    From:        Eli Schwartz <eschwartz@archlinux.org>
    Message-ID:  <217b4a75-b79e-dc2a-a2b2-cc5133d7cbef@archlinux.org>

  | What is "recent" about sort -u? I can find it listed as a mandatory
  | option in the POSIX 2004 manual.

The -u option appaeared in 7th edition Bell Labs Unix (1979) [I would
assume it was actually implemented somewhat earlier, that's when 7th
edition was released to the rest of the world.]

Also note that sort -u and sort | uniq are not quite the same, the -u
option only considers the key fields when deciding which records (lines)
are unique (of course, with no key options, the whole line is the key,
in which case they are more or less the same).

kre