Re: [ELPA] New package: transient

[조성빈]

> 2020. 5. 3. 오전 3:58, Drew Adams <address@hidden> 작성:
> 
> 
>> 
>>>> is it `multibyte-string-p` or `string-multibyte-p`,
>>>> `file-name-absolute-p` or `absolute-file-name-p`, ... ?
>>> Then "C-u C-h a WORDS..." is your friend.
>> 
>> Nope, way too slow.  I shouldn't have to do anything
>> more than `str-mul TAB`.
> 
> In Icicles I type `C-h f str S-SPC mul',
> and I get these candidates (all from vanilla Emacs):
> 
> article-strip-multiple-blank-lines  (command)
> gnus-article-strip-multiple-blank-lines  (command) 
> gnus-multi-decode-encoded-word-string
> multibyte-string-p 
> read-multilingual-string
> string-as-multibyte 
> string-make-multibyte
> string-to-multibyte

Yes, and the fact that there are functions from gnus is a problem — the user 
only wanted a function that handles strings, but there is no such way to encode 
that in search with the current naming scheme.

> And `C-h f file S-SPC abs' gives these (plus some
> Icicles and Dired+ functions):
> 
> file-name-absolute-p
> files--name-absolute-system-p 
> tramp-use-absolute-autoload-file-names
> 
> `S-SPC' lets you combine multiple patterns, with
> no regard to the order of their matches in a
> candidate.  Matching patterns `file' and `abs'
> doesn't care which match comes first in the
> function name.
> 
> (If you don't like to use `S-SPC' (and so be able
> to match candidates that have SPC chars in them)
> then just change that key to `SPC', comma, or
> whatever.)
> 
>> BTW: I started doing that back in Emacs-21 with
>> the newcomment.el package which tried to stick
>> to the "comment-" prefix even for things which
>> previously used a different name.
> 
> Oh, like `comment-make-bol-ws', `comment-quote-re',
> `comment-string-strip', `comment-string-reverse',
> and `comment-with-narrowing', which seem to have
> nothing particular to do with comments, except that
> they happen to be used to implement some code that
> handles comments?
> 
> A package prefix is one thing.  A prefix that
> advertises the type of thing that a function works
> with is another thing.  Just what is the prefix
> `comment-', here?
>