;
layout_close_pane(wp);
w = wp-window = window_create1(s-sx, s-sy);
On Sat, Apr 23, 2011 at 10:44:38PM +0100, Nicholas Marriott wrote:
I can reproduce this, looks like bad cursor positioning after
break-pane. Mailing so others can look and it doesn't get forgotten
I can reproduce this, looks like bad cursor positioning after
break-pane. Mailing so others can look and it doesn't get forgotten.
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Thanks, I'm glad to hear you are reconsidering this.
I might put it in the tmux FAQ as well.
On Wed, Apr 13, 2011 at 09:51:00AM +0200, Karl Ferdinand Ebert wrote:
Hello Nicholas,
On Wed, Apr 13, 2011 at 12:31 AM, Nicholas Marriott
[1]nicholas.marri...@gmail.com wrote:
Hi
Hi
Not to say I told you so or anything, but this might be a good time to
reiterate that doing this is a bad idea: the minor inconvenience it
prevents (easily avoided by the user with either tmux -S or by setting
TMPDIR) is much less of a potential problem than running with elevated
privileges.
On Sat, Oct 24, 2009 at 03:54:57PM -0400, Thomas Dickey wrote:
On Sat, Oct 24, 2009 at 07:20:28PM +0200, Nicholas Marriott wrote:
On Sat, Oct 24, 2009 at 12:49:31AM +1100, Tim Allen wrote:
On Fri, Oct 23, 2009 at 01:24:00PM +0100, Nicholas Marriott wrote:
It appears screen-256color
On Sat, Oct 24, 2009 at 07:42:26PM -0400, Thomas Dickey wrote:
On Sat, Oct 24, 2009 at 10:11:30PM +0100, Nicholas Marriott wrote:
On Sat, Oct 24, 2009 at 03:54:57PM -0400, Thomas Dickey wrote:
Since aixterm 16-colors are part of the default configuration settings,
it's reasonable to count
Hi
If you set TERM to anything aside from screen or screen-256color inside tmux
you will get screen corruption because applications will send the incorrect
escape sequences. This is not a bug.
The FAQ does not say that setting TERM to screen-256color will just work,
although it could probably be
;
+ break;
}
}
}
On Fri, Oct 23, 2009 at 10:30:34PM +1100, Tim Allen wrote:
On Fri, Oct 23, 2009 at 11:11:18AM +0100, Nicholas Marriott wrote:
The FAQ does not say that setting TERM to screen-256color will just
work, although it could probably be clearer. You need to do
On Sat, Oct 24, 2009 at 12:49:31AM +1100, Tim Allen wrote:
On Fri, Oct 23, 2009 at 01:24:00PM +0100, Nicholas Marriott wrote:
It appears screen-256color converts colours 8-15 into 90-97 which are an
extension designed to allow bright colours without the bold attribute (bold
font
This is committed to CVS HEAD now and will be in the next release of fdm when I
get around to it.
Thanks!
On Sat, Jul 25, 2009 at 08:02:46PM +0200, opter_l wrote:
As discussed here and on IRC.
I have replaced the link() call in deliver-maildir.c by a call to a new
`safemove()' function.
I'm going to run with this for a few days and if I don't see any problems I'll
commit it, then it'll be in 1.7 when I get around to doing some more stuff on
fdm.
Thanks
On Sat, Jul 25, 2009 at 08:02:46PM +0200, opter_l wrote:
As discussed here and on IRC.
I have replaced the link() call in
Sorry for the delay, I was a bit busy yesterday.
This looks great to me, I will give it further test, add the manual bits and
commit it later on today or tomorrow.
Thanks for your work!
On Sat, Jul 25, 2009 at 08:02:46PM +0200, opter_l wrote:
As discussed here and on IRC.
I have replaced
Hi
Saying that, I don't see a reason not to make this work for people who
are
prepared to accept the risk or who know for sure they are delivering mail
sequentially. With fdm, you will want to set queue-high/queue-low to 1,
and
perhaps parallel-accounts to 1 if you have multiple
Hi
Thanks for the report.
This isn't really an fdm bug per se, the point of maildirs is to allow delivery
to happen safely without locking. On AFS you are probably best using mboxes
which have flaws but can be locked atomically.
Saying that, I don't see a reason not to make this work for people
Okay, I have committed some parts of the diff and made a couple of other tweaks
which were sometimes causing it to hang. Please test the diff below instead.
Index: fdm.c
===
RCS file: /cvsroot/fdm/fdm/fdm.c,v
retrieving revision
On Tue, May 26, 2009 at 07:10:05AM +0100, Nicholas Marriott wrote:
Okay, I have committed some parts of the diff and made a couple of other
tweaks
which were sometimes causing it to hang. Please test the diff below instead.
This is better, please try this:
Index: fdm.c
Okay, this is the problem:
gmail-researchut: spamprobe receive: io: poll: Connection timed out
Your pipe process does not return in the timeout, so fdm aborts the
fetch. Unfortunately this then causes various things which sometimes end up
with fdm not exiting correctly.
fdm's management of
at 07:31:17PM +0100, Nicholas Marriott wrote:
Hi
This patch does not fix the problem - it doesn't drop the utmp privilege after
creating the socket so a user can trivially continue to cause the same issue
by
using the save-buffer command to create a file in /var/run/tmux.
If you do drop
Hi
This patch does not fix the problem - it doesn't drop the utmp privilege after
creating the socket so a user can trivially continue to cause the same issue by
using the save-buffer command to create a file in /var/run/tmux.
If you do drop the privileges, it will break socket recreation with
fdm will only remove the lock file if it exits normally (success or a normal
error), it will not remove it on a fatal error (which means a bug) or on
SIGKILL, and it is never going to since I want to know about these cases and
fix them. Please send me the - log of a session (don't forget to
Okay, thanks. Let me know.
On Sat, May 16, 2009 at 10:13:44PM +0530, Ritesh Raj Sarraf wrote:
On Saturday 16 May 2009 13:51:00 Nicholas Marriott wrote:
fdm will only remove the lock file if it exits normally (success or a
normal error), it will not remove it on a fatal error (which means
Yes, it is probably because it is setuid. fdm calls kill(pid, 0) to see if the
process has actually started. This isn't actually needed, it is a debugging
aid. In any case, if it gets EPERM it is probably safe to assume the process
does exist. Please try this diff:
Index: command.c
I'm not convinced by your version, it needs to explicitly state that
all mail from this account is kept, even if you later tell it to drop
the same mail in your rules. I'll have a closer look at the wording
later on.
2009/4/22 Ritesh Raj Sarraf r...@researchut.com:
On Wednesday 22 Apr 2009
fdm doesn't keep track of mail it has seen unless you tell it to. Due
to limitations in POP3 it requires a separate cache file (IMAP does
not require one). Look for new-only and old-only in the manual, IIRC
they have been there since about 1.4... I've been slacking on fdm
recently so they
The cache doesn't expire, otherwise it would refetch mail.
I should really convert this and the NNTP cache to reuse the generic
cache code which does support expiry.
2009/4/22 Ritesh Raj Sarraf r...@researchut.com:
On Wednesday 22 Apr 2009 23:17:56 Nicholas Marriott wrote:
fdm doesn't keep
Er, sorry, that was unclear. It doesn't expire, but any mail found no
longer to be in the account should be removed from the cache, so if
you delete the mail with another program fdm should remove it from the
cache.
2009/4/22 Nicholas Marriott nicholas.marri...@gmail.com:
The cache doesn't
Okay, I missed that. Hmm.
Can you show me the cache and the - output of a fetch where it is
refetching stuff in the cache? Don't forget to either strip passwords
or send it privately.
2009/4/22 Ritesh Raj Sarraf r...@researchut.com:
On Wednesday 22 Apr 2009 23:17:56 Nicholas Marriott wrote
27 matches
Mail list logo
