On Tue, 15 Aug 2006 at 8:35pm, Eddy Zhao wrote: > Hi Hari: > > Problem reported yesterday > > - "calling LookupNotifyFunc prematurely" problem seems solved > > - "path is very long" problem seems solved > > Problem found today (using the new plugin) > > - Without "set shellslash", open one file manually, open lookupfile window, > the path's backward slash is not replaced by forward slash
This is because you are using a custom command that passed an initial path with backslashes. The plugin now takes care of this as well. > - Sometimes, the following error msg popup when open file thru lookupfile > (after that file is opened successfully). The problem can't be reproduced > everytime (and can't find out how to reproduce it, I haven't seem > this problem > when using the previous version plugin) > > Error detected while processing function > <SNR>55_OpenCurFile..<SNR>15_LookupReset: > line 10: > E31: No such mapping > E31: No such mapping I can't reproduce this. David Fishburn reported the same error as something that gets generated while using the <C-B>, so I tried it with several variations with no success. I put in some trace which will give more information, so hopefully I can figure out something the next time it happens to you. > - Sometimes, after I open one file manually, and then open lookupfile window, > directory path is not updated with the newly opened file's path. > The problem can't be > reproduced everytime (and can't find out how to reproduce it, > previous version plugin > also have this problem) The path is not based on the latest file, but the buffer that you are currently in. This is how ido seems to behave. Try ido with two split windows containing files from different directory. The path that it starts with is set to the directory of the file the current window contains. If you want files from current directory (getcwd()), then you can just start typing (don't press <Tab>). > New feature request > > - Directory in showed in directory-content-window is postfixed by > "/", but the "/" is > too far from the path name. It might be more eye easy to postfix > directory name with > "/" directly after it. This is how it was before, and I removed it as I thought it is redundant to show the separator in both the name and the "kind" field. I am now showing in both places and it doesn't seem to clutter. > > Thanks > Eddy Please try the new version again, and let me know if you continue to see the error messages (with a copy of the messages) http://haridara.googlepages.com/lookupfile.zip -- Thanks, Hari > > 2006/8/15, Hari Krishna Dara <[EMAIL PROTECTED]>: > > > > On Mon, 14 Aug 2006 at 9:02pm, Eddy Zhao wrote: > > > > > Hi Hari: > > > > > > Problems reported yesterday > > > > > > - Put the "set shellslash" in vimrc solves most of the backward-slash > > problems. > > > May be it's worth mention in the plugin doc. > > > > I think a better option is to replace backslashes with forwardslashes in > > the plugin itself. If <Tab> inserted path with the right slashes, you > > wouldn't have faced this problem, so this is a bug in lookupfile. > > > > > - I can't reproduce the "Press TAB, C-b, find a lot of error message" > > > problem today, > > > I'll report the problem when I find the way to reproduce it. > > > > Thanks. > > > > > - MRU.vim provide history to files (not buffers) recently used. It is > > > especially > > > useful in switching between serveral frequently accessed > > > directories (even between > > > vim sessions). Combined with current lookupfile, user can locate > > > file even more > > > effeciently. > > > > I looked at this plugin. It doesn't provide any interface to access this > > list programmatically, so we need to somehow get this patched up. > > > > > Problems find today > > > > > > - When path is very long (exceed screen width), find > > > directory-content-window's filelist is messed up > > > > This seems to be a bug in completion. As a workaround, I am going to > > enable 'wrap' in this buffer. This seems to avoid the problem, though > > you will not then utilize the screen real estate properly. > > > > > - Input wrong path, RETURN, find input focus is automatically move to > > > the line beginning. It's more desirable that the input focus remain at > > > line end to facilitate user correct the last path segment > > > > > > - Input wrong path, RETURN, move to line end and delete the last path > > > segment, input correct path segment keyword, find popup-match-window > > > not showup > > > > > > - Input wrong path, RETURN, move to line end and delete the last path > > > segment, input intact correct path segment (not path keyword), RETURN, > > > find an empty buffer opened (instead of popup > > > directory-content-window) > > > - Sometimes, the following error msg popup serveral times when open > > > file thru lookupfile (after that file is opened successfully). The > > > problem can't be reproduced everytime (and can't find out how to > > > reproduce it) > > > > > > Error detected while processing function > > > <SNR>74_AcceptFile..<SNR>33_IdoAccept..lookupfile#AcceptFile: > > > line 15: > > > E121: Undefined variable: g:LookupFile_LookupNotifyFunc > > > > All the above problems are due to calling LookupNotifyFunc prematurely, > > which is doing an internal reset. I now moved the call to a different > > location, and now it will reset only when the validation has already > > been done. > > > > > My vimrc configuration is > > > > > > command! WalkCur :exec "LUWalk" expand('%:p:h').'/' > > > nmap <unique> <silent> w :WalkCur<CR> > > > nmap <unique> <silent> b :LUBufs<CR> > > > let g:LookupFile_PreserveLastPattern=0 > > > let g:LookupFile_AlwaysAcceptFirst=1 > > > let g:LookupFile_FileFilter = > > > '\.class$\|\.o$\|\.obj$\|\.exe$\|\.jar$\|\.zip$\|\.war$\|\.tgz$\|\.ear$' > > > > > > Thanks > > > Eddy > > > > Thanks for your feedback. I now updated the version at the below URL, so > > please give it another try: > > > > http://haridara.googlepages.com/lookupfile.zip > > > > -- > > Thanks, > > Hari > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam protection around > > http://mail.yahoo.com > > > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
