Re: irepeat.el - repeat through history data FAST

Re: irepeat.el - repeat through history data FAST

[Richard Stallman]

Instead of defining a special function irepeat, could you do the job
by redefining keys in the minibuffer keymaps?  That way it would work
for all the command that read arguments in the minibuffer and would
not require redefining the individual commands.

If this is impossible for some reason, please explain the obstacle;
maybe we could change Emacs to remove the obstacle.

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel

Re: irepeat.el - repeat through history data FAST

[Kevin A. Burton]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard Stallman <rms@gnu.org> writes:

> Instead of defining a special function irepeat, could you do the job by
> redefining keys in the minibuffer keymaps?  That way it would work for all the
> command that read arguments in the minibuffer and would not require redefining
> the individual commands.
> 
> If this is impossible for some reason, please explain the obstacle; maybe we
> could change Emacs to remove the obstacle.
<snip/>

It is something I am thinking about.  I was thinking about building this but I
need to give it more thought.

I am not sure irepeat should modify the minibuffer to replace the standard
completion.

I also have to look into this and see how this would work.  ...

Kevin

- -- 
Kevin A. Burton ( burton@apache.org, burton@openprivacy.org, burtonator@acm.org )
             Location - San Francisco, CA, Cell - 415.595.9965
        Jabber - burtonator@jabber.org,  Web - http://relativity.yi.org/

In the end, only kindness matters.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt

iD8DBQE8nMyaAwM6xb2dfE0RApzGAJ9Y0mq+KKgz3t898eosZ5qx6jwaiwCgw2+Q
c9+ct69fnf8fz0nIyf3ZSD4=
=dNJU
-----END PGP SIGNATURE-----

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel

Re: irepeat.el - repeat through history data FAST

[Richard Stallman]

    I am not sure irepeat should modify the minibuffer to replace the standard
    completion.

That is the only clean way to do it.  That is the only way that avoids
the need to redefine individual commands that use the minibuffer.
That is the only way that works across the board.

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel

Re: irepeat.el - repeat through history data FAST

[Alex Schroeder]

Richard Stallman <rms@gnu.org> writes:

>     I am not sure irepeat should modify the minibuffer to replace
>     the standard completion.
>
> That is the only clean way to do it.  That is the only way that avoids
> the need to redefine individual commands that use the minibuffer.
> That is the only way that works across the board.

Hm, I actually thought that irepeat could be an alternative to or a
replacement for completing-read.  But often this does not make sense,
for example I have used irepeat for finding files -- but since irepeat
searches a list of strings for matches, the really existing files are
not used for completion, the file-name-history is.  In this case, how
would you want to augment find-file with irepeat?  I think this is not
possible.  It makes more sense when switching buffers, but for
switching buffers, we already have a gazillion ways to do it.  It
makes sense when completing symbols, I think, because the list of
symbols is easy to obtain and reasonably fast to search (unlike the
list of existing files).  Thus there perhaps, a transparent
replacement would be the right thing to do.

My point is, replacing standard completion is not that easy.  Or
perhaps you mean that irepeat should work just like icomplete-mode?
Perhaps that is the only "generic" way in which irepeat can be used.
It could be used in more powerful ways, though.  The finding of files
based on the history is one such example.  But these "better" ways of
doing things are difficult to get right, so it seems that you are
asking for the hardest part, first.

Maybe we should add it to Emacs, then let people offer ways to use it
(ie. write functions which use irepeat to do useful stuff), and
then let us consider wether we want to add those to Emacs.  BTW
irepeat comes with some examples, and some of these use the semantic
package which is not part of Emacs, yet.  So perhaps we just want to
take the core of irepeat and add it to Emacs instead of adding the
whole list of functions using it.  Thus we add irepeat and helpers,
which is an alternative to completing-read for elisp authors.  That
seems like a good first step to me.

Alex.
-- 
http://www.emacswiki.org/
Can anybody tell me what is going so dreadfully wrong in Palestine?

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel

Re: irepeat.el - repeat through history data FAST

[Kim F. Storm]

Alex Schroeder <alex@gnu.org> writes:

> Richard Stallman <rms@gnu.org> writes:
> 
> >     I am not sure irepeat should modify the minibuffer to replace
> >     the standard completion.
> >
> > That is the only clean way to do it.  That is the only way that avoids
> > the need to redefine individual commands that use the minibuffer.
> > That is the only way that works across the board.
> 
> Hm, I actually thought that irepeat could be an alternative to or a
> replacement for completing-read.  But often this does not make sense,
> for example I have used irepeat for finding files -- but since irepeat
> searches a list of strings for matches, the really existing files are
> not used for completion, the file-name-history is.  In this case, how
> would you want to augment find-file with irepeat? 

Have you tried ido.el available from www.cua.dk ?
It works like iswitchb.el for finding files.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk


_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel

Re: irepeat.el - repeat through history data FAST

[Kevin A. Burton]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

storm@cua.dk (Kim F. Storm) writes:

> Alex Schroeder <alex@gnu.org> writes:
> 
> > Richard Stallman <rms@gnu.org> writes:
> > 
> > >     I am not sure irepeat should modify the minibuffer to replace
> > >     the standard completion.
> > >
> > > That is the only clean way to do it.  That is the only way that avoids
> > > the need to redefine individual commands that use the minibuffer.
> > > That is the only way that works across the board.
> > 
> > Hm, I actually thought that irepeat could be an alternative to or a
> > replacement for completing-read.  But often this does not make sense,
> > for example I have used irepeat for finding files -- but since irepeat
> > searches a list of strings for matches, the really existing files are
> > not used for completion, the file-name-history is.  In this case, how
> > would you want to augment find-file with irepeat? 
> 
> Have you tried ido.el available from www.cua.dk ?  It works like iswitchb.el
> for finding files.

Yes... I added a comparison section which includes ido.el

;;; Competitors
;;
;; There are already a number of alternative completion packages available for
;; Emacs:
;;
;; - ido.el - Very different than irepeat.  It uses the standard completion but
;; then adds info within the minibuffer for all completions.
;;
;; - icomplete-mode.el - Included within emacs.  Very similar to ido and uses
;; completion but doesn't color the prompt like ido.
;;
;; - iswitch-buffer.el - Handles buffer switching the same way that ido.el does.
;; This metaphor is still totally different than irepeat.el
;;
;; - iswitchb.el - Similar to irepeat.  Displays all the options in the
;; minibuffer.  This is kind of information overload in a lot of respects.  IMO
;; this is too much information that is not formated. 

- -- 
Kevin A. Burton ( burton@apache.org, burton@openprivacy.org, burtonator@acm.org )
             Location - San Francisco, CA, Cell - 415.595.9965
        Jabber - burtonator@jabber.org,  Web - http://relativity.yi.org/

Failure to accept hypocrisy is the sign of a weak mind.
  - me
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt

iD8DBQE8n8cXAwM6xb2dfE0RAmrBAKCyF81ku2FMtX5Tbw3AasJ9DTO0VwCffPYr
gcRcIV2WAnxzc8gHU+hEjE8=
=G4n4
-----END PGP SIGNATURE-----

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel

Re: irepeat.el - repeat through history data FAST

[Richard Stallman]

    Hm, I actually thought that irepeat could be an alternative to or a
    replacement for completing-read.  But often this does not make sense,
    for example I have used irepeat for finding files -- but since irepeat
    searches a list of strings for matches, the really existing files are
    not used for completion, the file-name-history is.  In this case, how
    would you want to augment find-file with irepeat?

The completion facilities you add could have a switch so that they
disable themselves when file name completion is in use.
You can look at minibuffer-completing-file-name,
or at minibuffer-completion-table.

Please give it a try.


_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel

Re: irepeat.el - repeat through history data FAST

[Kevin A. Burton]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Richard Stallman <rms@gnu.org> writes:

>     Hm, I actually thought that irepeat could be an alternative to or a
>     replacement for completing-read.  But often this does not make sense,
>     for example I have used irepeat for finding files -- but since irepeat
>     searches a list of strings for matches, the really existing files are
>     not used for completion, the file-name-history is.  In this case, how
>     would you want to augment find-file with irepeat?
> 
> The completion facilities you add could have a switch so that they disable
> themselves when file name completion is in use.  You can look at
> minibuffer-completing-file-name, or at minibuffer-completion-table.
> 
> Please give it a try.

I plan on giving this a good looking over.  This is an area of Emacs that I
really don't spend much time in... give me a few weeks as I am busy right now.
I will get back to you.

Kevin

- -- 
Kevin A. Burton ( burton@apache.org, burton@openprivacy.org, burtonator@acm.org )
             Location - San Francisco, CA, Cell - 415.595.9965
        Jabber - burtonator@jabber.org,  Web - http://relativity.yi.org/

The invariable mark of wisdom is to see the miraculous in the common.
    - Ralph Waldo Emerson (1803-1882)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt

iD8DBQE8oDthAwM6xb2dfE0RAv9zAKCzOgQrT+5cnP37ksGtIvR9QphK+wCgprGS
vR2WVc0z4/8K3x3ngDvpHjg=
=enWF
-----END PGP SIGNATURE-----

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel

Re: irepeat.el - repeat through history data FAST

[Kevin A. Burton]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Alex Schroeder <alex@gnu.org> writes:

<snip/>

> I think, because the list of symbols is easy to obtain and reasonably fast to
> search (unlike the list of existing files).  Thus there perhaps, a transparent
> replacement would be the right thing to do.

A transparent replacemet would be great.
<snip/>

> Maybe we should add it to Emacs, then let people offer ways to use it
> (ie. write functions which use irepeat to do useful stuff), and then let us
> consider wether we want to add those to Emacs.  BTW irepeat comes with some
> examples, and some of these use the semantic package which is not part of
> Emacs, yet.  So perhaps we just want to take the core of irepeat and add it to
> Emacs instead of adding the whole list of functions using it.  Thus we add
> irepeat and helpers, which is an alternative to completing-read for elisp
> authors.  That seems like a good first step to me.

I would rather stabilize irepeat first.  It is too early to talk about making
this a standard part of emacs.

Thanks.

Kevin

- -- 
Kevin A. Burton ( burton@apache.org, burton@openprivacy.org, burtonator@acm.org )
             Location - San Francisco, CA, Cell - 415.595.9965
        Jabber - burtonator@jabber.org,  Web - http://relativity.yi.org/

For evil to win, is for good men to do nothing.
       - Winston Churchill.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: Get my public key at: http://relativity.yi.org/pgpkey.txt

iD8DBQE8osWJAwM6xb2dfE0RAvIpAKCUo12Rd2s/zvOmk6anaJG4meFgsgCeKlA2
aEZlvUvs94mvWboD4PyepQ4=
=2oY9
-----END PGP SIGNATURE-----

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel