On 3/5/07, Martin Baehr <[EMAIL PROTECTED]> wrote:
> On Mon, Mar 05, 2007 at 01:55:24PM -0600, Myrddin Emrys wrote:
> > I dunno. The fact that it displayed the text, and re-displayed the command
> > line, is a pretty blunt stick indicating that there was no match. In
> > particular, you'll see the list of matching files for the new match
> > listed... if that doesn't send up warning signals (assuming they're not what
> > you wanted to delete), it's hard to imagine what would.
>
> good point.
> but that would not happen if there is only a single completion.
> unless an extra indication is given that it happened.
> and i like the idea with the color change of the letters that change
> case.

I haven't been very active in this discussion because of various real
life issues, including the fact that I will present my licenthiate
thesis tomorrow, but I am reading all entries with interest.

If I were to summarize the above discussion, it would read something like this:

* It might be acceptable to change the commandline string, but if that
happens the change _must_ be somehow marked on the commandline.
* The commandline string must only be changed if there is only one
single way in which it can be changed.
* It might be acceptable to only support case insensitive completions
on non-wildcarded strings for now.

The functionality above is pretty realistic to implement and seems
like a pretty reasonable tradeoff to me. There _will_ be some
situations where fish will change the commandline in undesirable ways,
but they should be rare and easy to spot. The behaviour is (in my
opinion) simple enough to be predictable while smart enough to do what
you want most of the time. Arguments against the above are extra
welcome.

On a side not, the functionality above would suddenly make it _much_
more desirable to implement undo/redo functionality.

>
> greetings, martin.
> --
> cooperative communication with sTeam      -     caudium, pike, roxen and unix
> offering: programming, training and administration   -  anywhere in the world
> --
> pike programmer   working in new zealand        open-steam.org|webhaven.co.nz
> unix system-      bahai.or.at                        iaeste.(tuwien.ac|or).at
> administrator     (caudium|gotpike).org                          is.schon.org
> Martin Bähr       http://www.iaeste.or.at/~mbaehr/
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Fish-users mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/fish-users
>


-- 
Axel

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Fish-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/fish-users

Reply via email to