Project Name | Stars | Downloads | Repos Using This | Packages Using This | Most Recent Commit | Total Releases | Latest Release | Open Issues | License | Language |
---|---|---|---|---|---|---|---|---|---|---|
Typescript Styled Plugin | 825 | 185 | 193 | 2 months ago | 38 | December 06, 2021 | mit | JavaScript | ||
TypeScript server plugin that adds intellisense to styled component css strings | ||||||||||
Atom Ternjs | 641 | 3 years ago | 119 | mit | JavaScript | |||||
JavaScript code intelligence for atom with tern.js and autocomplete-plus | ||||||||||
Compleat | 433 | 6 months ago | 12 | Haskell | ||||||
Generate command-line completions using a simple DSL. | ||||||||||
Compliment | 336 | 10 | 3 months ago | 42 | February 23, 2019 | 16 | epl-1.0 | Clojure | ||
The Clojure completion library you deserve | ||||||||||
Autocomplete Python | 245 | a year ago | 110 | gpl-2.0 | CoffeeScript | |||||
Jedi based Python autocomplete for Atom | ||||||||||
Racket Langserver | 208 | 2 months ago | 24 | other | Racket | |||||
Rnn Writer | 197 | 4 years ago | 1 | other | CoffeeScript | |||||
Package for the Atom text editor that provides responsive, inline "autocomplete" powered by a recurrent neural network. | ||||||||||
Atom Racer | 118 | 6 years ago | 32 | mit | CoffeeScript | |||||
Intelligent code completion for Rust in the Atom Editor. Requires Racer. | ||||||||||
Atom Ide Purescript | 115 | 3 years ago | 20 | mit | PureScript | |||||
Atom package for PureScript build, completion, etc support | ||||||||||
Sugartex | 73 | 3 | 2 | 3 years ago | 13 | January 21, 2019 | 3 | mit | Python | |
SugarTeX is a more readable LaTeX language extension and transcompiler to LaTeX. Fast Unicode autocomplete in Atom editor via https://github.com/kiwi0fruit/atom-sugartex-completions |
Generate tab completion for any shell command by specifying its usage in a
familiar manpage-like format. For example, a usage specification for
top(1)
:
top [-b | -c | -H | -i | -s | -S | -d <delay> | -n <num> | -p <pid> ...] ... ;
top (-h|-v)
Supported shells are bash
, fish
, and zsh
.
Get the source code: git clone git://github.com/mbrubeck/compleat.git
Next, install Stack.
To install Compleat in your system, run:
make install
This will install the compleat
binary into ~/.local/bin
and the
compleat_setup
script into ~/.bash_completion.d
.
To enable compleat in bash, add the following line to your .bashrc
.
(Adjust the path if you configured with a custom prefix.)
source ~/.bash_completion.d/compleat_setup
and install your .usage files in a directory named /etc/compleat.d
or
~/.compleat
:
mkdir ~/compleat
cp examples/* ~/compleat
Restart your shell to begin using completions:
exec bash
zsh support requires zsh >= 4.2.1, and currently uses zsh's bash-compatibility mode rather than taking advantage of zsh's extended completion features.
To enable compleat in zsh, make the following change to your .zshrc
.
(Adjust the path if you configured with a custom prefix.)
If you used the zsh wizard (zsh-newuser-install) to set up your zshrc
, it should contain lines
like the following (if they don't exist, simply add the lines in the change below):
autoload -Uz compinit
compinit
Change these to:
autoload -Uz compinit bashcompinit
compinit
bashcompinit
source ~/.bash_completion.d/compleat_setup
and install your .usage files in a directory named /etc/compleat.d
or
~/.compleat
:
sudo mkdir /etc/compleat.d
sudo cp examples/* /etc/compleat.d
Restart your shell to begin using completions:
exec zsh
To install the fish completion file, run:
make install-fish
To enable compleat in fish, add the following line to your ~/.config/fish/config.fish
.
source ~/.config/fish/compleat_setup.fish
and install your .usage files in a directory named /etc/compleat.d
or
~/.compleat
:
mkdir ~/compleat
cp examples/* ~/compleat
Restart your shell to begin using completions:
exec fish
Type top
and then press Tab a few times to see the example files in action.
A usage file contains commands and definitions, separated by semicolons.
A command consists of a command name followed by a pattern. The command name can be any atom. If there is more than one command in the file, compleat will attempt to match each of them against the input line.
An atom consists of letters, numbers, and any of the characters -_/@=+.,:
,
or any string enclosed in double quotes with C/Java-style backslash escapes.
The following are valid patterns:
foo
matches the string foo
. "x\\y"
matches
the string x\y
.a b
matches a
followed by b
.a b | c
matches either a b
or c
.[a]
matches zero or one occurrences of a
.a ...
matches one or more occurrences of a
.[a] ...
matches zero or more occurrences of a
.Use parentheses to group patterns:
a (b | c)
matches a
followed by either b
or c
.(a | b) ...
matches a
or b
followed by any number of additional
a
or b
.Patterns may also include variables:
name = value;
defines a new variable. The name can be any atom,
and the value can be any pattern. Then <name>
in a pattern refers to the
value as a sub-pattern.
name = !command;
defines a variable that uses a shell command to
generate suggested completions. The shell command should print one
suggested completion per line. The $COMP_LINE
and $COMP_CWORD
environment will contain the input line and the current word being
completed.
If no value is defined for name
, then the pattern <name>
will match any
word.
Copyright (c) 2009 Matt Brubeck
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.