* command line tabbing message '_arguments:comparguments:409: not enough arguments'
@ 2022-10-03 19:12 Jim
2022-10-04 3:43 ` Jun T
0 siblings, 1 reply; 4+ messages in thread
From: Jim @ 2022-10-03 19:12 UTC (permalink / raw)
To: devs
[-- Attachment #1: Type: text/plain, Size: 1039 bytes --]
HI everyone,
Messages when doing tab completion: (see subject line)
Disribution: devaun
Distribution zsh version: 5.8 -- at last check, still hasn't upgraded to
5.8.1 or 5.9
Local built versions: zsh-5.8.1-0-g1a490c7, zsh-5.9-0-g73d3173,
zsh-5.9-31-g7996fa5
After login, zsh version 5.8:
switching to 5.8.1: NO MESSAGES (% zsh-5.8.1)
switching from either 5.8 or 5.8.1 to 5.9* GET MESSAGE (% zsh-5.9 | %
zsh-5.9-31-dev)
After defaulting zsh to locally built version 5.9:
switching to the development version NO MESSAGES (% zsh-5.9-31-dev)
switching back to either 5.8 or 5.8.1: NEW MESSAGES(see below)
in this case tested both the system and locally built 5.8 version
(eval):setopt:3: no such option: NO_typesettounset
_arguments:comparguments:411: too many arguments
_description:zformat:89: invalid option: -F
NOTE: the completion still happens(hitting tab again), just get messages
QUESTION:
Is this a bug, or has something changed with the builds that I didn't
catch?
Regards,
Jim Murphy
[-- Attachment #2: Type: text/html, Size: 1473 bytes --]
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: command line tabbing message '_arguments:comparguments:409: not enough arguments'
2022-10-03 19:12 command line tabbing message '_arguments:comparguments:409: not enough arguments' Jim
@ 2022-10-04 3:43 ` Jun T
2022-10-04 4:36 ` Jun T
0 siblings, 1 reply; 4+ messages in thread
From: Jun T @ 2022-10-04 3:43 UTC (permalink / raw)
To: zsh-workers
> 2022/10/04 4:12, Jim <linux.tech.guy@gmail.com> wrote:
>
> After login, zsh version 5.8:
> switching to 5.8.1: NO MESSAGES (% zsh-5.8.1)
> switching from either 5.8 or 5.8.1 to 5.9* GET MESSAGE (% zsh-5.9 | % zsh-5.9-31-dev)
>
> After defaulting zsh to locally built version 5.9:
> switching to the development version NO MESSAGES (% zsh-5.9-31-dev)
>
> switching back to either 5.8 or 5.8.1: NEW MESSAGES(see below)
> in this case tested both the system and locally built 5.8 version
Please try the following:
% /path/to/zsh -f
% autoload -Uz compinit
% compinit
% echo $fpath
% cmd <TAB>
If this works OK then I guess something is wrong with your fpath/FPATH.
When using zsh-$version ($version is 5.9, 5.9.0-dev,..), fpath must include
$prefix/share/zsh/$version/functions/
This is version specific, and it is not a good idea to export FPATH.
If you have 'export FPATH' or such in your .zshrc/.zshenv then just remove it.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: command line tabbing message '_arguments:comparguments:409: not enough arguments'
2022-10-04 3:43 ` Jun T
@ 2022-10-04 4:36 ` Jun T
2022-10-04 7:55 ` Jim
0 siblings, 1 reply; 4+ messages in thread
From: Jun T @ 2022-10-04 4:36 UTC (permalink / raw)
To: zsh-workers
> 2022/10/04 12:43, I wrote:
> Please try the following:
>
> % /path/to/zsh -f
> % autoload -Uz compinit
> % compinit
> % echo $fpath
> % cmd <TAB>
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
% typeset -p FPATH
If it shows 'export ...' then it is exported. You can 'un-export' it
by 'typeset +x FPATH'. So you may try
% typeset +x FPATH
% /path/to/zsh
% echo $fpath
% cmd <TAB>
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: command line tabbing message '_arguments:comparguments:409: not enough arguments'
2022-10-04 4:36 ` Jun T
@ 2022-10-04 7:55 ` Jim
0 siblings, 0 replies; 4+ messages in thread
From: Jim @ 2022-10-04 7:55 UTC (permalink / raw)
To: Jun T; +Cc: devs
[-- 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 --]
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2022-10-04 7:56 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-10-03 19:12 command line tabbing message '_arguments:comparguments:409: not enough arguments' Jim
2022-10-04 3:43 ` Jun T
2022-10-04 4:36 ` Jun T
2022-10-04 7:55 ` Jim
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).