luish-extra

Extra material for luish.

Source: https://github.com/luispedro/luish-extra

Installing

In luish, add the repository (under any name, here extra), then enable all of its completion plugins:

$ plugin add luispedro/luish-extra extra
$ plugin add extra/completion/all

all loads bio, science, gui, dev, system, media and hpc. To have only some of them, enable them one by one instead (plugin add extra/completion/bio, …).

This needs luish 0.7.0 or later, and the plugins need std’s completion plugin.

What is supported lists the commands that are completed so far, and what to check when Tab doesn’t offer what you expect; Commands done and planned lists those planned too. Developing says how to add one.

The colour schemes are the plugin themes (plugin add extra/themes): see Colour schemes. The plugin conda sets conda up in interactive shells, cached (extra.conda = { options = { env = "ENV" } }): see conda. The plugin nvm does the same for nvm (extra.nvm = { options = { version = "node" } }): see nvm.

luish-extra is licensed under the MIT License, as luish is; the palettes of the colour schemes are their authors’, under their own licenses (see Colour schemes).

• What is supported
  • Programs that complete themselves
  • bio
  • science
  • gui
  • dev
  • system
  • media
  • hpc
  • When Tab doesn’t offer what you expect
• Commands done and planned
  • bio: bioinformatics
  • science: general scientific computing
  • gui: desktop programs
  • dev: development and deployment
  • system: system administration
  • media: audio, video and images
  • hpc: HPC clusters
  • Possible later plugins
• Colour schemes
  • Choosing one
  • What the colours say
  • Colours and terminals
  • Where the colours come from
• conda
  • Enabling it
  • What the cache depends on
• nvm
  • Enabling it
  • What the cache depends on
• Developing
  • Setting up
  • How a plugin is laid out
  • Adding a tool
  • Moving a generated module to a new version
  • Before committing