I'm made status-* use formats and add client_prefix format so you can do
eg #{?client_prefix,X,Y}.
On Sat, Jan 19, 2013 at 11:35:15PM +, Daniel wrote:
> > But I'm not sure about the indicator - why did you choose ^ and _? It
> > seems ugly.
>
> I was just looking for this little feature myse
> But I'm not sure about the indicator - why did you choose ^ and _? It
> seems ugly.
I was just looking for this little feature myself.
I would propose "^" and " ". One could also consider the representation
of the prefix key itself (along with spaces to the same length).
-
Hi
Did you send anything later on this? I only see this as the last mail
still in my inbox.
You don't need to call server_status_client so often - it just sets a
flag. Below is a changed diff to server-client.c alone which should be
all you need and I think is fine.
But I'm not sure about the in
server_status_client will set the CLIENT_STATUS bit and update when tmux
returns to the event loop, it's the right thing to do. Also tmux will
regenerate the status line but not actually draw it unless it has
changed.
Even so not sure I'm wild about updating the status line every time the
prefix k
On Sun, Aug 12, 2012 at 09:09:28AM +0100, Thomas Adam wrote:
> I'm not sure how Nicholas feels about this, but this has been on the TODO
> list for a while. I think ideally this should use some form of status-bg
> colour change instead of relying on some specific part of the status line to
> draw
Hello,
On Thu, Aug 09, 2012 at 08:04:46PM +, Andrew Reynhout wrote:
> Hi,
>
> I'm attaching a small patch. It adds a token to the status line format
> which will indicate whether you're in command-mode or not.
I'm not sure how Nicholas feels about this, but this has been on the TODO
list for
