Micah Cowan wrote:
> The following should bind J to join the current (already
> finished) selection with spaces:
>
> bind-key J run-shell 'tmux save-buffer /tmp/.tmux-exchange; tr \n " " <
> /tmp/.tmux-exchange >/tmp/.tmux-exchange-processed; tmux load-buffer
> /tmp/.tmux-exchange-processed'
I
Hallo,
attached find a very conservative patch against your patched
cmd-load-buffer.c which brings the number of calls to realloc()
from n=(final buffer size) to n
tmux.diff
Description: Binary data
At Thu, 18 Feb 2010 23:20:19 +,
Nicholas Marriott wrote:
>
> Hi
>
> Thanks for the diff.
>
Robin Lee Powell wrote:
> Copying from my other post:
>
> The other aspect to it is having a key that can shift between the
> various options. My idea there is to store the
> pass-through-before-pasting command in a (window?) option, and make
> a tmux command that takes an option name and a list
Hi
This is my first post to the list. I have started using tmux recently and i am
loving it. I have a question.
Is there a way to display HostName on top right corner of each split window? I
have seen that a small imformation about the lines copied to buffer is
displayed on the top right of each
Micah Cowan wrote:
> clemens fischer wrote:
>
>> Hi,
>>
>> I am very glad that tmux has rectangular copies now! But a problem
>> as well: in the following, try to cut out the block
>>
>> >bbb < from >aaa bbb
>> >y< >xxx y
>> >22 < >111 22
>>
>> At least in
Hi
On Fri, Feb 19, 2010 at 06:21:30AM +0100, Fulvio Ciriaco wrote:
> Yes, this is quite a more linear patch.
> It has one defect, in my opinion, i.e. that it does
> buffer-size reallocations, usually this is avoided
> by increasing the buffer by a factor 2 rather than increasing
> it by 1 byte. Th
I think the place for deciding how lines should be joined is in paste-buffer or
save-buffer (they can use common code if necessary), not in the copy mode.
On Fri, Feb 19, 2010 at 05:25:36PM +0100, clemens fischer wrote:
> Robin Lee Powell wrote:
>
> > Copying from my other post:
> >
> > The oth
Hi
There is no way to display that at the moment.
Someone was talking about per-pane status lines but that isn't done so far.
On Fri, Feb 19, 2010 at 10:10:24PM +0530, Srinivasa R Chamarthy wrote:
> Hi
>
> This is my first post to the list. I have started using tmux recently and i am
> loving
Micah Cowan wrote:
> Okay, these diffs have been rebased to before the copy-output-merge
> stuff (and to the latest OpenBSD changes), and reworked a bit. They
> should be applied in the order: word-separators, then cmd-prefixes.
[-- name: cmd-prefixes-rebased.diff --]
[-- name: word-separators.di
You keep saying that, and it took me a while to figure out what you
meant, so let me expand.
In screen, the exact work flow was:
hilight a selection
convert the newlines in the selection to something else
copy the selection
paste the selection
I think what you're asking for is this wo
On Fri, Feb 19, 2010 at 05:25:36PM +0100, clemens fischer wrote:
> What I have in mind is something special for any selection and would
> only apply to copy-mode: a per-window (per-pane?) option in a special
> struct hanging off of "struct window"(?), roughly:
>
> struct selection_op {
>
clemens fischer wrote:
> High quality indeed, and works as expected! Thank you very much, Micah!
> One question: it applied with offsets to portable HEAD from yesterday:
> How come?
I wrote it to apply after the last couple patches I'd recently
submitted. I figured it would apply without them
Robin Lee Powell wrote:
> In screen, the exact work flow was:
>
> hilight a selection
>
> convert the newlines in the selection to something else
>
> copy the selection
>
> paste the selection
>
> I think what you're asking for is this work flow:
>
> copy a selection
>
> convert the n
Robin Lee Powell wrote:
> On Fri, Feb 19, 2010 at 05:25:36PM +0100, clemens fischer wrote:
>
>> What I have in mind is something special for any selection and would
>> only apply to copy-mode: a per-window (per-pane?) option in a special
>> struct hanging off of "struct window"(?), roughly:
>>
>>
I guess the subject says it all. My Emacs fu is rusty and I got tired
of constantly thinking in an ancient, dynamic-scope lisp dialect,
tweaking my configuration and finding/maintaining oort-gnus versus gnus
and the like.
The one sad thing with vim is its inability to run a real sub-process
inter
Hi
You are pretty much right, sorry if I wasn't clear.
I think the "convert" bit should be done at the same time as paste.
So copy-mode always sticks the same stuff in the buffer (NOT necessarily what
it does now if other forms are easier), but it can be pasted in various
different ways.
I don'
16 matches
Mail list logo
