* David T-G <[EMAIL PROTECTED]> [05-12-2001 14:34]:
| % | The
| % | patch changes the behaviour in respect with old messages and unset
| % | mark_old, the messages stay old (and new messages stay new).
| %
| % I see! Like I said, I would've already expected this behaviour.
|
| Yep. This is ano
Rene, et al --
...and then Ren? Clerc said...
% * Nicolas Rachinsky <[EMAIL PROTECTED]> [05-12-2001 00:05]:
%
% | mark_old unset, new messages stay new (until read), and messages
% | marked_old become new when you leave the mailbox (just try it).
%
% Aha! I didn't know this; this explains a lot
* Nicolas Rachinsky <[EMAIL PROTECTED]> [05-12-2001 00:05]:
| I think it depends on mark_old, with mark_old set, mutt marks unread
| new mails as old when leaving the mailbox, old messages stay old. With
| mark_old unset, new messages stay new (until read), and messages
| marked_old become new wh
On Tue, Dec 04, 2001 at 07:49:46PM +0100, René Clerc <[EMAIL PROTECTED]> wrote:
> * Nicolas Rachinsky <[EMAIL PROTECTED]> [04-12-2001 19:27]:
>
> | On Mon, Dec 03, 2001 at 07:24:00PM -0500, David T-G
><[EMAIL PROTECTED]> wrote:
> | > Rene, since starting to use mutt I've never wished delete was
* Nicolas Rachinsky <[EMAIL PROTECTED]> [04-12-2001 19:27]:
| On Mon, Dec 03, 2001 at 07:24:00PM -0500, David T-G
|<[EMAIL PROTECTED]> wrote:
| > Rene, since starting to use mutt I've never wished delete was set to
| > ask-yes, but I sure hated mark_old (though I want stuff marked old at
| > tim
On Mon, Dec 03, 2001 at 07:24:00PM -0500, David T-G
<[EMAIL PROTECTED]> wrote:
> Rene, since starting to use mutt I've never wished delete was set to
> ask-yes, but I sure hated mark_old (though I want stuff marked old at
> times) :-)
There is an patch which leaves messages marked old marked old
Paul --
...and then Paul Brannan said...
% On Mon, Dec 03, 2001 at 02:59:31PM -0500, David T-G wrote:
% > ...and then Paul Brannan said...
% > % macro index $ ':set delete=ask-yes:set delete=no'
% > %
% > % All I get is a beep, and delete remains set to "ask-yes".
% >
% > That makes sense. Y
On Mon, Dec 03, 2001 at 02:59:31PM -0500, David T-G wrote:
> ...and then Paul Brannan said...
> % macro index $ ':set delete=ask-yes:set delete=no'
> %
> % All I get is a beep, and delete remains set to "ask-yes".
>
> That makes sense. Your macro sets it to ask-yes and then tries to sync
> th
On Mon, Dec 03, 2001 at 08:30:27PM -0600, David wrote:
> I think that this is exactly the problem... I dont know if you are on
> linux, but in my mounts through NIS to an HPUX machine from linux, I use
> a 'nolock' option that disables attempting to lock over NFS, and I just
> use dotlocking. I d
* David T-G <[EMAIL PROTECTED]> [04-12-2001 01:26]:
[context]
| Rene, since starting to use mutt I've never wished delete was set to
| ask-yes, but I sure hated mark_old (though I want stuff marked old at
| times) :-)
That was actually the first option I unset ;)
--
René Clerc
On Mon, Dec 03, 2001 at 07:24:00PM -0500, David T-G wrote:
> % suggested in the other thread), and it successfully created
> % testfile.lock; mutt_dotlock -u testfile successfully removed the file as
> % well.
>
> And this was from your NFS client box? Interesting. I wonder why mutt
> doesn't
On Mon, Dec 03, 2001 at 03:34:45PM -0500, Paul Brannan wrote:
>
> Perhaps this is a problem of the client being able to lock over nfs but
> the server not?
I think that this is exactly the problem... I dont know if you are on
linux, but in my mounts through NIS to an HPUX machine from linux, I u
Paul --
...and then Paul Brannan said...
% On Mon, Dec 03, 2001 at 02:59:31PM -0500, David T-G wrote:
% > ...and then Paul Brannan said...
% >
% > mutt -v
% >
% > show you? Do you have dotlocking available? It looks to me as though
...
%
% The relevant portion of mutt -v indicates:
% -HO
Hi,
* Paul Brannan <[EMAIL PROTECTED]> [01-12-03 21:34]:
>> If you want the messages to be deleted when you sync, set it to "yes" in
>> your macro; if not, leave it at "no" and forget about the macro. If you
>> want to be asked then just set it to ask-no and forget about the macro,
>> and when y
* Paul Brannan <[EMAIL PROTECTED]> [03-12-2001 21:36]:
| > If you want the messages to be deleted when you sync, set it to "yes" in
| > your macro; if not, leave it at "no" and forget about the macro. If you
| > want to be asked then just set it to ask-no and forget about the macro,
| > and when
On Mon, Dec 03, 2001 at 02:59:31PM -0500, David T-G wrote:
> ...and then Paul Brannan said...
> % This solves #2, but not #1 :(
>
> Interesting. What does
>
> mutt -v
>
> show you? Do you have dotlocking available? It looks to me as though
> mutt can only use fcntl locks but they are not s
Paul --
...and then Paul Brannan said...
% On Mon, Dec 03, 2001 at 10:31:53AM -0500, Brendan Cully wrote:
% > > > * Paul Brannan <[EMAIL PROTECTED]> [011130 15:42]:
% > > > > 1) When I start mutt, I see this message:
% > > > > fcntl: No locks available (errno = 37)
% > > > >How can I mak
On Mon, Dec 03, 2001 at 10:31:53AM -0500, Brendan Cully wrote:
> > > * Paul Brannan <[EMAIL PROTECTED]> [011130 15:42]:
> > > > 1) When I start mutt, I see this message:
> > > > fcntl: No locks available (errno = 37)
> > > >How can I make it go away?
> > > > 2) When I go to the index, I s
On Monday, 03 December 2001 at 10:14, Paul Brannan wrote:
> On Sat, Dec 01, 2001 at 08:59:24AM +0100, Sven Guckes wrote:
> > * Paul Brannan <[EMAIL PROTECTED]> [011130 15:42]:
> > > 1) When I start mutt, I see this message:
> > > fcntl: No locks available (errno = 37)
> > >How can I make
* Paul Brannan <[EMAIL PROTECTED]> [03-12-2001 16:16]:
| > use the file locking that goes along with your system?!
|
| Could you please point me to the documentation for specifying a
| different form of file locking? The mutt FAQ and mutt docs at mutt.org
| do not appear to contain such informa
On Sat, Dec 01, 2001 at 08:59:24AM +0100, Sven Guckes wrote:
> * Paul Brannan <[EMAIL PROTECTED]> [011130 15:42]:
> > 1) When I start mutt, I see this message:
> > fcntl: No locks available (errno = 37)
> >How can I make it go away?
>
> use the file locking that goes along with your syst
* Paul Brannan <[EMAIL PROTECTED]> [011130 15:42]:
> 1) When I start mutt, I see this message:
> fcntl: No locks available (errno = 37)
>How can I make it go away?
use the file locking that goes along with your system?!
> 2) When I go to the index, I see this message:
> /home/pbran
1) When I start mutt, I see this message:
fcntl: No locks available (errno = 37)
How can I make it go away?
2) When I go to the index, I see this message:
/home/pbrannan/.mh_profile not found, mh format names disabled
How can I make it go away?
3) When changing between mailboxes,
23 matches
Mail list logo
