On 2013–05–24 Chris Johnsen wrote:
> That renaming behavior (based on the actual command string, not the process
> that is running) sounds like what oh-my-zsh does. You could probably modify
> omz_termsupport_preexec in lib/termsupport.zsh to ignore your "stty prefix"
> (similar to the way it stri
On Fri, May 24, 2013 at 10:35 AM, Marco wrote:
> On 2013–05–14 Nicholas Marriott wrote:
>
> > The easiest solution is to run "stty -ixon; vim"
>
> This is what I'm doing now. My suggestion of setting stty in .zshenv
> broke too many other programs. Calling the programs like “stty
> -ixon; vim” ha
On 2013–05–14 Nicholas Marriott wrote:
> The easiest solution is to run "stty -ixon; vim"
This is what I'm doing now. My suggestion of setting stty in .zshenv
broke too many other programs. Calling the programs like “stty
-ixon; vim” has the disadvantage that the automatic window renaming
display
On 2013–05–14 Nicholas Marriott wrote:
> We have typically chosen - with a few exceptions - to try and make tmux
> create all windows with the same environment no matter how they are
> started. This means things are mostly consistent.
I don't have much knowledge about terminals internals, so bear
There are a number of places you can create a new window in tmux and the
difficulty is that several of these don't have an obvious parent or have
a choice of parents.
We have typically chosen - with a few exceptions - to try and make tmux
create all windows with the same environment no matter how
On 2013–05–14 Frank Terbeck wrote:
> You could create a wrapper script like this:
>
> [snip]
> #!/bin/sh
>
> stty -ixon
> exec "$@"
> [snap]
I found another workaround which does not require changing the
scripts that launch tmux. Commands in the file ~/.zshenv seems to
work regardless of the ty
Actually I wonder if it should instead be saved at server start - like
the initial global environment.
The trouble is that if you start tmux with a messed up termios you are
then SOL until you restart entirely. We know the system default termios
will be sane.
On Tue, May 14, 2013 at 11:22:04PM +
IXON could be pulled from the client termios like t_cc, look at
window.c:780.
I'm not sure about doing this because there isn't a termios available
for already attached sessions or for clients where stdin is not a
tty. We could fix that but it'd still vary depending where you create
the window fro
Thomas Adam wrote:
> On 14 May 2013 21:24, "Frank Terbeck" wrote:
[...]
>> I suppose having an option for new-window and new-session and/or a
>> server setting that sets the default state of the flowcontrol in the
>> terminals tmux provides, wouldn't be a completely ridiculous thing to
>> ask for.
On 14 May 2013 21:24, "Frank Terbeck" wrote:
>
> Marco wrote:
> > On 2013–05–14 Marco wrote:
> [...]
> >> I know you think the programs are at fault, but apparently it's
> >> common practice to make applications respect the stty setting,
> >> regardless if it makes sense or not. It's just not prac
Marco wrote:
> On 2013–05–14 Marco wrote:
[...]
>> I know you think the programs are at fault, but apparently it's
>> common practice to make applications respect the stty setting,
>> regardless if it makes sense or not. It's just not practical to
>> file a bug report against so many applications.
On 2013–05–14 Marco wrote:
> What would be the best place to fix this, tmux or the shell?
Sorry, stupid question. It would have to be fixed in *all* shells,
since it's not just one, which would probably be the same hassle
as fixing all programs.
> I know you think the programs are at fault, but
On 2013–05–14 Frank Terbeck wrote:
> > On 2013–05–14 Nicholas Marriott wrote:
> >> Surely vim should be turning off flow control itself though?
> >
> > As Frank already pointed out, it happens with all applications.
>
> To be fair, there are applications that do the right thing. The terminal
> ve
Marco wrote:
> On 2013–05–14 Nicholas Marriott wrote:
>> Surely vim should be turning off flow control itself though?
>
> As Frank already pointed out, it happens with all applications.
To be fair, there are applications that do the right thing. The terminal
version of emacs for example.
You coul
On 2013–05–14 Nicholas Marriott wrote:
> Sounds like it doesn't work for noninteractive shells, probably need to
> put the stty somewhere that your shell always reads even if
> noninteractive.
And where would that be, for instance?
> Surely vim should be turning off flow control itself though?
Nicholas Marriott wrote:
> Sounds like it doesn't work for noninteractive shells, probably need to
> put the stty somewhere that your shell always reads even if
> noninteractive.
>
> Surely vim should be turning off flow control itself though?
I think that turning flow control off is the only reas
Sounds like it doesn't work for noninteractive shells, probably need to
put the stty somewhere that your shell always reads even if
noninteractive.
Surely vim should be turning off flow control itself though?
On Tue, May 14, 2013 at 04:28:01PM +0200, Marco wrote:
> Hi,
>
> I already asked this
17 matches
Mail list logo
