Sessions help

[kalvinpearce]

I am trying to move over to this plugin from startify but having trouble getting sessions to work. This bit of the readme leads me to think sessions should show up somehow but I am not able to see them using either of the themes. Sorry if I missed something but just a bit confused 🙏

[goolord]

no, i haven't made any gui for sessions yet.
i'm missing feature parity with startify simply because i never used some of the features :p
i can look into it the next time i get the time/motivation to work on this plugin, if you want to submit a pr it shouldn't be too difficult tbh

[adrian5]

What's the intent behind mentioning sessions (and neovim-session-manager) in the README though? I found that confusing as well. Are they supported in some capacity?

[goolord]

because some people on reddit mentioned that they use startify for session management https://github.com/mhinz/vim-startify/blob/master/doc/startify.txt#L81-L92

i didn't even know that they would appear on the startify screen until this issue was opened

[adrian5]

Ah I see. Yeah, would be nice if the startify-like session listing could be implemented in the future.

[bennypowers]

can i prevent alpha from launching if a neovim-session-manager session exists?

[goolord]

in my experience having the sessions autoload will already do this, but I can add a configuration option to remove the VimEnter autocmd for creating an alpha buffer

[bennypowers]

Could we start by just adding a config flag which disables autorendering altogether, then it would be the user's job to define the autocmd?

alpha-nvim/lua/alpha.lua

Lines 586 to 589 in 4781fcf

	augroup alpha_start
	au!
	autocmd VimEnter * nested lua require'alpha'.start(true)
	augroup END

I can send a PR which migrates this snippet to the new lua API and only adds the autocmd if some config flag is present