On Wed, 16 Aug 2006 at 11:08am, Eddy Zhao wrote:
- 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.
Eddy,
Thanks for the extensive testing. I now uploaded it as version 1.2 to
vim.org:
http://www.vim.org/scripts/script.php?script_id=1581
It should be same as what you already have.
--
Thanks,
Hari
On Wed, 16 Aug 2006 at 5:46pm, Eddy Zhao wrote:
On Wed, 16 Aug 2006 at 11:08am, Eddy Zhao
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
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
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
- 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)
Hari:
Could you upload the pervious version plugin? The latest version
plugin always generate error message after I restart lookupfile window
Thanks
Eddy
2006/8/16, Eddy Zhao [EMAIL PROTECTED]:
- Sometimes, the following error msg popup when open file thru lookupfile
(after that
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 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
Hi Hari:
I tested the new plugin, most new features works as expected. Some
problems found,
see comments below:
- Backspace will delete the whole path, it's better it delete the
directory path
back only to the previous path delimiter
- Press TAB, delete path to parent directory, find
On Sun, 13 Aug 2006 at 11:42pm, Eddy Zhao wrote:
Hi Hari:
I tested the new plugin, most new features works as expected. Some
problems found,
see comments below:
- Backspace will delete the whole path, it's better it delete the
directory path
back only to the previous path delimiter
Give the new version a try, I uploaded it to the below URL:
http://haridara.googlepages.com/lookupfile.zip
Here are the improvements for LUWalk command:
- g:LookupFile_AlwaysAcceptFirst setting to always accept the first
entry (set it to 1, the default is 0).
- g:LookupFile_FileFilter to
Hi Hari:
I detailed compared ido.el and lookupfile.vim today, below are some
of the ido features that I personally think more convenient than the
current
lookupfile plugin:
- Ido don't need user to generate update tagfile (and don't have things
like LookupFile_MinPatLength and performance
I had some trouble but I was able to try ido.el. At first, emacs that
came with cygwin didn't start at all, even when I had X running, so I
downloaded it separately from gnu.org. I installed ido.el directly under
lisp directory, as I don't know how to put it in a user directory. Next
I had
Hi Hari:
I tried the new plugin. Excellent! Exactly what I want. There are
several missing features I think could make lookupfile even more
effecient useful. Can you evaluate these features also ?
- include opened buffer as matching target (ido feature)
- order matching files by mru first,
On 8/8/06, Eddy Zhao [EMAIL PROTECTED] wrote:
Hi Yakov,
Thanks for the prompt help. I tried the lookupfile plugin,
looks great at first glance, can you throw light on the below
problems I encountered
- do I always have to generate tagfile for every directory i visited?
if so, I feel
On Wed, 9 Aug 2006 at 1:02am, Eddy Zhao wrote:
Hi Yakov,
Thanks for the prompt help. I tried the lookupfile plugin,
looks great at first glance, can you throw light on the below
problems I encountered
- do I always have to generate tagfile for every directory i visited?
if so, I
On 8/9/06, Hari Krishna Dara [EMAIL PROTECTED] wrote:
I am not completely clear on your question. You can always generate a
single tag file which includes all the directories that you would visit.
Normally, for development branches, this is easy as you can generate the
tag file right at the root
Hari Krishna Dara wrote:
On Wed, 9 Aug 2006 at 1:02am, Eddy Zhao wrote:
Hi Yakov,
Thanks for the prompt help. I tried the lookupfile plugin,
looks great at first glance, can you throw light on the below
problems I encountered
- do I always have to generate tagfile for every directory i
On Wed, 9 Aug 2006 at 10:49pm, Yakov Lerner wrote:
On 8/9/06, Hari Krishna Dara [EMAIL PROTECTED] wrote:
I am not completely clear on your question. You can always generate a
single tag file which includes all the directories that you would visit.
Normally, for development branches, this
Hi,
Does anyone ever used ido.el in emacs? (www.cua.dk/ido.el)
The plugin could considerably speedup file accessing performance,
especially when I'm maintaining a large wiki docbase. So I really
want to know
- if vim have equivalent plugin like ido.el
- if not, is there any simple way to
On 8/8/06, Eddy Zhao [EMAIL PROTECTED] wrote:
Hi,
Does anyone ever used ido.el in emacs? (www.cua.dk/ido.el)
The plugin could considerably speedup file accessing performance,
especially when I'm maintaining a large wiki docbase. So I really
want to know
- if vim have equivalent plugin like
Hi Yakov,
Thanks for the prompt help. I tried the lookupfile plugin,
looks great at first glance, can you throw light on the below
problems I encountered
- do I always have to generate tagfile for every directory i visited?
if so, I feel its a big burden that prevent me using the plugin
Hello,
* On Tue, Aug 08, 2006 at 09:46:28PM +0800, Eddy Zhao [EMAIL PROTECTED] wrote:
The plugin could considerably speedup file accessing performance,
especially when I'm maintaining a large wiki docbase. So I really
want to know
- if vim have equivalent plugin like ido.el
- if not, is
* On Wed, Aug 09, 2006 at 01:02:54AM +0800, Eddy Zhao [EMAIL PROTECTED] wrote:
- It seems that I can't locate file named aaabbb thru directly typing
bbb, do I always have to locate file begin with the first letter of
the filename?
If, as I guess, its implementation relies on the same
24 matches
Mail list logo
