Re: [PATCH] vi-copy: select line with V

2014-08-07 Thread Juho Pohjala
Hi

Thanks for the comments! Please check the updated patch.

> in mode-keys.c you should also update the mode_key_cmdstr_copy array
Yes, new line was already included in the previous patch.


BR,
Juho


On Thu, Aug 7, 2014 at 11:06 PM, Nicholas Marriott
 wrote:
> Yes I will look at this after OpenBSD tree unlocks.
>
>
> On Wed, Jul 23, 2014 at 09:49:13PM +0100, Balazs Kezes wrote:
>> On 2014-07-13 00:59 +0300, Juho Pohjala wrote:
>> > Please have a look at the updated patch.
>>
>> Thanks, this works surprisingly well! Some nits: in mode-keys.c you
>> should also update the mode_key_cmdstr_copy array. Also, it would be
>> nice if you could leave the line mode via v (normal mode) or ^v (block
>> mode), or reenter the line mode from those when V is pressed. Vim also
>> works that way.
>>
>> Nicholas: After this is thoroughly tested, is this something you'd
>> consider for the mainline? It only affects the vi mode.
>>
>> Thanks!
>>
>> --
>> Balazs
>>
>> --
>> Want fast and easy access to all the code in your enterprise? Index and
>> search up to 200,000 lines of code with a free copy of Black Duck
>> Code Sight - the same software that powers the world's largest code
>> search on Ohloh, the Black Duck Open Hub! Try it now.
>> http://p.sf.net/sfu/bds
>> ___
>> tmux-users mailing list
>> tmux-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/tmux-users


patch2
Description: Binary data
--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users


Re: [PATCH] Implement command to enable / disable input

2014-08-07 Thread Anish Athalye
Thanks for the quick feedback! I've attached an updated patch.

–Anish



0001-Add-feature-to-enable-or-disable-keyboard-input.patch
Description: Binary data


> On Aug 7, 2014, at 1:01 PM, Nicholas Marriott  
> wrote:
> 
> Ok but in that case you also need to add it to the last-pane synopsis.
> 
> Also I don't see a need for any more one-line helper functions, just set
> and clear the flag directly and do without server_enable/disable_input.
> 
> This:
> 
> +   "[-ed] [-lDLRU] " CMD_TARGET_PANE_USAGE,
> 
> Should be changed to -DdeLlRU (and manpage too of couse).
> 
> Cheers
> 
> 
>> On Thu, Aug 07, 2014 at 12:27:10PM -0700, Anish Athalye wrote:
>> The last-pane section is also the part that runs if you `select-pane -l`.
>> 
>> As the patch is now, running `select-pane -d -l` will disable input for the 
>> last pane that you were in. I think that behavior is more intuitive than 
>> having that function not work (because something like `select-pane -d -U` 
>> will still work).
>> 
>> So I think it would be better to keep the patch as-is in that regard. Let me 
>> know if you still would like me to change it.
>> 
>> Also, I did update the man page (tmux.1) in the previously attached patch. 
>> Let me know if the explanation should be modified. 
>> 
>> ???Anish
>> 
>>> On Aug 7, 2014, at 12:10 PM, Nicholas Marriott 
>>>  wrote:
>>> 
>>> Hi
>>> 
>>> You don't need to add these to the last-pane section as well, just to
>>> select-pane. Also can you update the man page?
>>> 
>>> Cheers
>>> 
>>> 
>>> 
 On Thu, Aug 07, 2014 at 04:09:30PM +, Anish R Athalye wrote:
 Oh, good idea. I think adding it to the select-pane command makes more 
 sense.
 
 Please see attached patch.
 
 ?Anish
>>> 
>>> 
 
 
 
> On Aug 7, 2014, at 8:16 AM, Nicholas Marriott 
>  wrote:
> 
> Please make this a flag or a pair of flags on an existing command. Maybe
> select-pane or kill-pane.
> 
> 
> 
>> On Thu, Aug 07, 2014 at 07:25:27AM +, Anish R Athalye wrote:
>> Here?s a slightly modified version of the patch ? changed the interface 
>> slightly (better names).
>> 
>> ?Anish
>> 
>> 
>> 
>> 
>>> On Aug 6, 2014, at 11:58 PM, Anish R Athalye  wrote:
>>> 
>>> I think that it would be nice to have the ability to make specific 
>>> panes read only (switching from read/write).
>>> 
>>> I?ve wanted this feature to keep myself from accidentally sending input 
>>> to certain processes that I?ve started in certain panes (that I?m just 
>>> monitoring). This would be great for things like long compilation 
>>> processes that should be monitored but shouldn?t accidentally be 
>>> disturbed. This could even be useful for making something like an htop 
>>> pane read only.
>>> 
>>> It looks like there are some other people looking for this feature: 
>>> http://unix.stackexchange.com/questions/7588/is-there-a-tmux-shortcut-to-go-read-only
>>> 
>>> If you?re happy with the change, the attached patch is good to go with 
>>> a `git am`.
>>> 
>>> 
>>> ?Anish
>>> 
>>> <0001-Implement-command-to-enable-disable-input.patch>
>>> --
>>> Infragistics Professional
>>> Build stunning WinForms apps today!
>>> Reboot your WinForms applications with our WinForms controls. 
>>> Build a bridge from your legacy apps to the future.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk___
>>> tmux-users mailing list
>>> tmux-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/tmux-users
> 
> 
> 
>> --
>> Infragistics Professional
>> Build stunning WinForms apps today!
>> Reboot your WinForms applications with our WinForms controls. 
>> Build a bridge from your legacy apps to the future.
>> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
> 
>> ___
>> tmux-users mailing list
>> tmux-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/tmux-users
>>> 
>>> 
>>> 
--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users


Re: [PATCH] vi-copy: select line with V

2014-08-07 Thread Nicholas Marriott
Yes I will look at this after OpenBSD tree unlocks.


On Wed, Jul 23, 2014 at 09:49:13PM +0100, Balazs Kezes wrote:
> On 2014-07-13 00:59 +0300, Juho Pohjala wrote:
> > Please have a look at the updated patch.
> 
> Thanks, this works surprisingly well! Some nits: in mode-keys.c you
> should also update the mode_key_cmdstr_copy array. Also, it would be
> nice if you could leave the line mode via v (normal mode) or ^v (block
> mode), or reenter the line mode from those when V is pressed. Vim also
> works that way.
> 
> Nicholas: After this is thoroughly tested, is this something you'd
> consider for the mainline? It only affects the vi mode.
> 
> Thanks!
> 
> -- 
> Balazs
> 
> --
> Want fast and easy access to all the code in your enterprise? Index and
> search up to 200,000 lines of code with a free copy of Black Duck
> Code Sight - the same software that powers the world's largest code
> search on Ohloh, the Black Duck Open Hub! Try it now.
> http://p.sf.net/sfu/bds
> ___
> tmux-users mailing list
> tmux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tmux-users

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users


Re: [PATCH] Add wait-for signaling to commands that create new panes

2014-08-07 Thread Nicholas Marriott
Hi

What is this useful for?

This seems like a job for hooks if they are ever finished.


On Mon, Aug 04, 2014 at 01:59:26PM -0400, Nathaniel W Filardo wrote:
> Greetings list,
> 
> The attached patch adds options to new-window, new-session, and split-window
> (commands which create panes) to signal a wait_channel when that pane is
> destroyed, for example after the contained process exits.  Towards this end,
> it changes the life-cycle management code in cmd-wait-for.c to allow
> external holds on a wait_channel structure; these are only taken, at the
> moment, by the aforementioned commands.
> 
> It's something of an afternoon hack-job, so it might not be ideal.
> Comments and criticisms welcome; rotten tomatoes possibly understood but
> less welcome. ;)
> 
> Cheers!
> --nwf;

> diff --git a/cmd-new-session.c b/cmd-new-session.c
> index b36de70..4cf72fc 100644
> --- a/cmd-new-session.c
> +++ b/cmd-new-session.c
> @@ -38,7 +38,7 @@ const struct cmd_entry cmd_new_session_entry = {
>   "Ac:dDF:n:Ps:t:x:y:", 0, -1,
>   "[-AdDP] [-c start-directory] [-F format] [-n window-name] "
>   "[-s session-name] " CMD_TARGET_SESSION_USAGE " [-x width] "
> - "[-y height] [command]",
> + "[-y height] [-W channel] [command]",
>   CMD_STARTSERVER|CMD_CANTNEST,
>   NULL,
>   cmd_new_session_exec
> @@ -61,6 +61,7 @@ cmd_new_session_exec(struct cmd *self, struct cmd_q *cmdq)
>   u_intsx, sy;
>   struct format_tree  *ft;
>   struct environ_entry*envent;
> + struct wait_channel *wc = NULL;
>  
>   if (args_has(args, 't') && (args->argc != 0 || args_has(args, 'n'))) {
>   cmdq_error(cmdq, "command or window name given with target");
> @@ -214,10 +215,13 @@ cmd_new_session_exec(struct cmd *self, struct cmd_q 
> *cmdq)
>   if (c != NULL)
>   environ_update(update, &c->environ, &env);
>  
> + if (args_has(args, 'W'))
> + wc = wait_channel_hold_by_name(args_get(args,'W'));
> +
>   /* Create the new session. */
>   idx = -1 - options_get_number(&global_s_options, "base-index");
>   s = session_create(newname, argc, argv, path, cwd, &env, tiop, idx, sx,
> - sy, &cause);
> + sy, wc, &cause);
>   if (s == NULL) {
>   cmdq_error(cmdq, "create session failed: %s", cause);
>   free(cause);
> diff --git a/cmd-new-window.c b/cmd-new-window.c
> index cd0042e..d5987e8 100644
> --- a/cmd-new-window.c
> +++ b/cmd-new-window.c
> @@ -34,8 +34,8 @@ enum cmd_retval cmd_new_window_exec(struct cmd *, 
> struct cmd_q *);
>  
>  const struct cmd_entry cmd_new_window_entry = {
>   "new-window", "neww",
> - "ac:dF:kn:Pt:", 0, -1,
> - "[-adkP] [-c start-directory] [-F format] [-n window-name] "
> + "ac:dF:kn:Pt:W:", 0, -1,
> + "[-adkP] [-c start-directory] [-F format] [-n window-name] [-W channel]"
>   CMD_TARGET_WINDOW_USAGE " [command]",
>   0,
>   NULL,
> @@ -54,6 +54,7 @@ cmd_new_window_exec(struct cmd *self, struct cmd_q *cmdq)
>   int  argc, idx, last, detached, cwd, fd = -1;
>   struct format_tree  *ft;
>   struct environ_entry*envent;
> + struct wait_channel *wc = NULL;
>  
>   if (args_has(args, 'a')) {
>   wl = cmd_find_window(cmdq, args_get(args, 't'), &s);
> @@ -152,10 +153,13 @@ cmd_new_window_exec(struct cmd *self, struct cmd_q 
> *cmdq)
>   }
>   }
>  
> + if (args_has(args, 'W'))
> + wc = wait_channel_hold_by_name(args_get(args, 'W'));
> +
>   if (idx == -1)
>   idx = -1 - options_get_number(&s->options, "base-index");
>   wl = session_new(s, args_get(args, 'n'), argc, argv, path, cwd, idx,
> - &cause);
> + wc, &cause);
>   if (wl == NULL) {
>   cmdq_error(cmdq, "create window failed: %s", cause);
>   free(cause);
> diff --git a/cmd-split-window.c b/cmd-split-window.c
> index ea047a3..9a4fc15 100644
> --- a/cmd-split-window.c
> +++ b/cmd-split-window.c
> @@ -37,6 +37,7 @@ const struct cmd_entry cmd_split_window_entry = {
>   "split-window", "splitw",
>   "c:dF:l:hp:Pt:v", 0, -1,
>   "[-dhvP] [-c start-directory] [-F format] [-p percentage|-l size] "
> + "[-W channel] "
>   CMD_TARGET_PANE_USAGE " [command]",
>   0,
>   cmd_split_window_key_binding,
> @@ -158,6 +159,10 @@ cmd_split_window_exec(struct cmd *self, struct cmd_q 
> *cmdq)
>   }
>   new_wp = window_add_pane(w, hlimit);
>  
> + if (args_has(args, 'W'))
> + new_wp->signal_on_destroy =
> + wait_channel_hold_by_name(args_get(args, 'W'));
> +
>   path = NULL;
>   if (cmdq->client != NULL && cmdq->client->session == NULL)
>   envent = environ_find(&cmdq->client->environ, "PATH");
> diff --git a/cmd-wait-for.c b/cmd-wait-for.c
> index e251863..f0dd92b 100644
> --- a/cmd-wait-for.c
> +++ b/cmd-wait-for.c
> @@ -43,6 +43,7 @@ 

Re: [PATCH] Implement command to enable / disable input

2014-08-07 Thread Nicholas Marriott
Ok but in that case you also need to add it to the last-pane synopsis.

Also I don't see a need for any more one-line helper functions, just set
and clear the flag directly and do without server_enable/disable_input.

This:

+   "[-ed] [-lDLRU] " CMD_TARGET_PANE_USAGE,

Should be changed to -DdeLlRU (and manpage too of couse).

Cheers


On Thu, Aug 07, 2014 at 12:27:10PM -0700, Anish Athalye wrote:
> The last-pane section is also the part that runs if you `select-pane -l`.
> 
> As the patch is now, running `select-pane -d -l` will disable input for the 
> last pane that you were in. I think that behavior is more intuitive than 
> having that function not work (because something like `select-pane -d -U` 
> will still work).
> 
> So I think it would be better to keep the patch as-is in that regard. Let me 
> know if you still would like me to change it.
> 
> Also, I did update the man page (tmux.1) in the previously attached patch. 
> Let me know if the explanation should be modified. 
> 
> ???Anish
> 
> > On Aug 7, 2014, at 12:10 PM, Nicholas Marriott 
> >  wrote:
> > 
> > Hi
> > 
> > You don't need to add these to the last-pane section as well, just to
> > select-pane. Also can you update the man page?
> > 
> > Cheers
> > 
> > 
> > 
> >> On Thu, Aug 07, 2014 at 04:09:30PM +, Anish R Athalye wrote:
> >> Oh, good idea. I think adding it to the select-pane command makes more 
> >> sense.
> >> 
> >> Please see attached patch.
> >> 
> >> ?Anish
> >> 
> > 
> > 
> >> 
> >> 
> >> 
> >>> On Aug 7, 2014, at 8:16 AM, Nicholas Marriott 
> >>>  wrote:
> >>> 
> >>> Please make this a flag or a pair of flags on an existing command. Maybe
> >>> select-pane or kill-pane.
> >>> 
> >>> 
> >>> 
>  On Thu, Aug 07, 2014 at 07:25:27AM +, Anish R Athalye wrote:
>  Here?s a slightly modified version of the patch ? changed the interface 
>  slightly (better names).
>  
>  ?Anish
>  
>  
>  
>  
> > On Aug 6, 2014, at 11:58 PM, Anish R Athalye  wrote:
> > 
> > I think that it would be nice to have the ability to make specific 
> > panes read only (switching from read/write).
> > 
> > I?ve wanted this feature to keep myself from accidentally sending input 
> > to certain processes that I?ve started in certain panes (that I?m just 
> > monitoring). This would be great for things like long compilation 
> > processes that should be monitored but shouldn?t accidentally be 
> > disturbed. This could even be useful for making something like an htop 
> > pane read only.
> > 
> > It looks like there are some other people looking for this feature: 
> > http://unix.stackexchange.com/questions/7588/is-there-a-tmux-shortcut-to-go-read-only
> > 
> > If you?re happy with the change, the attached patch is good to go with 
> > a `git am`.
> > 
> > 
> > ?Anish
> > 
> > <0001-Implement-command-to-enable-disable-input.patch>
> > --
> > Infragistics Professional
> > Build stunning WinForms apps today!
> > Reboot your WinForms applications with our WinForms controls. 
> > Build a bridge from your legacy apps to the future.
> > http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk___
> > tmux-users mailing list
> > tmux-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/tmux-users
>  
> >>> 
> >>> 
> >>> 
>  --
>  Infragistics Professional
>  Build stunning WinForms apps today!
>  Reboot your WinForms applications with our WinForms controls. 
>  Build a bridge from your legacy apps to the future.
>  http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
> >>> 
>  ___
>  tmux-users mailing list
>  tmux-users@lists.sourceforge.net
>  https://lists.sourceforge.net/lists/listinfo/tmux-users
> >>> 
> >> 
> > 
> > 
> > 

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users


Re: [PATCH] Implement command to enable / disable input

2014-08-07 Thread Anish Athalye
The last-pane section is also the part that runs if you `select-pane -l`.

As the patch is now, running `select-pane -d -l` will disable input for the 
last pane that you were in. I think that behavior is more intuitive than having 
that function not work (because something like `select-pane -d -U` will still 
work).

So I think it would be better to keep the patch as-is in that regard. Let me 
know if you still would like me to change it.

Also, I did update the man page (tmux.1) in the previously attached patch. Let 
me know if the explanation should be modified. 

–Anish

> On Aug 7, 2014, at 12:10 PM, Nicholas Marriott  
> wrote:
> 
> Hi
> 
> You don't need to add these to the last-pane section as well, just to
> select-pane. Also can you update the man page?
> 
> Cheers
> 
> 
> 
>> On Thu, Aug 07, 2014 at 04:09:30PM +, Anish R Athalye wrote:
>> Oh, good idea. I think adding it to the select-pane command makes more sense.
>> 
>> Please see attached patch.
>> 
>> ?Anish
>> 
> 
> 
>> 
>> 
>> 
>>> On Aug 7, 2014, at 8:16 AM, Nicholas Marriott  
>>> wrote:
>>> 
>>> Please make this a flag or a pair of flags on an existing command. Maybe
>>> select-pane or kill-pane.
>>> 
>>> 
>>> 
 On Thu, Aug 07, 2014 at 07:25:27AM +, Anish R Athalye wrote:
 Here?s a slightly modified version of the patch ? changed the interface 
 slightly (better names).
 
 ?Anish
 
 
 
 
> On Aug 6, 2014, at 11:58 PM, Anish R Athalye  wrote:
> 
> I think that it would be nice to have the ability to make specific panes 
> read only (switching from read/write).
> 
> I?ve wanted this feature to keep myself from accidentally sending input 
> to certain processes that I?ve started in certain panes (that I?m just 
> monitoring). This would be great for things like long compilation 
> processes that should be monitored but shouldn?t accidentally be 
> disturbed. This could even be useful for making something like an htop 
> pane read only.
> 
> It looks like there are some other people looking for this feature: 
> http://unix.stackexchange.com/questions/7588/is-there-a-tmux-shortcut-to-go-read-only
> 
> If you?re happy with the change, the attached patch is good to go with a 
> `git am`.
> 
> 
> ?Anish
> 
> <0001-Implement-command-to-enable-disable-input.patch>
> --
> Infragistics Professional
> Build stunning WinForms apps today!
> Reboot your WinForms applications with our WinForms controls. 
> Build a bridge from your legacy apps to the future.
> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk___
> tmux-users mailing list
> tmux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tmux-users
 
>>> 
>>> 
>>> 
 --
 Infragistics Professional
 Build stunning WinForms apps today!
 Reboot your WinForms applications with our WinForms controls. 
 Build a bridge from your legacy apps to the future.
 http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
>>> 
 ___
 tmux-users mailing list
 tmux-users@lists.sourceforge.net
 https://lists.sourceforge.net/lists/listinfo/tmux-users
>>> 
>> 
> 
> 
> 

--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users


Re: [PATCH] Implement command to enable / disable input

2014-08-07 Thread Nicholas Marriott
Hi

You don't need to add these to the last-pane section as well, just to
select-pane. Also can you update the man page?

Cheers



On Thu, Aug 07, 2014 at 04:09:30PM +, Anish R Athalye wrote:
> Oh, good idea. I think adding it to the select-pane command makes more sense.
> 
> Please see attached patch.
> 
> ?Anish
> 


> 
> 
> 
> On Aug 7, 2014, at 8:16 AM, Nicholas Marriott  
> wrote:
> 
> > Please make this a flag or a pair of flags on an existing command. Maybe
> > select-pane or kill-pane.
> > 
> > 
> > 
> > On Thu, Aug 07, 2014 at 07:25:27AM +, Anish R Athalye wrote:
> >> Here?s a slightly modified version of the patch ? changed the interface 
> >> slightly (better names).
> >> 
> >> ?Anish
> >> 
> >> 
> >> 
> >> 
> >> On Aug 6, 2014, at 11:58 PM, Anish R Athalye  wrote:
> >> 
> >>> I think that it would be nice to have the ability to make specific panes 
> >>> read only (switching from read/write).
> >>> 
> >>> I?ve wanted this feature to keep myself from accidentally sending input 
> >>> to certain processes that I?ve started in certain panes (that I?m just 
> >>> monitoring). This would be great for things like long compilation 
> >>> processes that should be monitored but shouldn?t accidentally be 
> >>> disturbed. This could even be useful for making something like an htop 
> >>> pane read only.
> >>> 
> >>> It looks like there are some other people looking for this feature: 
> >>> http://unix.stackexchange.com/questions/7588/is-there-a-tmux-shortcut-to-go-read-only
> >>> 
> >>> If you?re happy with the change, the attached patch is good to go with a 
> >>> `git am`.
> >>> 
> >>> 
> >>> ?Anish
> >>> 
> >>> <0001-Implement-command-to-enable-disable-input.patch>
> >>> --
> >>> Infragistics Professional
> >>> Build stunning WinForms apps today!
> >>> Reboot your WinForms applications with our WinForms controls. 
> >>> Build a bridge from your legacy apps to the future.
> >>> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk___
> >>> tmux-users mailing list
> >>> tmux-users@lists.sourceforge.net
> >>> https://lists.sourceforge.net/lists/listinfo/tmux-users
> >> 
> > 
> > 
> > 
> >> --
> >> Infragistics Professional
> >> Build stunning WinForms apps today!
> >> Reboot your WinForms applications with our WinForms controls. 
> >> Build a bridge from your legacy apps to the future.
> >> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
> > 
> >> ___
> >> tmux-users mailing list
> >> tmux-users@lists.sourceforge.net
> >> https://lists.sourceforge.net/lists/listinfo/tmux-users
> > 
> 




--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users


Re: [PATCH] Implement command to enable / disable input

2014-08-07 Thread Anish R Athalye
Oh, good idea. I think adding it to the select-pane command makes more sense.

Please see attached patch.

–Anish



0001-Add-feature-to-enable-or-disable-keyboard-input.patch
Description: Binary data



On Aug 7, 2014, at 8:16 AM, Nicholas Marriott  
wrote:

> Please make this a flag or a pair of flags on an existing command. Maybe
> select-pane or kill-pane.
> 
> 
> 
> On Thu, Aug 07, 2014 at 07:25:27AM +, Anish R Athalye wrote:
>> Here?s a slightly modified version of the patch ? changed the interface 
>> slightly (better names).
>> 
>> ?Anish
>> 
>> 
>> 
>> 
>> On Aug 6, 2014, at 11:58 PM, Anish R Athalye  wrote:
>> 
>>> I think that it would be nice to have the ability to make specific panes 
>>> read only (switching from read/write).
>>> 
>>> I?ve wanted this feature to keep myself from accidentally sending input to 
>>> certain processes that I?ve started in certain panes (that I?m just 
>>> monitoring). This would be great for things like long compilation processes 
>>> that should be monitored but shouldn?t accidentally be disturbed. This 
>>> could even be useful for making something like an htop pane read only.
>>> 
>>> It looks like there are some other people looking for this feature: 
>>> http://unix.stackexchange.com/questions/7588/is-there-a-tmux-shortcut-to-go-read-only
>>> 
>>> If you?re happy with the change, the attached patch is good to go with a 
>>> `git am`.
>>> 
>>> 
>>> ?Anish
>>> 
>>> <0001-Implement-command-to-enable-disable-input.patch>
>>> --
>>> Infragistics Professional
>>> Build stunning WinForms apps today!
>>> Reboot your WinForms applications with our WinForms controls. 
>>> Build a bridge from your legacy apps to the future.
>>> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk___
>>> tmux-users mailing list
>>> tmux-users@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/tmux-users
>> 
> 
> 
> 
>> --
>> Infragistics Professional
>> Build stunning WinForms apps today!
>> Reboot your WinForms applications with our WinForms controls. 
>> Build a bridge from your legacy apps to the future.
>> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
> 
>> ___
>> tmux-users mailing list
>> tmux-users@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/tmux-users
> 



smime.p7s
Description: S/MIME cryptographic signature
--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users


Re: [PATCH] Implement command to enable / disable input

2014-08-07 Thread Nicholas Marriott
Please make this a flag or a pair of flags on an existing command. Maybe
select-pane or kill-pane.



On Thu, Aug 07, 2014 at 07:25:27AM +, Anish R Athalye wrote:
> Here?s a slightly modified version of the patch ? changed the interface 
> slightly (better names).
> 
> ?Anish
> 
> 
> 
> 
> On Aug 6, 2014, at 11:58 PM, Anish R Athalye  wrote:
> 
> > I think that it would be nice to have the ability to make specific panes 
> > read only (switching from read/write).
> > 
> > I?ve wanted this feature to keep myself from accidentally sending input to 
> > certain processes that I?ve started in certain panes (that I?m just 
> > monitoring). This would be great for things like long compilation processes 
> > that should be monitored but shouldn?t accidentally be disturbed. This 
> > could even be useful for making something like an htop pane read only.
> > 
> > It looks like there are some other people looking for this feature: 
> > http://unix.stackexchange.com/questions/7588/is-there-a-tmux-shortcut-to-go-read-only
> > 
> > If you?re happy with the change, the attached patch is good to go with a 
> > `git am`.
> > 
> > 
> > ?Anish
> > 
> > <0001-Implement-command-to-enable-disable-input.patch>
> > --
> > Infragistics Professional
> > Build stunning WinForms apps today!
> > Reboot your WinForms applications with our WinForms controls. 
> > Build a bridge from your legacy apps to the future.
> > http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk___
> > tmux-users mailing list
> > tmux-users@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/tmux-users
> 



> --
> Infragistics Professional
> Build stunning WinForms apps today!
> Reboot your WinForms applications with our WinForms controls. 
> Build a bridge from your legacy apps to the future.
> http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk

> ___
> tmux-users mailing list
> tmux-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/tmux-users


--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk
___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users


Re: [PATCH] Implement command to enable / disable input

2014-08-07 Thread Anish R Athalye
Here’s a slightly modified version of the patch — changed the interface slightly (better names).–Anish

0001-Implement-command-to-enable-disable-input.patch
Description: Binary data
On Aug 6, 2014, at 11:58 PM, Anish R Athalye  wrote:I think that it would be nice to have the ability to make specific panes read only (switching from read/write).I’ve wanted this feature to keep myself from accidentally sending input to certain processes that I’ve started in certain panes (that I’m just monitoring). This would be great for things like long compilation processes that should be monitored but shouldn’t accidentally be disturbed. This could even be useful for making something like an htop pane read only.It looks like there are some other people looking for this feature: http://unix.stackexchange.com/questions/7588/is-there-a-tmux-shortcut-to-go-read-onlyIf you’re happy with the change, the attached patch is good to go with a `git am`.–Anish<0001-Implement-command-to-enable-disable-input.patch>--Infragistics ProfessionalBuild stunning WinForms apps today!Reboot your WinForms applications with our WinForms controls. Build a bridge from your legacy apps to the future.http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk___tmux-users mailing listtmux-users@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinfo/tmux-users

smime.p7s
Description: S/MIME cryptographic signature
--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users


[PATCH] Implement command to enable / disable input

2014-08-07 Thread Anish R Athalye
I think that it would be nice to have the ability to make specific panes read only (switching from read/write).I’ve wanted this feature to keep myself from accidentally sending input to certain processes that I’ve started in certain panes (that I’m just monitoring). This would be great for things like long compilation processes that should be monitored but shouldn’t accidentally be disturbed. This could even be useful for making something like an htop pane read only.It looks like there are some other people looking for this feature: http://unix.stackexchange.com/questions/7588/is-there-a-tmux-shortcut-to-go-read-onlyIf you’re happy with the change, the attached patch is good to go with a `git am`.–Anish

0001-Implement-command-to-enable-disable-input.patch
Description: Binary data


smime.p7s
Description: S/MIME cryptographic signature
--
Infragistics Professional
Build stunning WinForms apps today!
Reboot your WinForms applications with our WinForms controls. 
Build a bridge from your legacy apps to the future.
http://pubads.g.doubleclick.net/gampad/clk?id=153845071&iu=/4140/ostg.clktrk___
tmux-users mailing list
tmux-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tmux-users