Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #15113

Re: alias problem -- conflict found

Path csiph.com!xmission!news.snarked.org!news.linkpendium.com!news.linkpendium.com!panix!usenet.stanford.edu!not-for-mail
From Pierre Gaston <pierre.gaston@gmail.com>
Newsgroups gnu.bash.bug
Subject Re: alias problem -- conflict found
Date Wed, 10 Jul 2019 14:09:53 +0200
Lines 39
Approved bug-bash@gnu.org
Message-ID <mailman.808.1562760610.2688.bug-bash@gnu.org> (permalink)
References <5D255A6E.4060600@tlinx.org> <5D23C417.5060108@tlinx.org> <20190709132112.GW2450@eeg.ccf.org> <10340.1562742284@jinx.noi.kre.to> <5D25D398.7010300@tlinx.org> <CAPSX3sQeAPHYvwHB6DFvFR1Ur=5WDWLj7HXgRO06UksyrcTPyQ@mail.gmail.com>
NNTP-Posting-Host lists.gnu.org
Mime-Version 1.0
Content-Type text/plain; charset="UTF-8"
X-Trace usenet.stanford.edu 1562760610 5895 209.51.188.17 (10 Jul 2019 12:10:10 GMT)
X-Complaints-To action@cs.stanford.edu
Cc Robert Elz <kre@munnari.oz.au>, bug-bash@gnu.org
To L A Walsh <bash@tlinx.org>
Envelope-to bug-bash@gnu.org
DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ac5ZrzMML++EqYaVEHZZVdk/qwCYazxlzXgIyChndvo=; b=QvOB7q5fOYp4GtvNt9/LVePWKA8MbeRmaNFb4xPDnTcoHu3QtF/ljv91J7D9M/d+IK Ocp6Q8pICjskB1zguD7mSS4HP3q8v8nxrkH6pdF03uo5O+KBC5Mf8BVymYcso28iBLZs 4eax66Mr9vF4bsPCHDNlHx+RdqeGzUQnb6vIxW0nfVIgIE0oQlMNwbFAS9lLveoCq50S AKSYjxVHhlsXPD2HxxTpx8ZwTZpmMLZsVIDOgn0oII9YVrVr0UtGKlvd01C45N6piNhB 8dJjtPztIDZWscpCJki5QMgxNF2toM8s0TZPGY+axkyaOuyeq9AgXDFF9VKoGSrnqwcV LKiA==
X-Google-DKIM-Signature v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ac5ZrzMML++EqYaVEHZZVdk/qwCYazxlzXgIyChndvo=; b=fvfVhQRa5fTqoHw1fEmrxndgQc5IQPlETcT8POWIFq7xtSM8IFCmGo+35iJgWYxf02 +TpZqzfpimHqbtK7KaNTA4L4WQGDbgM5YGtShNxTlVhe4ikgPZupogOn5SGk0tu6PLHj HxJWsu8k61PD7Yuien1eXKydWEn/w6oW5a3Xcv/+W02STxmnm89wxFX9TfClyBMeapxY tbTpaU4SE72JRpx5ivCnLwAKR7PMqTwPJ7vYHtwvJvdiJpZ7Gv/UZy4Wzdgfsymnb3pJ b+vqr0POGXc0pXOvievREmIcttWrBjCr2TYCaqbzBjoAPyxddTb8pT+WEN3YBg+6TAYG QOYQ==
X-Gm-Message-State APjAAAXbg+hRIKvU06+sShQQlxShn3pPeErG0jR5jiI5kWuJhzaNRLRs g+PbnwZDHDGEw3ujbqYmyNzRzPCcD0pRo/NGdgEQ4HyrrpA=
X-Google-Smtp-Source APXvYqy3YKOLQsAzENJldSbUTrXsnx+KP2O5madXgPCkdKZIKTos1vuQINV6A2TcUni3SLU0pZZQrnDV4rfznLrEa0Q=
X-Received by 2002:aed:2d83:: with SMTP id i3mr23769481qtd.368.1562760604300; Wed, 10 Jul 2019 05:10:04 -0700 (PDT)
In-Reply-To <5D25D398.7010300@tlinx.org>
X-detected-operating-system by eggs.gnu.org: Genre and OS details not recognized.
X-Received-From 2607:f8b0:4864:20::829
X-Content-Filtered-By Mailman/MimeDel 2.1.23
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 <CAPSX3sQeAPHYvwHB6DFvFR1Ur=5WDWLj7HXgRO06UksyrcTPyQ@mail.gmail.com>
X-Mailman-Original-References <5D255A6E.4060600@tlinx.org> <5D23C417.5060108@tlinx.org> <20190709132112.GW2450@eeg.ccf.org> <10340.1562742284@jinx.noi.kre.to> <5D25D398.7010300@tlinx.org>
Xref csiph.com gnu.bash.bug:15113

Show key headers only | View raw


On Wed, Jul 10, 2019 at 2:03 PM L A Walsh <bash@tlinx.org> wrote:

>
>
> On 2019/07/10 00:04, Robert Elz wrote:
> >     Date:        Tue, 09 Jul 2019 20:24:30 -0700
> >     From:        L A Walsh <bash@tlinx.org>
> >     Message-ID:  <5D255A6E.4060600@tlinx.org>
> >
> >   |     Why?  What makes clarity "horrible".
> >
> > It isn't the clarity (if you call it that, it is really obscurity
> > as no-one else can read your scripts/commands and have any idea
> > what they really do) but the using of aliases that way to achieve it.
> >
> I doubt that.
>

Steven Bourne did the same tricks in C, and it lead to the creation of the
The International Obfuscated C Code Contest

https://www.ioccc.org/faq.html

Q: How did the IOCCC get started?
A: One day (23 March 1984 to be exact), back Larry Bassel and I (Landon
Curt Noll) were working for National Semiconductor's Genix porting group,
we were both in our offices trying to fix some very broken code. Larry had
been trying to fix a bug in the classic Bourne shell (C code #defined to
death to sort of look like Algol) and I had been working on the finger
program from early BSD (a bug ridden finger implementation to be sure). We
happened to both wander (at the same time) out to the hallway in Building
7C to clear our heads.

We began to compare notes: ''You won't believe the code I am trying to
fix''. And: ''Well you cannot imagine the brain damage level of the code
I'm trying to fix''. As well as: ''It more than bad code, the author really
had to try to make it this bad!''.

....

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread


Thread

Re: alias problem -- conflict found Pierre Gaston <pierre.gaston@gmail.com> - 2019-07-10 14:09 +0200

csiph-web