First Last Prev Next    No search results available      Search page      Enter new bug
Bug#: 83824
Alias:
Product:
Component:
Status: RESOLVED
Resolution: FIXED
Assigned To: Mamoru KOMACHI (RETIRED) <usata@gentoo.org>
Hardware:
OS:
Version:
Priority:
Severity:
Reporter: Calum Selkirk <cselkirk@xs4all.nl>
Add CC:
CC:
URL:
Summary:
Status Whiteboard:
Keywords:

Filename Description Type Creator Created Size Actions
Create a New Attachment (proposed patch, testcase, etc.) View All

Bug 83824 depends on: Show dependency tree
Bug 83824 blocks:
Votes: 0    Show votes for this bug    Vote for this bug

Additional Comments: (this is where you put emerge --info)


Not eligible to see or edit group visibility for this bug.






View Bug Activity   |   Format For Printing   |   XML   |   Clone This Bug


Description:   Opened: 2005-03-02 07:58 0000
This isn't so much a bug with zsh-completion (it could happen with any third
party completions).

The problem is this: If you happen to compile your functions (zcompile). Then
the functions added by zsh-completion will not be made available to your shell,
that is until you delete .zcompdump{.zwc} and recompile. 

With zsh-completion installed and site-fucntions in my $fpath the new
completions were not recognized until I had deleted .zcompdump{.zwc}, restarted
the shell and recompiled the .z*.{zwc}

Similarly to the update from (if my memory is correct) zsh 4.1 to 4.2 there is
very little that the package manager could do in this regard, but it's maybe a
good idea to add this to the README or to pass this information to the user
during install in the form of and einfo.

------- Comment #1 From Mamoru KOMACHI (RETIRED) 2005-04-05 21:51:50 0000 -------
Thanks for your suggestion. I added einfos to zsh-completion ebuilds.
If you notice any other things to improve zsh packages, please
let me know :)

First Last Prev Next    No search results available      Search page      Enter new bug