kikito / ansicolors.lua Goto Github PK

It's something very minor, in the usage section the third print raises an error because of "underlined" instead of "underline".

I agree completely that LuaRocks releases should be automated; mine are! See for example luaposix/luaposix's Makefile.am, and note that because you use LuaRocks's built-in build system you don't need the "foo-release" branch bit, so the code will be that bit simpler. Do ask if I can help.

hey, very nice lua file.
im trying to use this in neovim lua configuration.

but when trying to print this:

local colored = require("ansi-colors")


function copy_current_line_to_clipboard()
	vim.cmd("execute 'normal \"+yy'")
	print(colored("%{red}line copied to clipboard%{reset}"))
end

nnoremap("<C-c>", "<cmd> lua copy_current_line_to_clipboard()<CR>")
inoremap("<C-c>", "<C-o><cmd> lua copy_current_line_to_clipboard()<CR>")

i get this:

i've tested the file in my terminal:

with this:

local colored = require("ansi-colors")
print(colored("%{red}line copied to clipboard%{reset}"))

so the plugin works.

apparently, vim cannot display ansi codes.

how do i make neovim display ansi codes in command-line area?

Windows has gained suppprt for ANSI sequences (since 2019, a specific release of 2010 added it).

• ANSI sequences are available
• might not be enabled by default
• Windows API function setconsolemode() can be used to enable it
• It can also be enabled by using os.execute as a workaround

So imho the behaviour of this library should be adjusted. But it is slightly problematic I think;

• enabling colors on Windows by default is breaking behaviour
• on Posix it is assumed that the caller of the library wants to use colors (since there are no checks whatsoever, eg using an isapty function to detect a pty)
• so enabling color by default on Windows would make sense... though support for it might not be enabled...

So I see 2 options:

• follow Posix behaviour and enable colors by default, if the caller doesn't want colors, then just don't use the lib.
  • Caller is responsible for proper checks and balances, as well as setup.
  • Lines up best with the Posix behaviour
  • breaking
• enable colors, but make the calls to enable color support (using an external lib to call setconsolemode or use the os.execute workaround.
  • Doing the setup for the caller.
  • less breaking
  • Responsibilities are different from Posix (since caller doesn't do the setup)

wdyt?