On Sun, Jun 17, 2012, at 11:00 PM, Thomas Adam wrote:
> OK, I had to do a few things differently to you. Does the following
> help?
>
> diff --git a/trunk/cmd.c b/trunk/cmd.c
> index 7aefeff..09b4922 100644
> --- a/trunk/cmd.c
> +++ b/trunk/cmd.c
> @@ -1303,7 +1303,7 @@ cmd_get_default_path(str
On Sun, Jun 17, 2012 at 10:53:54PM +0100, Thomas Adam wrote:
> Hi,
>
> On 17 June 2012 22:50, Giorgio Lando wrote:
> >
> > On Sun, Jun 17, 2012, at 08:46 PM, Giorgio Lando wrote:
> >> 1) I start tmux;
> >> 2) I launch mutt with the following key binding defined in my tmux.conf:
> >> bind p neww -
Hi,
On 17 June 2012 22:50, Giorgio Lando wrote:
>
> On Sun, Jun 17, 2012, at 08:46 PM, Giorgio Lando wrote:
>> 1) I start tmux;
>> 2) I launch mutt with the following key binding defined in my tmux.conf:
>> bind p neww -k -t:6 'mutt'
>> 3) I suspend my laptop to ram;
>> 4) I relaunch mutt with th
On Sun, Jun 17, 2012, at 08:46 PM, Giorgio Lando wrote:
> 1) I start tmux;
> 2) I launch mutt with the following key binding defined in my tmux.conf:
> bind p neww -k -t:6 'mutt'
> 3) I suspend my laptop to ram;
> 4) I relaunch mutt with that same keybinding.
Sorry to correct myself so soon, bu
Hi, in many occasions, after resuming from suspension to ram, the tmux
server suddenly segfaults for me. The segfault happens quite randomly,
but a way to reproduce it is the following:
1) I start tmux;
2) I launch mutt with the following key binding defined in my tmux.conf:
bind p neww -k -t:6 '
