#3662 seems to work well for me.

While testing it, I've encountered a couple of other related issues/observations (not caused by #3662). I'm not sure yet if we should qualify them as bugs or not.

I run micro -filetype go foo, do something, then open my init.lua in another tab (in order to add onBufferOptionChanged to test 93c11d6) -> my init.lua is suddenly highlighted all red, because its filetype is set to Go instead of Lua.
One may argue this is "expected behavior", but...
So I add onBufferOptionChanged to my init.lua:

function onBufferOptionChanged(buf, option, old, new)
    micro.InfoBar():Message("option ", option, " changed: ", old, " ", new)
end

and then when I execute micro -filetype go foo again, I get this:

Plugin initlua: init:267: attempt to index a non-table object(nil) with key 'Message'
stack traceback:
	init:267: in function <init:266>
	[G]: in function 'SetOption'
	ftoptions:8: in main chunk
	[G]: ?

Ok, I change it to:

function onBufferOptionChanged(buf, option, old, new)
    if micro.InfoBar() ~= nil then
        micro.InfoBar():Message("option ", option, " changed: ", old, " ", new)
    end
end

Now it doesn't throw the error anymore, but once micro started, I see this in the infobar:

option tabstospaces changed: true false

(again, triggered by the ftoptions plugin)

filetype command-line argument regression #3659

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions