On Tue 22.Sep'09 at 7:34:51 +0200, Johann Haarhoff wrote: > >> >> Hm, by this description I believe you also see directory names >> as auto-completion possibilities. But I don't. For me the >> new 'Run' dialog completion shows only the executables in >> my PATH... >> >> Am I missing something? > > OK, this is what happens on my computer with the latest version of next > (before my patch). > > Say I have a executable that is not in my path, it is in > /home/johann/installfiles/newprogram/src/newprogram > > So I bring up the Run dialog and I type: > > /ho<TAB> > > wmaker completes this to: > > /home > > then I type: > > /jo<TAB> > > wmaker completes this to: > > /home/johann > > etc.etc. until we get to: > > /home/johann/installfiles/newprogram/src/newprogram > > But after each completion I have to manually type the "/" to get it to > complete the next directory. > > After my patch I type: > > /ho<TAB> > > wmaker completes this to: > > /home/ (note the trailing slash) > > I type: > > jo<TAB> > > wmaker completes this to: > > /home/johann/ > > etc. etc. > > So yes, wmaker has always been able to complete directory names, all I > added is that directory names now have a trailing "/"; this does three > things, it > > 1) shows you that you are completing a directory and not a filename, > 2) saves one character of typing, and > 3) makes it behave more consistent with shell (bash) autocompletion
Thanks Johann! _Now_ I see the reason for your patch, and indeed it makes sense to put the trailing "/" in the way you use it. I will edit your original commit log to add some of the new info you provided below and push it to 'next'. ( Btw, I didn't even know that if you _start_ with "/" then the run dialog will autocomplete the dir names...) -- To unsubscribe, send mail to [email protected].
