From: Ray Andrews <rayandrews@eastlink.ca>
To: zsh-users@zsh.org
Subject: Re: `whence -v X` shows file for functions, but not alias; workaround?
Date: Fri, 13 Jan 2017 10:18:43 -0800 [thread overview]
Message-ID: <dd3742ef-8b92-91fc-6f9b-ec85e33a9a86@eastlink.ca> (raw)
In-Reply-To: <alpine.LRH.2.00.1701122107080.4560@toltec.zanshin.com>
On 12/01/17 11:04 PM, Bart Schaefer wrote:
>
> And in 20+ years I don't think anyone else has asked about it, so ...
>
At one point I thought I wanted that too but after realizing that it
really was impossible
via internal methods I ended up just setting all my aliases within one
file named 'aliases'
and that was the end of the issue. Some times I can bend the shell to
my will but other
times I have to bend my will to the shell and often the latter ends up
being the better.
prev parent reply other threads:[~2017-01-13 18:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 17:24 Timothee Cour
2017-01-13 4:21 ` Eric Cook
2017-01-13 7:04 ` Bart Schaefer
2017-01-13 18:18 ` Ray Andrews [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=dd3742ef-8b92-91fc-6f9b-ec85e33a9a86@eastlink.ca \
--to=rayandrews@eastlink.ca \
--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).