zsh-workers
 help / color / mirror / code / Atom feed
From: Jim <linux.tech.guy@gmail.com>
To: Jun T <takimoto-j@kba.biglobe.ne.jp>
Cc: devs <zsh-workers@zsh.org>
Subject: Re: command line tabbing message '_arguments:comparguments:409: not enough arguments'
Date: Tue, 4 Oct 2022 02:55:28 -0500	[thread overview]
Message-ID: <CA+rB6GLYa6sB87qrGrM6m2TDbgKCzu8P-0Dntg0UxyiEK2KotQ@mail.gmail.com> (raw)
In-Reply-To: <C2CBE127-DE50-48CC-ABE2-CF444408FDEA@kba.biglobe.ne.jp>

[-- Attachment #1: Type: text/plain, Size: 896 bytes --]

On Mon, Oct 3, 2022 at 11:37 PM Jun T <takimoto-j@kba.biglobe.ne.jp> wrote:

>
> Sorry, if FPATH is exported then it is inherited by the child
> zsh even if it is started with option -f. So the above will not work.
>
> You can check whether FPATH is exported of not by
> If it shows 'export ...' then it is exported. You can 'un-export' it
>

Sorry, as soon as I saw "if FPATH is exported"  I figured out what was
happening.

My .zshrc file makes sure FPATH is exported.  This is because some
scripts/functions I
wrote failed if FPATH wasn't exported. So, I export it all the time. I
didn't consider what
this would do when switching shells.

I now have the following aliases:

  alias swshell='[[ $parameters[FPATH] == *export* ]] && typeset +x FPATH ;
'
  alias xportfpath='[[ $parameters[FPATH] == *export* ]] || typeset -x
FPATH'

Solved.  Sorry for the noise.

Thanks for you response,

Jim

[-- Attachment #2: Type: text/html, Size: 1454 bytes --]

      reply	other threads:[~2022-10-04  7:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03 19:12 Jim
2022-10-04  3:43 ` Jun T
2022-10-04  4:36   ` Jun T
2022-10-04  7:55     ` Jim [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=CA+rB6GLYa6sB87qrGrM6m2TDbgKCzu8P-0Dntg0UxyiEK2KotQ@mail.gmail.com \
    --to=linux.tech.guy@gmail.com \
    --cc=linuxtechguy@gmail.com \
    --cc=takimoto-j@kba.biglobe.ne.jp \
    --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).