That would leave no way to execute the command as-is without accepting any
autocompletion. It would also be extremely shocking to any existing CLI user
that typing `some command here<enter>` would not actually run that command.
I feel pretty strongly that the behavior of <enter> should not be modified in
any fashion. If you want to accept suggestions, there are multiple ways to do
so (e.g. tab, ctrl-f).
-Kevin
On Apr 8, 2014, at 4:40 PM, Sylvain Benner <sylvain.ben...@gmail.com> wrote:
> I would just use <enter> to do partial auto-complete (on each word) and then
> still have to press <enter> one more time to execute the completed command.
> <shift><enter> could do the whole completion but another hit on <enter>
> should be required to execute the command.
>
> shell is a sensible domain, you cannot automate too much thing or bad things
> will happen. This is the same than vi modes in a file manager, you have to
> adapt it because file managers are sensible to mistakes.
>
> -syl20bnr-
>
>
> On Tue, Apr 8, 2014 at 7:14 PM, Goran Mekic <m...@lugons.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On Tue, Apr 08, 2014 at 06:39:55PM -0400, glphvgacs wrote:
> > what is the difference between that case and when the rest of the line
> > is *filled-in* by the suggestion engine then? users sees what's to be
> > executed and then hits the enter. i would argue that, in majority of
> > cases, it's safer to run commands from history to run then for the first
> > time since you have already run that command, this is the second time
> > and a quick check should suffice.
> The difference is that if I type <something> and hit <enter> I expect
> <something> to be executed, not
> <something><else-that-autocomplete-thinks-i-should-run>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.22 (GNU/Linux)
>
> iQEcBAEBAgAGBQJTRILGAAoJEGQ+3A6abaaCItkH/jgL+5XZi5Hzm+S2bEO5iXVZ
> JJtpR+Roz5ObFvT3+Fq6WpegLRpGwDg6MQKPPHBRORQAOyVuTZ5VeQ3n0I134zgK
> 5iC2k1frBL+GhWM82FGdqrIFLCg9p2QPiJQnJvdWeBqexVYuT9jKlkk/vLCwjUDJ
> 7rMqOq3pHZBvP/Jgzwr12LIcnRxhUr4vzGfewfQKeIXssmSTKpcWwz5WvOhRYmb5
> oKGK6pLqeFUHizuPGNA9CA3iyr9H7NUVmt8S7eMr9NykZrBG9dmpBlYnRHcZU8WR
> e9ZQPt1CEOB48+Rp3xQINMBedAzRb/X0lfCfwOqK5Ak7cFguISwW6+BH2qyRGyY=
> =3Dkn
> -----END PGP SIGNATURE-----
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees
> _______________________________________________
> Fish-users mailing list
> Fish-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/fish-users
>
> ------------------------------------------------------------------------------
> Put Bad Developers to Shame
> Dominate Development with Jenkins Continuous Integration
> Continuously Automate Build, Test & Deployment
> Start a new project now. Try Jenkins in the cloud.
> http://p.sf.net/sfu/13600_Cloudbees_______________________________________________
> Fish-users mailing list
> Fish-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/fish-users
------------------------------------------------------------------------------
Put Bad Developers to Shame
Dominate Development with Jenkins Continuous Integration
Continuously Automate Build, Test & Deployment
Start a new project now. Try Jenkins in the cloud.
http://p.sf.net/sfu/13600_Cloudbees
_______________________________________________
Fish-users mailing list
Fish-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fish-users
