From: "Bart Schaefer" <schaefer@candle.brasslantern.com>
To: zsh-workers@sunsite.auc.dk
Subject: Re: #compdef -k menu-select glitch in 3.1.9
Date: Tue, 6 Jun 2000 17:52:11 +0000 [thread overview]
Message-ID: <1000606175211.ZM726@candle.brasslantern.com> (raw)
In-Reply-To: <200006060948.LAA08623@beta.informatik.hu-berlin.de>
On Jun 6, 11:48am, Sven Wischnowsky wrote:
} Subject: Re: #compdef -k menu-select glitch in 3.1.9
}
} Bart Schaefer wrote:
}
} > Should we stick a `(( $+functions[$_i_file] )) && continue' or equivalent
} > into the `for _i_file in ...' loop in compinit?
}
} Or make compinit tell the user about such things and add an option to
} make it be quiet
That won't do it for me, as I want to have both versions of the function
around. It should get the right one.
} (that reminds me of the security checks you suggested
} for loading the completion system; I got no reply to my suggested
} patch in 11440).
Oh, I'm sorry, I thought I had replied.
11440 is the right idea, but I think the test should be for directories
or files that are writable by anyone other than root or the current user.
That means files not owned by the root or the current user fail, as do
files in any group or world writable directory, or in any directory not
owned by root or by the current user.
Then it needs three possibilities for how to treat failure of the tests:
(1) Ask whether to use the completion system.
(2) Silently ignore all directories and files that fail.
(3) Silently accept all directories and files in $fpath.
} > The other puzzler, with the beeping, still remains.
}
} That's because menu-select always returns zero, whereas the other
} completion widgets return 1 when listing and LISTBEEP is set.
But it isn't listing any more at the time of the beep! I get the beep
when I *exit* from menu selection with a choice, not when I *enter* menu
selection (which would make more sense from the listbeep standpoint).
} Hm, is it `correct' to make menu-select beep, too?
No.
} I don't have any opinion here since I don't let it beep at me at
} all... what do you want to have?
I don't believe menu selection should be considered a listing for the
purposes of listbeep, no matter how you got there; but if it is going to
be, then it ought to beep before and not after.
--
Bart Schaefer Brass Lantern Enterprises
http://www.well.com/user/barts http://www.brasslantern.com
Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net
next prev parent reply other threads:[~2000-06-06 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-06-06 9:48 Sven Wischnowsky
2000-06-06 17:52 ` Bart Schaefer [this message]
-- strict thread matches above, loose matches on Subject: below --
2000-06-06 4:56 Bart Schaefer
2000-06-06 5:16 ` Bart Schaefer
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=1000606175211.ZM726@candle.brasslantern.com \
--to=schaefer@candle.brasslantern.com \
--cc=zsh-workers@sunsite.auc.dk \
/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).