| Age | Commit message (Collapse) | Author |
|---|
|
Problem: Lua build problem with old compiler.
Solution: Move declarations to start of the block. (Taro Muraoka,
closes #6477)
|
|
Problem: Cannot build with Lua 5.4.
Solution: Use luaL_typeerror instead defining it. (closes #6454)
|
|
Problem: Coverity warns for unsing unitialized field.
Solution: Initialize v_lock.
|
|
Problem: Insufficient test coverage for Lua.
Solution: Add tests. (Yegappan Lakshmanan, closes #6368) Fix uncovered
memory leak. Avoid unnecessary copy/free.
|
|
Problem: Lua: cannot use table.insert() and table.remove().
Solution: Add the list functions. (Prabir Shrestha, closes #6353)
|
|
Problem: Lua arrays are zero based.
Solution: Make Lua arrays one based. (Prabir Shrestha, closes #6347)
Note: this is not backwards compatible.
|
|
Problem: Cannot build with dynamic Lua.
Solution: Add dll variables.
|
|
Problem: Not so easy to pass a lua function to Vim.
Solution: Convert a Lua function and closure to a Vim funcref. (Prabir
Shrestha, closes #6246)
|
|
Problem: Not easy to require Lua modules.
Solution: Improve use of Lua path. (Prabir Shrestha, closes #6098)
|
|
Problem: ml_delete() often called with FALSE argument.
Solution: Use ml_delete_flags(x, ML_DEL_MESSAGE) when argument is TRUE.
|
|
Problem: Cannot build with Lua on MS-Windows.
Solution: Add DLL symbol for luaL_Loadstring. (Ken Takata)
|
|
Problem: Compiler warning for not using value in Lua.
Solution: Add "(void)".
|
|
Problem: Not easy to call a Vim function from Lua.
Solution: Add vim.call() and vim.fn(). (Prabir Shrestha, closes #6063)
|
|
Problem: Unloading shared libraries on exit has no purpose.
Solution: Do not unload shared libraries on exit.
|
|
Problem: Compiler warning in Lua interface.
Solution: Add type cast. (Ken Takata, closes #5621)
|
|
Problem: Maintaining a Vim9 branch separately is more work.
Solution: Merge the Vim9 script changes.
|
|
Problem: VAR_SPECIAL is also used for booleans.
Solution: Add VAR_BOOL for better type checking.
|
|
Problem: Using old C style comments.
Solution: Use // comments where appropriate.
|
|
Problem: Pressing "q" at the more prompt doesn't stop Python output. (Daniel
Hahler)
Solution: Check for got_int in writer(). (closes #5053)
Also do this for Lua.
|
|
Problem: Set_ref_in_list() only sets ref in items.
Solution: Rename to set_ref_in_list_items() to avoid confusion.
|
|
Problem: Not checking return value of ga_grow(). (Coverity)
Solution: Only append when ga_grow() returns OK.
|
|
Problem: Lua interface does not support Blob.
Solution: Add support to Blob. (Ozaki Kiichi, closes #4151)
|
|
Problem: Lua: may garbage collect function reference in use.
Solution: Keep the function name instead of the typeval. Make luaV_setref()
handle funcref objects. (Ozaki Kiichi, closes #4127)
|
|
Problem: Lua interface leaks memory.
Solution: Clear typeval after copying it.
|
|
Problem: Macros for MS-Windows are inconsistent, using "32", "3264 and
others.
Solution: Use MSWIN for all MS-Windows builds. Use FEAT_GUI_MSWIN for the
GUI build. (Hirohito Higashi, closes #3932)
|
|
Problem: Giving error messages is not flexible.
Solution: Add semsg(). Change argument from "char_u *" to "char *", also
for msg() and get rid of most MSG macros. (Ozaki Kiichi, closes
#3302) Also make emsg() accept a "char *" argument. Get rid of
an enormous number of type casts.
|
|
Problem: The Lua interface doesn't know about v:null.
Solution: Add Lua support for v:null. (Uji, closes #3744)
|
|
Problem: Missing support for Lua 5.4 32 bits on Unix.
Solution: Define lua_newuserdatauv. (Kazunobu Kuriyama)
|
|
Problem: Preferred cursor column not set in interfaces.
Solution: Set w_set_curswant when setting the cursor. (David Hotham,
closes #3060)
|
|
Problem: Lua API changed, breaking the build.
Solution: Adjust prototype of lua_rawgeti(). (Ken Takata,
closes #3157, closes #3144)
|
|
Problem: Static analysis errors in Lua interface. (Coverity)
Solution: Check for NULL pointers.
|
|
Problem: luaeval('vim.buffer().name') returns an error.
Solution: Return an empty string. (Dominique Pelle, closes #3167)
|
|
Problem: Lua interface does not support funcref.
Solution: Add funcref support. (Luis Carvalho)
|
|
Problem: W_WIDTH() is always the same.
Solution: Expand the macro.
|
|
Problem: FEAT_WINDOWS adds a lot of #ifdefs while it is nearly always
enabled and only adds 7% to the binary size of the tiny build.
Solution: Graduate FEAT_WINDOWS.
|
|
Problem: May get ml_get error when :luado deletes lines or switches to
another buffer. (Nikolai Pavlov, issue #1421)
Solution: Check the buffer and line every time.
|
|
Problem: Generated files are outdated.
Solution: Generate the files. Avoid errors when generating prototypes.
|
|
Problem: Looping over windows, buffers and tab pages is inconsistant.
Solution: Use FOR_ALL_ macros everywhere. (Yegappan Lakshmanan)
|
|
Problem: The versplit feature makes the code uneccessary complicated.
Solution: Remove FEAT_VERTSPLIT, always support vertical splits when
FEAT_WINDOWS is defined.
|
|
Problem: No support for JSON.
Solution: Add jsonencode() and jsondecode(). Also add v:false, v:true,
v:null and v:none.
|
|
Problem: Cannot use the "dll" options on MS-Windows.
Solution: Support the options on all platforms. Use the built-in name as
the default, so that it's clear what Vim is looking for.
|
|
Problem: When using Lua there may be a crash. (issue #468)
Solution: Avoid using an unitialized tv. (Yukihiro Nakadaira)
|
|
Problem: Libraries for dynamically loading interfaces can only be defined
at compile time.
Solution: Add options to specify the dll names. (Kazuki Sakamoto,
closes #452)
|
|
Problem: Can't specify when not to ring the bell.
Solution: Add the 'belloff' option. (Christian Brabandt)
|
|
Problem: Building with Lua 5.1 doesn't work.
Solution: Define lua_replace and lua_remove. (KF Leong)
|
|
Problem: Building with Lua 5.3 doesn't work, symbols have changed.
Solution: Use the new names for the new version. (Felix Schnizlein)
|
|
Problem: Can't build with Lua 5.3 on Windows.
Solution: use luaL_optinteger() instead of LuaL_optlong(). (Ken Takata)
|
|
Problem: Returning 1 in the wrong function. (Raymond Ko)
Solution: Return 1 in the right function (hopefully).
|
|
Problem: luaV_setref() not returning the correct value.
Solution: Return one.
|
|
Problem: luaV_setref() is missing a return statement. (Ozaki Kiichi)
Solution: Put the return statement back.
|
