Gem completion and slow loading

[vcastellm]

Gem completion script makes each new terminal window take ages to load. Just deleting the symlink from enabled completions folder makes it load reasonable well.

[ghost]

Unfortunately it's not possible to make it any faster since bash_it needs to get a list of gems each time it loads the completion.

On Jul 24, 2011, at 11:48 AM, victorcoder wrote:

Gem completion script makes each new terminal window take ages to load. Just deleting the symlink from enabled completions folder makes it load reasonable well.

Reply to this email directly or view it on GitHub:
#73

[vcastellm]

Yes and I think it's preferably to not enable it by default because it can create a bad impression for new users.

[ghost]

I can't stop from enabling it by default. We automatically enable all completion plugins by default.

[tswicegood]

It might be worthwhile to add an exemption and/or allow the users to decide which ones they want to enable on tha first pass thru.

[ghost]

I might add something to the install script. Anyone else think this is a good idea? I was planning on adding something like this:

tell the user:

bash_it comes with tab-completion for the gem command. Using this requires it to download a list of gems which will make shell startup time slower. Would you like to enable this completion plugin? (Y/N)

[tswicegood]

I think it could be even simpler (from the user's perspective, not ours):

Would you like to enable all, some, or none of the [plugins|completion|aliases] (this may make bash_it run slower):
[All/Some/None]:

All continues to act as it currently does, Some prompts the user for each one, None skips the step all together.

[vcastellm]

Could be possible to make it like in omz? load just the list of commands and load gems list on demand

[ghost]

@tswicegood's idea looks like a good one. I'll try implementing it.

[ghost]

Fixed with 021000c.

[vcastellm]

It's an old commit, push pending?

[ghost]

Oh, sorry. Typo. Was fixed in 3eff6b2.

[vcastellm]

Oh, I think you were going to fix the gem completion file.

Selecting "some" drives through an endless process that I thinks it's not that great idea.

I'll try to help with this.

[tswicegood]

@mr-szymanski I was thinking more along the lines of moving the for loop into the while true loop so you would be asked for each type so you could enable all plugins, some aliases, and none of the completion, or so on.

[ghost]

Ahh, ok. I'll try that, then. Thanks.

[ghost]

Fixed with 159e1e4.