Re: completion-ignored-extensions

Stephen J Turnbull writes: Stephen> However what could be done easily enough (I think) is to create a Stephen> Custom "Variables That There Is No Consensus Default For" group. For Stephen> this kind of variable, if you wanted to add TeX extensions to the Stephen> ignored extensions, you would add a checkbox widget to its Custom Stephen> widget list. I'm not sure I understand you well there, but it seems that what you mean is something like what gnus does for some hooks (like gnus-group-mode-hook where you have a predefined toggle for gnus-topic-mode) ? I don't think that's quite the point however, because if you do this, there's still going to be a war on the question of knowing whether, say, the .idx toggle should be on or off by default. IMHO, adding a predefined toggle for it might be a convenience, but that's all. This problem actually makes me think of a more powerfull mechanism that could be nice to have: something like an extension priority sorting. What I'd actually like to have is the following: - C-x C-f <some text> - TAB <xemacs pops up a buffer with possible completions> - and then, successive TABs (which doesn't change the completions) complete the minibuffer with the possible values in an order that you have the possibility to customize. -- / / _ _ Didier Verna http://www.inf.enst.fr/~verna/ - / / - / / /_/ / E.N.S.T. INF C201.1 mailto:verna＠inf.enst.fr /_/ / /_/ / /__ / 46 rue Barrault Tel. (33) 01 45 81 73 46 75634 Paris cedex 13 Fax. (33) 01 45 81 31 19