With my longest:full,full setting I don't have to delete anything, I just repeatedly hit the right-arrow key (or down-arrow to descend into directories); if there are too many matches I can get an overview by hitting Ctrl-D instead of <Tab>, then type something more specific once I know what the choices are.
Best regards, Tony. On Wed, May 9, 2018 at 12:25 PM, Christian Brabandt <[email protected]> wrote: > > On Mi, 09 Mai 2018, Tony Mechelynck wrote: > >> So what's the problem? > > It is confusing and the chance that the first full match is actually the > one wanted by the user is lesser, the more matches there are. > > This is a random example from my current system. It might differ if you > have those files not available. Try to edit this file on linux¹: > sp /usr/include/linux/netfilter/xt_time.h > > Vim stops completing at directory boundaries (good, but already the > linux is completed to libdrm (after typing li<tab>), which is wrong). > But after typing x<tab> it will complete to x_tables.h and i have to > manually delete the t_time.h manually type "t<tab>" notice it is the > wrong match again (xt_AUDIT.h), manually delete again the _AUDIT.h, type > _t<tab> (completes to xt_tcpmss.h), delete it again and so on. By that > time I am better off, manually typeing the whole path (at least if I do > not make a typo). So in that case the whole filetype completion did not > help me. > > Now consider a case where you have many long filenames that only differ > slightly by some numbers or letters. It makes completion so much painful > because you have to stare carefully at your commandline. > > Yes I know about c_CTRL-D but I am just to used to typing <tab> from the > shell, and it stops automatically when it can't find a unique match. > > ¹) diretory looks like this here: > ipset xt_CONNMARK.h xt_comment.h xt_multiport.h > nf_conntrack_common.h xt_CONNSECMARK.h xt_connbytes.h xt_nfacct.h > nf_conntrack_ftp.h xt_CT.h xt_connlabel.h xt_osf.h > nf_conntrack_sctp.h xt_DSCP.h xt_connlimit.h xt_owner.h > nf_conntrack_tcp.h xt_HMARK.h xt_connmark.h xt_physdev.h > nf_conntrack_tuple_common.h xt_IDLETIMER.h xt_conntrack.h xt_pkttype.h > nf_log.h xt_LED.h xt_cpu.h xt_policy.h > nf_nat.h xt_LOG.h xt_dccp.h xt_quota.h > nf_tables.h xt_MARK.h xt_devgroup.h xt_rateest.h > nf_tables_compat.h xt_NFLOG.h xt_dscp.h xt_realm.h > nfnetlink.h xt_NFQUEUE.h xt_ecn.h xt_recent.h > nfnetlink_acct.h xt_RATEEST.h xt_esp.h xt_rpfilter.h > nfnetlink_compat.h xt_SECMARK.h xt_hashlimit.h xt_sctp.h > nfnetlink_conntrack.h xt_SYNPROXY.h xt_helper.h xt_set.h > nfnetlink_cthelper.h xt_TCPMSS.h xt_ipcomp.h xt_socket.h > nfnetlink_cttimeout.h xt_TCPOPTSTRIP.h xt_iprange.h xt_state.h > nfnetlink_log.h xt_TEE.h xt_ipvs.h xt_statistic.h > nfnetlink_queue.h xt_TPROXY.h xt_l2tp.h xt_string.h > x_tables.h xt_addrtype.h xt_length.h xt_tcpmss.h > xt_AUDIT.h xt_bpf.h xt_limit.h xt_tcpudp.h > xt_CHECKSUM.h xt_cgroup.h xt_mac.h xt_time.h > xt_CLASSIFY.h xt_cluster.h xt_mark.h xt_u32.h > > > > Best, > Christian > -- > Wer aus dem Rahmen fällt war vorher nicht unbedingt im Bilde. > > -- > -- > You received this message from the "vim_dev" maillist. > Do not top-post! Type your reply below the text you are replying to. > For more information, visit http://www.vim.org/maillist.php > > --- > You received this message because you are subscribed to the Google Groups > "vim_dev" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
