From: Micah Elliott <mde@micahelliott.com>
To: TJ Luoma <luomat@gmail.com>
Cc: Zsh-Users List <zsh-users@zsh.org>
Subject: Re: Any way to have ".sh" be optional?
Date: Thu, 26 Sep 2013 14:27:11 -0700 [thread overview]
Message-ID: <CAELbujqMfX7Sgrr=JtJ8HZey6N4TwfyvS44J1XPvJJ3sOFs4=w@mail.gmail.com> (raw)
In-Reply-To: <CADjGqHsrd8K=rW6dyDxwddYMu-iG6tmNMMj0HtJZ6SVQksWmCw@mail.gmail.com>
On Thu, Sep 26, 2013 at 1:12 PM, TJ Luoma <luomat@gmail.com> wrote:
>
> I tend to name all of my Zsh scripts to end with '.sh' so I can easily
> `fgrep -i Whatever *.sh` when I'm looking for something.
Cool, I tend to use .zsh, but mostly so I know they're not system scripts.
> However, I would rather not have to type the ".sh" if not necessary. (Yes, I
> am that lazy.)
Leaving out the .«tab» saves a little bit of typing. But you might have
already fully tab-completed a couple chars in.
> is there a way to tell zsh "If I use the command 'foo' and there is no 'foo'
> but there is 'foo.sh' then I want to use 'foo.sh'?
You could tie into the command_not_found_hook (briefly mentioned in
zshmisc(1)). Something like this:
command_not_found_handler() {
actual=$@[1].sh
print "Proxying for actual: $actual"
for p in $path; do
if [[ -x $p/$actual ]]; then
$actual $@[2,-1]
break
fi
done
}
Then use:
% foo aa bb
Proxying for actual: foo.sh
<regular output>...
A couple caveats:
* I don't actually do this, but maybe I'll try; the func is not really
tested
* zsh syntax highlighting
(https://github.com/zsh-users/zsh-syntax-highlighting) won't match foo
* running in cwd as ./foo isn't handled
* not sure if looping over path is best approach; would something with
hash work?
--
twitter:@MicahElliott | email:mde@MicahElliott.com | http://membean.com
Remember your words with Membean!
next prev parent reply other threads:[~2013-09-26 23:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-26 20:12 TJ Luoma
2013-09-26 20:39 ` Jérémie Roquet
2013-09-26 21:27 ` Micah Elliott [this message]
2013-09-26 23:35 ` TJ Luoma
2013-09-26 21:40 ` Bart Schaefer
2013-09-26 23:18 ` TJ Luoma
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='CAELbujqMfX7Sgrr=JtJ8HZey6N4TwfyvS44J1XPvJJ3sOFs4=w@mail.gmail.com' \
--to=mde@micahelliott.com \
--cc=luomat@gmail.com \
--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).