| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| | |
|
| | |
|
| | |
|
| |
|
|
| |
existing hooks to use notifys instead.
|
| |
|
|
|
| |
affected session or window when a hook fires. Enable session-created and
session-closed hooks now that that is available.
|
| |
|
|
|
| |
that the user can get at additional information - now used for the
"hook" format, more to come.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
but there is also now a global command queue. Instead of command queues
being dispatched on demand from wherever the command happens to be
added, they are now all dispatched from the top level server
loop. Command queues may now also include callbacks as well as commands,
and items may be inserted after the current command as well as at the end.
This all makes command queues significantly more predictable and easier
to use, and avoids the complex multiple nested command queues used by
source-file, if-shell and friends.
A mass rename of struct cmdq to a better name (cmdq_item probably) is
coming.
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
the complicated ones get no hooks for now (more to come).
|
| |
|
|
| |
from the end of every command queue (which could be nested).
|
| |
|
|
| |
handling.
|
| |
|
|
|
| |
using a wrong TERM without xenl is not so broken if used on a sensible
terminal.
|
| |
|
|
|
|
|
| |
which could potentially free the currently running command, so we need
to take a reference to it in cmdq_continue_one.
Fixes problem reported by Theo Buehler.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
confusing, particularly trying to automatically figure out what target
hooks should be using. So simplify it:
- drop before hooks entirely, they don't seem to be very useful;
- commands with special requirements now fire their own after hook (for
example, if they change session or window, or if they have -t and -s
and need to choose which one the hook uses as current target);
- commands with no special requirements can have the CMD_AFTERHOOK flag
added and they will use the -t state.
At the moment new-session, new-window, split-window fire their own hook,
and display-message uses the flag. The remaining commands still need to
be looked at.
|
| |
|
|
| |
be done with hooks instead.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
sequences (notable EL and ED but also IL, DL, ICH, DCH) create blank
cells using the current background colour rather than the default
colour.
On modern systems BCE doesn't really have many benefits, but most other
terminals now support it, some (lazy) applications rely on it, and it is
not hard to include now that we have pane background colours anyway.
Mostly written by Sean Haugh.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Prepare the state again before the "after" hooks are run, because the
command may have killed or moved windows.
- Use the hooks list from the newly prepared target, not the old hooks
list (only matters for new-session really).
- Correctly detect an invalid current state and ignore it in
cmd_find_target ("killw; swapw").
- Change neww, new, killp, killw, splitw, swapp, swapw to update the
current state (used if no explicit target is given) to something more
useful after they have finished. For example, neww changes it to the
newly created window.
Hooks are still relatively new and primitive so there are likely to be
more changes to come.
Parts based on bug reports from Uwe Werler and Iblis Lin.
|
| | |
|
| |
|
|
| |
do not draw if pane is not visible.
|
| |
|
|
|
| |
modify the screen, not after; and use grid_view_insert_cells to make
space not grid_move_cells.
|
| | |
|
| |
|
|
| |
command prompt.
|
| |
|
|
| |
pane. Reported by Theo Buehler.
|
| |
|
|
|
|
| |
support line editing and instead executes a command as soon as a
non-number key is pressed. Add a -N flag to command-prompt for the same
in copy mode. Reported by Theo Buehler.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
fired then triple), and use for select-word and select-line in copy
mode. Inspired by a different solution from Omar Sandoval.
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The vi-copy and emacs-copy mode key tables are gone, and instead copy
mode commands are bound in one of two normal key tables ("copy-mode" or
"copy-mode-vi"). Keys are bound to "send-keys -X copy-mode-command". So:
bind -temacs-copy C-Up scroll-up
bind -temacs-copy -R5 WheelUpPane scroll-up
Becomes:
bind -Tcopy-mode C-Up send -X scroll-up
bind -Tcopy-mode WheelUpPane send -N5 -X scroll-up
This allows the full command parser and command set to be used - for
example, we can use the normal command prompt for searching, jumping,
and so on instead of a custom one:
bind -Tcopy-mode C-r command-prompt -p'search up' "send -X search-backward '%%'"
command-prompt also gets a -1 option to only require on key press, which
is needed for jumping.
The plan is to get rid of mode keys entirely, so more to come eventually.
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
because it is not possible to keep the mouse on the border when the
minimum size is reached.
|
| | |
|
| |
|
|
|
| |
they are enabled and break the actual screen generation code into a
separate function. Fixes problems reported by Romain Francoise.
|
| |
|
|
| |
sensibly.
|
| | |
|
| |
|
|
|
| |
because we don't care if it is truncated to the screen width, we don't
want it to be fatal.
|
| |
|
|
|
|
|
| |
the end of the source, but it was wrong and causes problems that are
only showing up now we are more aggressive about skipping redundant
screen updates. Remove the optimization entirely as more trouble than it
is worth to fix (and it'll have to go when BCE is done anyway).
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
functions static.
|
