| Commit message (Collapse) | Author | Age |
... | |
|
|
|
| |
/c/c looks awful, and C:/ is simply better.
|
| |
|
| |
|
| |
|
|
|
|
| |
This is case in Cygwin, which doesn't have /etc/shells ans chsh.
|
|
|
|
|
|
|
|
|
| |
Yes, it's an awful hack, but IPC support (and fork support as well -
even FAQ mentions that, and suggests "restarting process" to solve the
problem (http://cygwin.com/faq/faq.html#faq.using.fixing-fork-failures),
but let's ignore that for now) is simply broken in Cygwin. Having to try
to do exactly same thing in Cygwin, just so perhaps it will work is a
completely normal thing (not). I love Windows.
|
|
|
|
|
|
|
| |
I commited executables in previous commit (removed using git push
--force - sorry, I wouldn't want to waste space in git repository), so I
think *.exe files should be forbidden to avoid any problems (there is no
reason to ever commit them)
|
|
|
|
|
|
| |
Yes, hostname is broken under Cygwin, but for fish it's an issue, as it
makes fish_config more buggy than it needs to be (by making UTF-8 errors
according to Python).
|
|
|
|
|
| |
It appears that dircolors -c under Cygwin has >&/dev/null at end that is
valid C shell syntax, but isn't accepted in fish shell.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Note that this will NOT get updated on every run - even if autoconf is run manually, the value may be cached. The PACKAGE_VERSION variable/symbol will not be reliable. Use FISH_BUILD_VERSION instead.
|
|
|
|
|
|
|
|
| |
This commit hooks the Makefile up to generate a FISH_BUILD_VERSION
symbol and kills off PACKAGE_VERSION in .cpp files.
It also modifies the tarball generation script to add the necessary
version file for releases.
|
|
|
|
|
|
| |
Originally from the git sources (GIT-VERSION-GEN)
(C) Junio C Hamano <junkio@cox.net>
Reused under GPL v2.0
|
|
|
|
| |
(but not all!) build_documentation.sh is needed for the tarball if you run make distclean
|
| |
|
|
|
|
|
| |
closes #931
also fixes a crossreference error
|
|
|
|
|
|
| |
git.git's __git_ps1 doesn't have an upstream prefix. I'm not sure why
one was added to our __fish_git_prompt, but it certainly shouldn't
default to a space.
|
| |
|
|
|
|
| |
Doxyfile.help isn't generated
|
| |
|
|
|
|
|
|
| |
It reuses $__fish_git_prompt_char_stateseparator, since it has a
similar meaning and goes otherwise unused when
$__fish_git_prompt_show_informative_status is set.
|
|
|
|
|
|
|
|
|
|
|
| |
This changes the defaults for several characters when
$__fish_git_prompt_show_informative_status is set so that the prompt
looks more like the typical informative prompt.
Before: (master >1<2|+3#4*5%6)
After: (master↑1↓2|●3✖4✚5…6)
The defaults were taken from magicmonty/bash-git-prompt
|
|
|
|
|
|
| |
This makes $__fish_git_prompt_show_informative_status imply
$__fish_git_prompt_showupstream = "informative", while adding a none
option for showupstream to disable it if desired.
|
|
|
|
|
| |
This makes $__fish_git_prompt_showupstream = "auto" mean "informative"
instead of "git" if $__fish_git_prompt_show_informative_status is set.
|
| |
|
|
|
|
|
|
|
| |
plus speling in documentation for bind.
Note that this commit does not re-enable the generation of the manpage for
test, which will therefore still fall through to the system manual page with
`man test`.
|
| |
|
| |
|
|
|
|
|
| |
`test -n informative` will always succeed. We want to test the
informative variable instead so that other modes can still work.
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
| |
(Closes #91, #932)
Currently, control-E is bound to `end-of-line`.
This patch modifes the `end-of-line` procedure so that, if it is invoked when
the cursor is at the end of a command and there is pending completion text,
it will accept the completion text and move to the end. The behavior of
`end-of-line` will not otherwise be altered.
|
| |
|
|
|
|
|
|
| |
It's easy to forget the definition of ___fish_git_prompt_status_order
when there are dozens of lines between where it is defined and where
it is used.
|
|
|
|
|
|
|
| |
A few characters and colors got added without being added to the event
list for repainting.
Also sort and re-align list of characters in validate_chars.
|
|
|
|
|
| |
based on git.git 14d7649: "bash prompt: avoid command substitution
when checking for untracked files"
|
|
|
|
|
|
|
|
|
|
|
|
| |
The code invoked `git rev-parse` several times when the required
information could be collected all at once.
This is based on the following commits from git.git:
efaa0c1: bash prompt: combine 'git rev-parse' executions in the main code path
e3e0b93: bash prompt: combine 'git rev-parse' for detached head
0f37c12: bash prompt: use bash builtins to check for unborn branch for dirty state
dd0b72c: bash prompt: use bash builtins to check stash state
|
|
|
|
|
|
|
|
| |
It's a one line function called in a single place. I suspect it only
existed because the bash equivalent __gitdir existed (it was more
complex), but that function no longer exists either, as of git.git
511ad15: "bash prompt: run 'git rev-parse --git-dir' directly instead
of __gitdir()"
|
|
|
|
|
|
|
|
|
|
| |
Simply using cut duplicates (poorly) `git rev-parse --short`
This also restores the ... printed after the abbreviation which
__fish_git_prompt had been missing.
Based on git.git e8f21ca: "bash prompt: print unique detached HEAD
abbreviated object name"
|
|
|
|
| |
based on git.git 1306321: "prompt: fix for simple rebase"
|
|
|
|
|
|
|
|
| |
Unlike the rest of the __fish_git_prompt_char_* variables, it does not
have its own color because the most likely values are a space and
nothing.
based on git.git 15a54fb: prompt: introduce GIT_PS1_STATESEPARATOR
|
|
|
|
|
|
|
| |
Adds a progress indicator to the rebase messages. (e.g. |REBASE 2/5)
based on the git-prompt portion of git.git b71dc3e: "bash-prompt.sh:
show where rebase is at when stopped"
|
|
|
|
|
|
|
| |
git revert was taught to revert multiple commits, and it stores it
branch information in REVERT_HEAD just like the other *_HEAD files.
based on git.git 3ee4452: bash: teach __git_ps1 about REVERT_HEAD
|
|
|
|
|
| |
The option was added in git.git 66cb5d4, so pay attention to it like
we do the other bash.* options.
|
|
|
|
|
|
|
|
|
|
|
|
| |
Based on GIT_PS1_SHOW_COLORHINTS, it introduces more color by default
and also changes the color of the branch name based on if it is a real
branch or detached.
Based on the following commits from git.git:
9b7e776: show color hints based on state of the git tree
9b3aaf8: Fix up colored git-prompt
76c36c0: coloured git-prompt: paint detached HEAD marker in red
|
|
|
|
|
|
|
| |
This is mostly useful for the next commit that will have different
colors default to different values, but it has one immediate change:
all __fish_git_prompt_color_* variables now default to
__fish_git_prompt_color instead of to nothing, as they used to.
|