| Age | Commit message (Collapse) | Author |
|---|
|
Actually replace the value of the environment variable $HOME with
"~" instead of appending the tilde in front of the prompt.
|
|
When the current path is /home/user/.config/doublecmd the prompt
now reads "/h/u/.c/doublecmd", not "/h/u/./doublecmd" as was the
case. This matches what the Fish shell does.
Enclose the Perl snippet in single quotes instead of double quotes.
|
|
znt: updated README.md, twice as fast searching
|
|
Close #2739
|
|
|
|
Add support for "putty" $TERM in termsupport.zsh
|
|
[tmux-cssh plugin] Initial version
|
|
|
|
Fixes #4597
|
|
|
|
Otherwise `start` will confuse the first parameter as the title of
a new command prompt if the parameter contains whitespace. That is
because the command to be run will be:
start "abc def"
which opens a new command prompt window with the title "abc def".
With the added empty string we force the start command to interpret
the passed parameter as the file / command:
start "" "abc def"
which will be interpreted like `""` is the title and the rest is
the file or command to start.
-------
**NOTE:** this wouldn't be necessary if the start script in msys
was defined differently; that is, if it had the empty string
already incorporated in the script (/usr/bin/start), like so:
```diff
-cmd //c start "${@//&/^&}"
+cmd //c start "" "${@//&/^&}"
```
Notice however that this would make it impossible to use start
setting a different title, so it's probably best to leave it as is.
More info: http://sourceforge.net/p/msys2/tickets/14/
-------
The change `${(z)open_cmd}` is necessary to force zsh to split the
variable by the spaces and interpret it as separate words.
More info: http://zsh.sourceforge.net/FAQ/zshfaq03.html#l17
|
|
Added an option for the msys value of $OSTYPE
|
|
|
|
|
|
znt: n-history supports multi-line cmds and starts with current buffer
Fixes #4648
|
|
|
|
|
|
|
|
|
|
Update Zsh Navigation Tools plugin
|
|
There a syntax error if $cmd_var contains more than one word,
so we drop the current way to prepend nohup and use a simpler
if-else form.
|
|
Also accept any forms of yes as an answer to the "do you want to update?" prompt
|
|
vi-mode: fix smkx/rmkx by removing broken line-init/finish widgets
|
|
Closes #4578
|
|
The old implementation would attempt to load both the default and custom
implementations, with the custom one coming first, so it would get clobbered
by the default version.
|
|
Update z version to 5dc2a86
|
|
|
|
Updates OMZ's copy to commit 2c295432175990c1bb4e90bc13f609daa67a25d6 from zsh-users/zsh-history-substring-search
|
|
upstream repo
|
|
[wd] update minor version (v0.4.2)
|
|
Update uninstall.sh
|
|
Update github plugin to work with current hub versions
|
|
Fixes #4565
|
|
|
|
Drop the use of nohup on OSX for tmux compatibility
|
|
Apparently `nohup` is not needed in OSX, and using it has the side
that it may break under tmux with the error
nohup: can't detach from console: No such file or directory
For now, this commit only drops the use of `nohup` in OSX. But it
*may* not be necessary under other similar platforms.
|
|
|
|
gradle plugin: also list tasks in subprojects
Cleanup gradle plugin file
|
|
- Delete useless #!zsh
- Simplify gradle build file check
- Format comments and delete TODO stuff (already dealt with)
- Use `$()` syntax for cat commands
|
|
|
|
dircycle: remove redundant key bindings
|
|
Removed Similar Aliases
|
|
bundle outdated alias
|
|
Fixing strange git unstaged prompt behavior
|
|
Mercurial plugin: revise README
|
|
In bindkey strings, "^[" and "\e" mean the same thing. They're both notations for Escape.
|
|
The zle-line-init and zle-line-finish definitions here were broken with
respect to smkx/rmkx because their "if" logic had fallthrough where it shouldn't,
so the mode was left in rmkx all the time. This just removes those widgets
entirely, because they're now defined (correctly) in lib/keybindings.zsh and
not needed in plugins.
|
|
|
|
Closes #4616
Changes the `plugins=(... mercurial ...)` to be closer to correct zsh syntax, removing commas and extra spaces.
Revises discussion on configuring themes to avoid sounding like users should modify the theme definition file in the main OMZ folder. Prioritizes the suggestion of using a theme which already supports hg_prompt_info.
|
|
Two similar aliases which were causing issues.
|
