From: Aryn Starr <whereislelouch@icloud.com>
To: Daniel Shahaf <d.s@daniel.shahaf.name>
Cc: zsh-workers@zsh.org
Subject: Re: [Feature Request] Add ability to define functions as noglob
Date: Thu, 15 Aug 2019 20:03:21 +0430 [thread overview]
Message-ID: <99E84896-AC85-4643-AE83-9BAF2463D40B@icloud.com> (raw)
In-Reply-To: <89238b4d-d051-4b86-b76b-3ebb70134b09@www.fastmail.com>
[-- Attachment #1: Type: text/plain, Size: 1154 bytes --]
1. Any function getting urls or math expressions (code expressions in general, in fact) is much more useable with noglob. And I have quite a few of such functions.
2. Probably an option set by oh-my-zsh is changing my which. I don’t want to disable such an option, though, since I greatly benefit from it.
Another point I forgot; Aliases are generally not as good as functions, since you need to define the alias before you can use it. This introduces incidental complexity and a need to manage what came before what.
> On Aug 15, 2019, at 7:55 PM, Daniel Shahaf <d.s@daniel.shahaf.name> wrote:
>
> Aryn Starr wrote on Thu, 15 Aug 2019 14:54 +00:00:
>> A lot of functions need to be noglob.
>
> Why? What's the use-case? Maybe noglob isn't the right tool for the job.
>
>> My current workflow is to define the function as `function sth-raw()`
>> and then `alias sth='noglob sth-raw'`. (I use different names so that
>> I can use `which sth-raw` to easily inspect the source.)
>
> You don't need to use different names. «which foo» would only expand
> «foo» if it were a global alias, which in your case it isn't.
>
>
prev parent reply other threads:[~2019-08-15 15:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 14:53 Aryn Starr
2019-08-15 15:25 ` Daniel Shahaf
2019-08-15 15:33 ` Aryn Starr [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=99E84896-AC85-4643-AE83-9BAF2463D40B@icloud.com \
--to=whereislelouch@icloud.com \
--cc=d.s@daniel.shahaf.name \
--cc=zsh-workers@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).