When profiling (on 100,000 calls) with this test:
```lua
start_t = os.clock()
for i = 1, 100000 do
_ = home .. prefix
end
end_t = os.clock()
print(end_t - start_t)
```
I get on my computer this (warm):
os.getenv("HOME") 0.005506
str:gsub("^~", home) 0.009333
str:find("^~") 0.006041
str:sub(2) 0.005455
a .. b 0.003603
Difference between gsub and sub + .. seems negligible, but just
to make it correct, here we are.
---
Note to myself: attaching new patch to the old thread via --in-reply-to makes the patch lost.
lua/plugins/complete-filename.lua | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
I don't think it makes a difference whether it takes 5/100000 of a
second or 10/100000 of a second to run this check (and potentially the
substitution) each time ...
Since it doesn't make the code more complex, I'm ok with it though!
LGTM!
Cheers,
Silvan
diff --git a/lua/plugins/complete-filename.lua b/lua/plugins/complete-filename.lua
index 02b9f3a9..604361c2 100644
--- a/lua/plugins/complete-filename.lua+++ b/lua/plugins/complete-filename.lua
@@ -23,9 +23,10 @@ local complete_filename = function(expand)
end
-- Expand tilda for the home directory
- if prefix:find('^~') then+ _, j = prefix:find('^~')+ if j ~= nil then local home = assert(os.getenv("HOME"), "$HOME variable not set!")
- prefix = prefix:gsub("^~", home, 1)+ prefix = home .. prefix:sub(j + 1) end
local cmdfmt = "vis-complete --file '%s'"
Applied!
I agree with Silvan that its probably not a good use of time to go
looking in paths that are rarely called for such small
improvements. But I'm not going to let the work go to waste since
it was already done.
If I put you up to this based on some comment of mine I'm sorry
that wasn't my intention.
- Randy