From: zzapper <david@rayninfo.co.uk>
To: zsh-users@zsh.org
Subject: Re: Function or Alias - Does it matter?
Date: Sun, 23 Nov 2014 22:35:09 +0000 (UTC) [thread overview]
Message-ID: <XnsA3EEE5C28605Cdavidrayninfocouk@80.91.229.13> (raw)
In-Reply-To: <CADjGqHuZpMyRCvEMivTZhW63Dk0wgSR8K+q0Whd_MhW57qB0Ag@mail.gmail.com>
>
> Is there any reason to prefer one or the other?
>
> Tj
My preference would be an alias especially since I can TAB complete it,
however when I need something a bit more complicated then it's got to be a
function.
You can comment functions etc
--
zzapper
https://twitter.com/dailyzshtip
---
This email has been checked for viruses by Avast antivirus software.
http://www.avast.com
prev parent reply other threads:[~2014-11-23 22:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-19 0:13 TJ Luoma
2014-11-19 0:45 ` James Pearson
2014-11-19 2:51 ` Bart Schaefer
2014-11-19 8:59 ` Oliver Kiddle
2014-11-23 22:35 ` zzapper [this message]
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=XnsA3EEE5C28605Cdavidrayninfocouk@80.91.229.13 \
--to=david@rayninfo.co.uk \
--cc=zsh-users@zsh.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).