| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
| |
- Add four new functions: forward-bigword, backward-bigword,
kill-bigword, backward-kill-bigword
- Add new enum move_word_style_whitespace and related state machine
method
- Change vi key bindings to operate on bigwords: B, gE, W, E, dW, diW,
daW, dE, dB, dgE, cW, ciW, caW, cE, cB, cgE, yW, yiW, yaW, yE, yB,
ygE
|
| | |
|
| |
|
|
|
|
|
|
|
| |
su does not reset XDG_RUNTIME_DIR, which means that XDG_RUNTIME_DIR
may point to directories that the user does not have permission
to access. Similarly there is no guarantee that XDG_RUNTIME_DIR
points to a directory that actually exists. Rather than try to
handle these issues, we simply ignore them, effectively disabling
realtime uvar notifications. Fixes #1955.
|
| |
|
|
|
|
|
| |
Backing out fix for #2096 until we know how to avoid
spamming other terminals (#2102)
This reverts commit 5c4acc8ee1485e40b00ea0578aeff338078cfb8b.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Notification is sent using an OSC 777 escape sequence as described at
http://known.phyks.me/2014/local-notifications-for-weechat-and-urxvt.
The specific notification is crafted to match that emitted by bash
when running under Fedora 22 with the "vte-profile" RPM installed.
See the code for "__vte_prompt_command" starting at
http://pkgs.fedoraproject.org/cgit/vte291.git/tree/vte291-command-notify.patch#n307
to see exactly what bash produces. My approach is, however, a bit
more paranoid about control characters embedded in commands.
Gnome-terminal 3.16 responds to this escape sequence by posting a
desktop notification if the containing terminal window does not have
focus. This lets the user know that a long-running background command
has completed. Job notification is promoted as a Fedora 22 feature
(http://fedoramagazine.org/terminal-job-notifications-in-fedora-22-workstation/),
so it would be good for fish users to be benefit from it.
Conversely, anyone who does not want this feature can use "functions
--erase __notify_vte_command_completed" to turn it off.
|
| |
|
|
| |
(Now from Automake 1.14.1.)
|
| |
|
|
|
| |
(Now from http://git.savannah.gnu.org/gitweb/?p=config.git;a=tree, timestamp
March 2015)
|
| |
|
|
|
|
|
|
|
|
|
| |
This reverts commit bfbeca8b6c2fd5f25488bc1add4198e570898722 which was
submitted in #2089.
`pass` ships its own completions and duplication is likely to cause
problems.
See https://github.com/fish-shell/fish-shell/pull/1843 for the
rationale.
|
| | |
|
| | |
|
| |
|
|
| |
Closes #2064.
|
| |\ |
|
| | |
| |
| |
| | |
[skip ci]
|
| | |
| |
| |
| | |
Fixes #2075
|
| | |
| |
| |
| | |
Fixes #1754
|
| | |
| |
| |
| | |
Fixes #1754
|
| | |
| |
| |
| | |
It's long and obnoxious
|
| | |
| |
| |
| |
| |
| | |
Before this fix, `function -a arg1 name1` would produce a
function named 'arg1'. After this fix, it will produce a
function named 'name'. See #2068 for more.
|
| | |
| |
| |
| |
| | |
When declaring a function using the function "function", the options must follow, not precede, the function name.
The examples demonstrate this syntax, but the synopsis previously showed the options preceding the name.
|
| | |
| |
| |
| | |
Fixes #2067
|
| | |
| |
| |
| | |
Fixes #2067
|
| |/ |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
In FAQ:
> I'm seeing weird output before each prompt when using screen. What's wrong?
The command provided is
echo 'function fish_title;end' > ~/.config/fish/config.fish
Using `>` will overwrite current config.fish.
We should use `>>` instead.
|
| | |
|
| |
|
|
| |
Fixes #1809
|
| |
|
|
| |
Fixes #2044
|
| |
|
|
| |
Fixes #1255
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
Per #1485
|
| | |
|
| |
|
|
| |
Introduced with 6ece852 for #834.
|
| |
|
|
| |
[skip ci]
|
| |
|
|
| |
Fixes #2041
|
| |
|
|
| |
Fixes #2046
|
| | |
|
| |
|
|
|
|
| |
Example: we can point $* to argv
Fixes #1288
|
| |
|
|
| |
Preparation for issue #1228
|
| | |
|
| |
|
|
| |
Fixes #2034
|
| |
|
|
|
|
|
|
| |
With the fix for #365, fish_command_not_found event handlers
receive the command and all of its arguments. But commands
like /usr/lib/command-not-found expect only the command name.
So when invoking an external command, just pass the command
name, not all of the arguments.
|
| |
|
|
|
|
|
|
|
|
|
| |
Before running a command, we add the command to history, so
that if the command causes us to exit it's still captured in
history. But that command should not be considered part of
history when expanding the history within the command itself.
For example, `echo $history[1]` should be the previously
run command, not `echo $history[1]` itself.
Fixes #2028
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For the case
```
bind \et "commandline -i 1" "commandline -i 2"
```
the order of execution of the commands is now in-order.
Note that functions codes are prepended to the queue in reverse order, so they
will be executed in-order. This should allow all bindings of the form
```
bind \et beginning-of-line force-repaint
```
to remain unchanged.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Using builtin `commandline -f`, one would expect to have commands executed in
the order that they were given. This motivates the change to a queue.
Unfortunately, fish internals still need lookahead_list to act as a stack. Add
and rename functions to support both cases and have lookahead_list as
a std::deque internally.
This code is delicate, and we should probably dog-food this in nightly for
a while before the next-minor release.
Fixes #1567
|
| | |
|
| | |
|
| |
|
|
| |
This reverts commit e17f6fb2dcdbc147cfdb4a55639ad784a927f2a6.
|
| |
|
|
|
|
| |
Per discussion in #1956, back this out until we have consensus.
This reverts commit 20a6b65b2536c4f59934a2e52271cfa814a586ea.
|
| | |
|
Michael Steed
ridiculousfish
Ben Liblit
David Adam
John Pham
Rico Sta. Cruz
Jeremy W. Sherman
Jakukyo Friel
Brendan Whitfield
Ingo Blechschmidt
Sanne Wouda
Roman Hargrave
Konrad Borowski