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


Groups > gnu.bash.bug > #15117 > unrolled thread

Re: alias problem -- conflict found

Started byL A Walsh <bash@tlinx.org>
First post2019-07-10 06:48 -0700
Last post2019-07-10 06:48 -0700
Articles 1 — 1 participant

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

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

#15117 — Re: alias problem -- conflict found

FromL A Walsh <bash@tlinx.org>
Date2019-07-10 06:48 -0700
SubjectRe: alias problem -- conflict found
Message-ID<mailman.826.1562766596.2688.bug-bash@gnu.org>

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.

[toc] | [standalone]


Back to top | Article view | gnu.bash.bug


csiph-web