aboutsummaryrefslogtreecommitdiffhomepage
Commit message (Collapse)AuthorAge
* git: Add missing remote subcommands completionGravatar mr.Shu2015-11-28
| | | | | | | | * Add completion for missing `git remote` subcommands. * Should fix #2567 Signed-off-by: mr.Shu <mr@shu.io>
* fish_tests.cpp: use temporary path for completion testsGravatar David Adam2015-11-27
| | | | Closes #2322
* Complete bg and fg with job PIDs.Gravatar Daniel Matz2015-11-27
|
* Add a function to complete job PIDs.Gravatar Daniel Matz2015-11-27
|
* Fix tab completion after '%' character.Gravatar Daniel Matz2015-11-27
|
* Remove circular dependency in fallback seqGravatar Fabian Homborg2015-11-27
| | | | | | This was subtle because `type` invoked seq. Fixes #2570
* Add completion for OSX rmGravatar Fabian Homborg2015-11-27
| | | | | 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.
* Update hg completionGravatar Daniel Matz2015-11-23
| | | | | | | | | | | | | | | 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.
* Add completions for OSX whichGravatar Fabian Homborg2015-11-23
|
* Add more sudo optionsGravatar Fabian Homborg2015-11-23
|
* Support the OSX versions of head/tailGravatar Fabian Homborg2015-11-19
| | | | | | See #2537. These were written from the online versions of the manpages.
* math: Join lines manuallyGravatar Fabian Homborg2015-11-19
| | | | | | This is an issue with 15-year old versions of bc that don't support BC_LINE_LENGTH. Closes #2548
* psub: add -s, --suffixGravatar Eugene Sharygin2015-11-14
|
* Add completion for stringGravatar Fabian Homborg2015-11-12
| | | | | | | A bit simplistic since we can't complete e.g. regexes properly, but it does the job. Fixes #2543
* Merge pull request #2539 from seethemhigh/docs-typosGravatar Fabian Homborg2015-11-10
|\ | | | | Fix a doc typo
| * Fix a doc typoGravatar seethemhigh2015-11-10
|/
* Upgrade Xcode project for newest XcodeGravatar ridiculousfish2015-11-09
|
* Remove duplicate \cw binding in default key bindingsGravatar ridiculousfish2015-11-08
|
* Attempt to fix the sporadic uvar test failures on LinuxGravatar ridiculousfish2015-11-08
| | | | | | | | | | | | | | | | | | 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.
* Fix key_reader make target.Gravatar Gordon Tyler2015-11-08
|
* Use unused cleanup_autogenerated_fileGravatar Alexander Hedges2015-11-08
|
* Remove autogenerated files before generating the new onesGravatar Alexander Hedges2015-11-08
| | | | | | | 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.
* Guard against files that don't end in .[1...9]Gravatar Alexander Hedges2015-11-08
| | | | | | | 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.
* Ignore references to builtin on the macGravatar Alexander Hedges2015-11-08
| | | | | 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.
* Make input_mapping_execute stop returning R_NULL too oftenGravatar ridiculousfish2015-11-07
| | | | | | | | | | 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
* Teach the cd autosuggestion how to descend "unique" hierarchiesGravatar ridiculousfish2015-11-07
| | | | | | | | 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
* vi-mode: Inherit \cf and \cb bindings as wellGravatar Fabian Homborg2015-11-06
| | | | | | | This makes them {forward,backward}-char instead of -word, which means they accept suggestions _fully_. Fixes #2255
* Improve apt-get completionGravatar maxried2015-11-01
| | | Added apt-get changelog sub-command completion.
* tests: try longer timeout in case setting fish_key_bindings is taking too longGravatar David Adam2015-10-30
|
* Update fish_default_key_bindings.fishGravatar maxried2015-10-29
| | | fish_default_key_bindings.fish comments were wrong. Corrected comment about pagination.
* vi-mode: Make \cb do backward-word againGravatar Fabian Homborg2015-10-28
| | | | This is mentioned in the documentation, so keep it for now.
* vi: Bind \cx to end-of-line in insert modeGravatar Fabian Homborg2015-10-28
| | | | This will also accept any autosuggestion completely.
* Add cargo and rustc completion.Gravatar Bheesham Persaud2015-10-26
| | | | rustc.fish makes heavy use of the `string` commands.
* Add ability to customize the amount of path shortening in prompt_pwdGravatar Gary Peck2015-10-26
| | | | Allows the length of each shortened path component to be customized by setting the `fish_prompt_pwd_dir_length` variable to the number of characters to include (plus a leading dot because that's special). Maintains the default behavior of shortening path components to just one character. You can also set `fish_prompt_pwd_dir_length` to an empty or invalid value or 0 to disable shortening completely.
* Make 'set -ql' search up to function scopeGravatar ridiculousfish2015-10-23
| | | | | | | | | | | | | Previously 'set -ql' would only look for variables in the immediate local scope. This was not very useful. It's also arguably surprising, since a 'set -l' in a function, followed by a 'set -ql' in a child block, would fail. There was also no way to check for a function-scoped variable, since omitting the scope would also pull in global variables. We could revisit this and introduce an explicit function scope. Fixes #2502
* Revert "reader.cpp: send carriage return after printing the window title"Gravatar ridiculousfish2015-10-21
| | | | | This fix introduced #2499 This reverts commit 13479fbc2a130d97caeb66f7f56fb89c6be8c489.
* Switch useradd and chsh to `string`Gravatar Fabian Homborg2015-10-21
|
* fish_complete_subcommand: shadow scope to inherit e.g. $PATHGravatar David Adam2015-10-21
| | | | Closes: #2141.
* Update mix completionGravatar Jan Ernsting2015-10-20
| | | | | | | Among others `mix escriptize` has not been supported since July 2014: https://github.com/elixir-lang/elixir/issues/2468 Also explain what mix is.
* git: Complete subcommands for git submodule foreachGravatar Fabian Homborg2015-10-20
|
* git: Disable submodule subcommand completion if one is already givenGravatar Fabian Homborg2015-10-20
|
* Fix git submodule completionsGravatar Fabian Homborg2015-10-20
| | | | Fixes #2494
* tests/bind.expect: re-enable but at human typing speed onlyGravatar David Adam2015-10-18
| | | | | | | The interactive bind tests work if the keys are treated like there is a human pressing them. This reverts commit 0006d23df82fd10c37acecc5a0fd578afb3be437.
* Disable the bind test for nowGravatar Fabian Homborg2015-10-18
| | | | | | | | | | This isn't pretty, but it fails for, as far as I can see, no _real_ reason. It doesn't seem to be possible to trigger the failure in real usage, no matter how fast you press the ESC key followed by something else. So now this is known and constant travis emails don't help it in any way.
* git completion: Allow branches with "/" in them as unique remote branchesGravatar Fabian Homborg2015-10-16
|
* reader.cpp: send carriage return after printing the window titleGravatar David Adam2015-10-16
| | | | | | | Terminals can get confused by all the non-printed characters about the line position. Closes #2453.
* Fix usage of history_filenameGravatar Jeff Kowalski2015-10-16
|
* Migrate fish_history from config to data dirGravatar Jeff Kowalski2015-10-16
| | | | | | | | | New implementation of migration code within the history_t class will copy the contents of the old fish_history found in the config directory to its new location in the data directory. The old file is left intact. This is done only in the event that a fish_history is not already found in the data directory ($XDG_DATA_HOME/fish or ~/.local/share/fish).
* Correct tests for new location of fish_historyGravatar Jeff Kowalski2015-10-16
| | | | | | | | The fish_history file is now located in the "data" directory ($XDG_DATA_HOME/fish or ~/.local/share/fish), accessible using the function `path_get_data`. (This commit also cleans trailing whitespace in the source file.)
* Access fish_history from $XDG_DATA_HOMEGravatar Jeff Kowalski2015-10-16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Add new functions path_get_data and path_create_data which parallel existing functions path_get_config and path_create_data. The new functions refer to XDG_DATA_HOME, if it is defined, or ./local/share if not. Modify history_filename to use the new function path_get_data. As a consequence, fish_history will now be located in XDG_DATA_HOME, not XDG_CONFIG_HOME. Note that these changes mirror what is already used in fish-shell/share/tools/create_manpage_completions.py, which stores the completions in XDG_DATA_HOME This change matches recommendations in the xdg basedir spec at http://standards.freedesktop.org/basedir-spec/basedir-spec-0.7.html ($XDG_DATA_HOME defines the base directory relative to which user specific data files should be stored. If $XDG_DATA_HOME is either not set or empty, a default equal to $HOME/.local/share should be used.) It addresses suggestions from the following issues: 1. Don't put history in $XDG_CONFIG_HOME (closes #744) https://github.com/fish-shell/fish-shell/issues/744 2. Fish is placing non-config files in $XDG_CONFIG_HOME #1257 https://github.com/fish-shell/fish-shell/issues/1257 3. Move non-config data out of $XDG_CONFIG_HOME #1669 https://github.com/fish-shell/fish-shell/issues/1669
generated by cgit v1.2.3 (git 2.39.1) at 2024-07-04 04:16:33 +0000