| Age | Commit message (Collapse) | Author |
|---|
|
Gives a better error message than "command not found: strfile", because
it's not obvious to many users that strfile is part of fortune.
Also handles the weird /usr/sbin install location for strfile on Cygwin.
|
|
|
|
file. Use local variable for readability, and anonymous function to provide a scope for the local variable.
|
|
Chuck Norris fortune
|
|
Fix first-tab completion in task command
|
|
Plugin for Ember-cli
|
|
docker containers based on defined names
|
|
Add initial JHBuild plugin support
|
|
Fix composer completion: "\s" is a gawk-specific regexp operator.
|
|
added stats command to docker plugin
|
|
|
|
|
|
|
|
This is a bunch of alias for the JHBuild tool.
A well known tool in the GNOME dev project.
|
|
This is done by calling `_task` at the end of the _task completion file,
as is standard in completion files.
|
|
docker container autocomplete listing uses containers ID instead of names.
Most users identify their containers by name. ID is only needed and used on a dynamic environment more suited in scripts.
|
|
|
|
|
|
Ubuntu and Debian store the system-installed virtualenvwrapper in
/etc/bash_completion.d/virtualenvwrapper, so that it gets automatically sourced
at startup in Bash. By not putting it somewhere in $PATH, they end up excluding
others (e.g. Zsh) that might want to use that file. Oops!
The virtualenvwrapper plugin should account for this so that Ubuntu (or Debian)
users don't end up with this message:
zsh virtualenvwrapper plugin: Cannot find virtualenvwrapper.sh. Please install with `pip install virtualenvwrapper`.
even when they have a virtualenvwrapper installed to a known location.
|
|
[Plugin composer] Multiple fixes
|
|
Refactor and improve web-search plugin
|
|
Add Fedora support for command-not-found plugin
|
|
Removing 'local' usage to prevent issue when installed with antigen
|
|
Added trapwinch to vi-mode plugin.
|
|
dircycle plugin: clean and fix logic once and for all
|
|
sudo: maintain cursor position
|
|
This is because we can't be sure which arguments require a json file
and which don't, so the `else' statement will always be difficult to
check for correctness.
|
|
|
|
Use $_comp_command1 for command list generation instead of 'composer':
`$_comp_command1` contains the command written in the command line.
This allows us to have a different composer name
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
They are implemented in lib anyway.
|
|
Sources the activate.sh file or informs the user, that its not
available.
Overriding the cd function, as it was formerly done, is not needed
anymore, activate.sh does this by itself.
|
|
|
|
This way the user can keep their preferred pushd syntax while enabling
us to use a standard syntax in our defined functions.
To explain further, without a clear value on the PUSHD_MINUS option, we
could be changing the +1/-0 values all we want, that some user would
find that it didn't work for him.
We have two options, then:
- Setting a particular value, which was my first approach.
- Using `emulate -L zsh` to ensure all options defined in the function's
body won't be passed along to the main zsh instance.
For more info see:
http://zsh.sourceforge.net/Doc/Release/Shell-Builtin-Commands.html#index-emulate
|
|
|
|
This change follows this proposed behaviour:
Ctrl+Shift+Left: move to last visited directory
Ctrl+Shift+Right: move to next visited directory
an alternative behaviour would be:
Ctrl+Shift+Left: move directory to the left in `dirs` output
Ctrl+Shift+Right: move directory to the right in `dirs` output
It also introduces `setopt nopushdminus` as a way to standardise
pushd syntax. It's value wasn't clear before, which has been the
cause of so many pull requests regarding this plugin not working
in some environments.
|
|
virtualenvwrapper: Deactivate only if in virtualenv
|
|
Improved ant completion
|
|
As suggested in https://github.com/robbyrussell/oh-my-zsh/pull/3329#issuecomment-72062236
|
|
Make use of ant's project help feature instead of trying to parse XML with regex (see: http://stackoverflow.com/a/1732454/740787).
This is a behavioral change that does a few things:
• adds support for ant imports, which were previously not recognized as possibly containing targets
• supresses targets with no description, as these are conventionally for internal use only
|
|
Regen .ant_targets only if it's newer than build.xml? Yeah, that seems wrong.
|
|
|
|
|
