<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rtmux.git/cmd-delete-buffer.c, branch master</title>
<subtitle>Tmux with Rahm's extra hacks.</subtitle>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rtmux.git/'/>
<entry>
<title>Merge delete-buffer into cmd-set-buffer.c and change the paste buffer</title>
<updated>2015-09-11T14:41:50+00:00</updated>
<author>
<name>nicm</name>
<email>nicm</email>
</author>
<published>2015-09-11T14:41:50+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rtmux.git/commit/?id=a3de5dbab1680528d622a5054075e3d8efced795'/>
<id>a3de5dbab1680528d622a5054075e3d8efced795</id>
<content type='text'>
API so it has one paste_free() rather than free_top and free_name
(everywhere that uses it already has the right pointer).
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
API so it has one paste_free() rather than free_top and free_name
(everywhere that uses it already has the right pointer).
</pre>
</div>
</content>
</entry>
<entry>
<title>Instead of setting up the default keys by building the key struct</title>
<updated>2014-10-20T22:29:25+00:00</updated>
<author>
<name>nicm</name>
<email>nicm</email>
</author>
<published>2014-10-20T22:29:25+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rtmux.git/commit/?id=45dfc5a074e2ceae11a6d4aeae597bee1e028503'/>
<id>45dfc5a074e2ceae11a6d4aeae597bee1e028503</id>
<content type='text'>
directly with a helper function in the cmd_entry, include a table of
bind-key commands and pass them through the command parser and a
temporary cmd_q.

As well as being smaller, this will allow default bindings to be command
sequences which will probably be needed soon.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
directly with a helper function in the cmd_entry, include a table of
bind-key commands and pass them through the command parser and a
temporary cmd_q.

As well as being smaller, this will allow default bindings to be command
sequences which will probably be needed soon.
</pre>
</div>
</content>
</entry>
<entry>
<title>Add support for named buffers. If you don't name a buffer, things work</title>
<updated>2014-05-13T07:34:35+00:00</updated>
<author>
<name>nicm</name>
<email>nicm</email>
</author>
<published>2014-05-13T07:34:35+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rtmux.git/commit/?id=3dbacbb62b033c04185fb87da5b0622f0aafee86'/>
<id>3dbacbb62b033c04185fb87da5b0622f0aafee86</id>
<content type='text'>
much as before - buffers are automatically named "buffer0000",
"buffer0001" and so on and ordered as a stack. Buffers can be named
explicitly when creating ("loadb -b foo" etc) or renamed ("setb -b
buffer0000 -n foo"). If buffers are named explicitly, they are not
deleted when buffer-limit is reached. Diff from J Raynor.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
much as before - buffers are automatically named "buffer0000",
"buffer0001" and so on and ordered as a stack. Buffers can be named
explicitly when creating ("loadb -b foo" etc) or renamed ("setb -b
buffer0000 -n foo"). If buffers are named explicitly, they are not
deleted when buffer-limit is reached. Diff from J Raynor.
</pre>
</div>
</content>
</entry>
<entry>
<title>There is no longer a need for a paste_stack struct or for global_buffers</title>
<updated>2014-04-24T09:14:43+00:00</updated>
<author>
<name>nicm</name>
<email>nicm</email>
</author>
<published>2014-04-24T09:14:43+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rtmux.git/commit/?id=bec6c807cd580b003cd94b52a20caa2cbc7a0753'/>
<id>bec6c807cd580b003cd94b52a20caa2cbc7a0753</id>
<content type='text'>
to be global. Move to paste.c.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
to be global. Move to paste.c.
</pre>
</div>
</content>
</entry>
<entry>
<title>Remove the barely-used and unnecessary command check() function.</title>
<updated>2013-10-10T12:00:18+00:00</updated>
<author>
<name>nicm</name>
<email>nicm</email>
</author>
<published>2013-10-10T12:00:18+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rtmux.git/commit/?id=d45c12b6c9405da549197c2852ac124fc0d5b340'/>
<id>d45c12b6c9405da549197c2852ac124fc0d5b340</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Add a command queue to standardize and simplify commands that call other</title>
<updated>2013-03-24T09:54:10+00:00</updated>
<author>
<name>Nicholas Marriott</name>
<email>nicm@openbsd.org</email>
</author>
<published>2013-03-24T09:54:10+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rtmux.git/commit/?id=20636d956dd36c1f14152569a4d44a50eea9083d'/>
<id>20636d956dd36c1f14152569a4d44a50eea9083d</id>
<content type='text'>
commands and allow a command to block execution of subsequent
commands. This allows run-shell and if-shell to be synchronous which has
been much requested.

Each client has a default command queue and commands are consumed one at
a time from it. A command may suspend execution from the queue by
returning CMD_RETURN_WAIT and then resume it by calling cmd_continue() -
for example run-shell does this from the callback that is fired after
the job is freed.

When the command queue becomes empty, command clients are automatically
exited (unless attaching). A callback is also fired - this is used for
nested commands in, for example, if-shell which can block execution of
the client's cmdq until a new cmdq becomes empty.

Also merge all the old error/info/print functions together and lose the
old curclient/cmdclient distinction - a cmdq is bound to one client (or
none if in the configuration file), this is a command client if
c-&gt;session is NULL otherwise an attached client.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
commands and allow a command to block execution of subsequent
commands. This allows run-shell and if-shell to be synchronous which has
been much requested.

Each client has a default command queue and commands are consumed one at
a time from it. A command may suspend execution from the queue by
returning CMD_RETURN_WAIT and then resume it by calling cmd_continue() -
for example run-shell does this from the callback that is fired after
the job is freed.

When the command queue becomes empty, command clients are automatically
exited (unless attaching). A callback is also fired - this is used for
nested commands in, for example, if-shell which can block execution of
the client's cmdq until a new cmdq becomes empty.

Also merge all the old error/info/print functions together and lose the
old curclient/cmdclient distinction - a cmdq is bound to one client (or
none if in the configuration file), this is a command client if
c-&gt;session is NULL otherwise an attached client.
</pre>
</div>
</content>
</entry>
<entry>
<title>Make command exec functions return an enum rather than -1/0/1 values and</title>
<updated>2012-07-11T07:10:15+00:00</updated>
<author>
<name>Nicholas Marriott</name>
<email>nicm@openbsd.org</email>
</author>
<published>2012-07-11T07:10:15+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rtmux.git/commit/?id=ede8312d59c5d08990f83f38682c26434823525b'/>
<id>ede8312d59c5d08990f83f38682c26434823525b</id>
<content type='text'>
add a new value to mean "leave client running but don't attach" to fix
problems with using some commands in a command sequence. Most of the
work by Thomas Adam, problem reported by "jspenguin" on SF bug 3535531.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
add a new value to mean "leave client running but don't attach" to fix
problems with using some commands in a command sequence. Most of the
work by Thomas Adam, problem reported by "jspenguin" on SF bug 3535531.
</pre>
</div>
</content>
</entry>
<entry>
<title>xfree is not particularly helpful, remove it. From Thomas Adam.</title>
<updated>2012-07-10T11:53:01+00:00</updated>
<author>
<name>Nicholas Marriott</name>
<email>nicm@openbsd.org</email>
</author>
<published>2012-07-10T11:53:01+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rtmux.git/commit/?id=df912e3540968a2a0b266e523ecc08bb2dc0ca20'/>
<id>df912e3540968a2a0b266e523ecc08bb2dc0ca20</id>
<content type='text'>
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
</pre>
</div>
</content>
</entry>
<entry>
<title>Clean up and simplify tmux command argument parsing.</title>
<updated>2011-01-04T00:42:46+00:00</updated>
<author>
<name>Nicholas Marriott</name>
<email>nicm@openbsd.org</email>
</author>
<published>2011-01-04T00:42:46+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rtmux.git/commit/?id=7502cb3adbb26a2f94445a35626e64041d6769f9'/>
<id>7502cb3adbb26a2f94445a35626e64041d6769f9</id>
<content type='text'>
Originally, tmux commands were parsed in the client process into a
struct with the command data which was then serialised and sent to the
server to be executed. The parsing was later moved into the server (an
argv was sent from the client), but the parse step and intermediate
struct was kept.

This change removes that struct and the separate parse step. Argument
parsing and printing is now common to all commands (in arguments.c) with
each command left with just an optional check function (to validate the
arguments at parse time), the exec function and a function to set up any
key bindings (renamed from the old init function).

This is overall more simple and consistent.

There should be no changes to any commands behaviour or syntax although
as this touches every command please watch for any unexpected changes.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
Originally, tmux commands were parsed in the client process into a
struct with the command data which was then serialised and sent to the
server to be executed. The parsing was later moved into the server (an
argv was sent from the client), but the parse step and intermediate
struct was kept.

This change removes that struct and the separate parse step. Argument
parsing and printing is now common to all commands (in arguments.c) with
each command left with just an optional check function (to validate the
arguments at parse time), the exec function and a function to set up any
key bindings (renamed from the old init function).

This is overall more simple and consistent.

There should be no changes to any commands behaviour or syntax although
as this touches every command please watch for any unexpected changes.
</pre>
</div>
</content>
</entry>
<entry>
<title>Change from a per-session stack of buffers to one global stack which is</title>
<updated>2010-12-30T23:16:18+00:00</updated>
<author>
<name>Nicholas Marriott</name>
<email>nicm@openbsd.org</email>
</author>
<published>2010-12-30T23:16:18+00:00</published>
<link rel='alternate' type='text/html' href='http://git.josher.dev/rtmux.git/commit/?id=cc42614fa92a0fd93ae359af6562401a2d3d00d7'/>
<id>cc42614fa92a0fd93ae359af6562401a2d3d00d7</id>
<content type='text'>
much more convenient and also simplifies lot of code. This renders
copy-buffer useless and makes buffer-limit now a server option.

By Tiago Cunha.
</content>
<content type='xhtml'>
<div xmlns='http://www.w3.org/1999/xhtml'>
<pre>
much more convenient and also simplifies lot of code. This renders
copy-buffer useless and makes buffer-limit now a server option.

By Tiago Cunha.
</pre>
</div>
</content>
</entry>
</feed>
