| Commit message (Collapse) | Author | Age |
... | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This adds support for the ANSI x3.64 "bright" colors in the basic sixteen
color palette. This is especially useful when trying to use the base colors
as a background color. The "bright" variants tend to be more useful as
background colors compared to the non-bright variants.
This also fixes a bug in so far as palette number 7 is actually grey and
not white whereas palette number 15 is white. At least on the terminal
emulators on which I've tested this change (Ubuntu xterm & uxterm, Mac
OS X Terminal & iTerm2).
Resolves issue #1464.
|
|/ /
| |
| |
| |
| |
| |
| | |
* Add more options to `git cherry-pick` so that the suggested options
mimic the man page (https://www.git-scm.com/docs/git-cherry-pick/).
Signed-off-by: mr.Shu <mr@shu.io>
|
| |
| |
| |
| |
| |
| |
| | |
Adds support for the man-db alias format used in CentOS/RHEL 5
Adds basic support for the output of apropos on Solaris
Work on #2087.
|
| |
| |
| |
| | |
Should fix the build at least partly on msys2.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
|\ \
| | |
| | | |
git: Improve completion for git remote
|
|/ /
| |
| |
| |
| |
| |
| |
| |
| |
| | |
* Make sure that the `git remote` subcommands are not repeatedly
suggested (that is do not suggest a subcommand if there already is one).
* Add both long and short options to `git remote` subcommands where
appropriate.
Signed-off-by: mr.Shu <mr@shu.io>
|
|\ \
| | |
| | | |
git: Add missing remote subcommands completion
|
|\ \ \
| | |/
| |/| |
Added completions for cat, cp, mktemp, stat, touch for OS X.
|
| | | |
|
| | |
| | |
| | |
| | | |
Closes #2321
|
| |/
|/|
| |
| |
| |
| |
| |
| | |
* Add completion for missing `git remote` subcommands.
* Should fix #2567
Signed-off-by: mr.Shu <mr@shu.io>
|
| | |
|
| |
| |
| |
| | |
Closes #2322
|
| | |
|
| | |
|
|/ |
|
|
|
|
|
|
| |
This was subtle because `type` invoked seq.
Fixes #2570
|
|
|
|
|
| |
As always, this not only doesn't support longopts, but also has some
options that GNU rm doesn't - in this case, an undelete function.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This does a number of things:
- Removing trailing space from suggested repos for hg.
- Use the string builtin for hg completions.
- Add more internal merge tools to hg completion.
- Enable completions for abbreviated hg commands.
- Stop completing a deprecated hg branches option.
- Properly match the hg subcommand when preceeded by global switches.
- Stop completing deprecated hg glog.
- Complete hg config instead of showconfig.
- Properly complete when global switches are before the hg command.
- Properly handle the repository switch for hg completions.
- Properly handle the hg global switch cwd.
|
| |
|
| |
|
|
|
|
|
|
| |
See #2537.
These were written from the online versions of the manpages.
|
|
|
|
|
|
| |
This is an issue with 15-year old versions of bc that don't support BC_LINE_LENGTH.
Closes #2548
|
| |
|
|
|
|
|
|
|
| |
A bit simplistic since we can't complete e.g. regexes properly, but it
does the job.
Fixes #2543
|
|\
| |
| | |
Fix a doc typo
|
|/ |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We identify when the universal variable file has changed out from under us by
comparing a bunch of fields from its stat: inode, device, size, high-precision
timestamp, generation. Linux aggressively reuses inodes, and the size may be
the same by coincidence (which is the case in the tests). Also, Linux
officially has nanosecond precision, but in practice it seems to only uses
millisecond precision for storing mtimes. Thus if there are three or more
updates within a millisecond, every field we check may be the same, and we are
vulnerable to the ABA problem. I believe this explains the occasional test
failures.
The solution is to manually set the nanosecond field of the mtime timestamp to
something unlikely to be duplicated, like a random number, or better yet, the
current time (with nanosecond precision). This is more in the spirit of the
timestamp, and it means we're around a million times less likely to collide.
This seems to fix the tests.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Currently if there is a conflict with two manpages having the same
name, one completion will override the other. But if one can be parsed
and the other can't the one with parsed results will always have a
higher priority.
|
|
|
|
|
|
|
| |
It seems smart to only let files be parsed that are clearly
manpage files. Other files wouldn't be openend by man so
I think it is safe to guess that only these files are man
pages.
|
|
|
|
|
| |
On my system (OS-X 10.11) references to builtin are denoted by:
".so man1/builtin.1". So you also need to check against that.
|
|
|
|
|
|
|
|
|
|
| |
input_mapping_execute, when passed false for allow_commands, will return
R_NULL. However currently it does this unconditionally, even if we don't
have any commands. This defeats our read-ahead optimization, so we
always read and process one byte at a time. This caused pasting to be
much slower.
Fixes #2215
|
|
|
|
|
|
|
|
| |
If we are cd'ing into a directory, and the directory has only one
child which is itself a directory, the autosuggestion should
descend as far as it can.
Fixes #2531
|
|
|
|
|
|
|
| |
This makes them {forward,backward}-char instead of -word, which means
they accept suggestions _fully_.
Fixes #2255
|
|
|
| |
Added apt-get changelog sub-command completion.
|
| |
|
|
|
| |
fish_default_key_bindings.fish comments were wrong. Corrected comment about pagination.
|
|
|
|
| |
This is mentioned in the documentation, so keep it for now.
|
|
|
|
| |
This will also accept any autosuggestion completely.
|
|
|
|
| |
rustc.fish makes heavy use of the `string` commands.
|