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


Groups > gnu.bash.bug > #15117

Re: alias problem -- conflict found

From L A Walsh <bash@tlinx.org>
Newsgroups gnu.bash.bug
Subject Re: alias problem -- conflict found
Date 2019-07-10 06:48 -0700
Message-ID <mailman.826.1562766596.2688.bug-bash@gnu.org> (permalink)
References <5D23C417.5060108@tlinx.org> <20190709132112.GW2450@eeg.ccf.org> <5D255A6E.4060600@tlinx.org> <e6845cba-fbc7-e195-aca5-9e4bc6a0df3a@case.edu> <5D25ECCA.3020400@tlinx.org>

Show all headers | View raw



On 2019/07/10 06:22, Chet Ramey wrote:
> On 7/9/19 11:24 PM, L A Walsh wrote:
>
>   
>> ----
>>     Why?  What makes clarity "horrible".  If someone didn't know shell's
>> way of assigning different attributes to 'declare', vs. most languages
>> having
>> different keywords or variable notations would be more familiar.
>>     
>
> Clarity is fine, but it's an individual thing, and requires additional
> context. If it makes things easier for you, great, but one of the things
> you have to sacrifice is the ability for other people to help you figure
> things out.
>
>   
If I submit something for other to look at, I usually have a key
at the top:

shopt -s expand_aliases
alias my=declare int='my -i '  array='my -a ' map='my -A

If they don't understand that, then I'd be skeptical of how much help
I'd be sacrificing.

Regardless, I use such things as a matter of health.  The fewer repetitive
characters I have to type, the better.

I find that using a small subset like the above is within the capabilities
of most shell programmers.

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


Thread

Re: alias problem -- conflict found L A Walsh <bash@tlinx.org> - 2019-07-10 06:48 -0700

csiph-web