--MGYHOYXEY6WxJCY8
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
* Rob 'Feztaa' Park <[EMAIL PROTECTED]>, 2002-07-29 00:31 -0400:
> Alas! Iain Truskett spake thus:
> > * Patrick ([EMAIL PROTECTED]) [29 Jul 2002 12:02]:
> > > *
Elimar --
...and then Elimar Riesebieter said...
%
% On Sun, 28 Jul 2002 the mental interface of Michael Tatge told:
%
% > Elimar Riesebieter ([EMAIL PROTECTED]) muttered:
% > > I've configured my mutt for using gnupg. But when I define a PGP
% > > getkeys command, the display gets corrupted?
.
* On 2002.07.28, in <[EMAIL PROTECTED]>,
* "Lee J. Moore" <[EMAIL PROTECTED]> wrote:
>
> Aaah, I thought with Mutt it was strictly backticks and the pipe
> only came into it with dgc's patch. I should've at least tried
> it out before writing. Thanks! ;)
To clarify this: variables which
--gBBFr7Ir9EOA20Yy
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Andre Berger spake thus:
> By the way, what would an exmaple
> procmail rule to add a sender to the spamassassin blacklist look
> like?
Probably something
How can I control the number of spaces a character uses when reading
mail in the pager? Mutt 1.3.99i.
TIA,
Jim
On Mon, Jul 29, 2002 at 01:22:53PM -0700, Jim Osborn wrote:
> How can I control the number of spaces a character uses when reading
> mail in the pager? Mutt 1.3.99i.
It appears to be hardcoded (to 8). Most versions of curses assume 8.
(ncurses allows you to set it in the TABSTOP variable - whic
Michael Montagne wrote:
> I don't use maildir. Can I still use the Trash feature in version 1.4?
> Currently I'm using 1.3.28-bf1, but a recent apt-get upgraded me to 1.4
> and now my trash directive in .muttrc generates an error.
i'm assuming that you're using debian since you mention apt. i'm
Michael --
...and then Michael Montagne said...
%
% I don't use maildir. Can I still use the Trash feature in version 1.4?
% Currently I'm using 1.3.28-bf1, but a recent apt-get upgraded me to 1.4
% and now my trash directive in .muttrc generates an error.
What is that directive?
I suspect th
I don't use maildir. Can I still use the Trash feature in version 1.4?
Currently I'm using 1.3.28-bf1, but a recent apt-get upgraded me to 1.4
and now my trash directive in .muttrc generates an error.
--
Michael Montagne [[EMAIL PROTECTED]] 503.226.1575
--
>On 29/07/02, from the brain of David T-G tumbled:
> Michael --
>
> ...and then Michael Montagne said...
> %
> % I don't use maildir. Can I still use the Trash feature in version
> 1.4?
> % Currently I'm using 1.3.28-bf1, but a recent apt-get upgraded me to
> 1.4
> % and now my trash directive
At 4:49 PM EDT on July 29 Rob 'Feztaa' Park sent off:
> Alas! Andre Berger spake thus:
> > By the way, what would an exmaple
^^
It's not mutt, but since I don't have time to read the procmail list...
> > procmail rule to add a sender to the spamassassin blacklist look
> > like?
>
>
Michael Montagne wrote:
>> I suspect that the mutt you were using before had Cedric Duval's
>> trash folder patch applied and that the new one doesn't.
> Yes, that's true. I assumed it would be included in 1.4 by default.
> Do I need to switch to maildir to get the same functionality?
the $ma
* Thomas E. Dickey <[EMAIL PROTECTED]> [2002-07-29 21:37]:
> On Mon, Jul 29, 2002 at 01:22:53PM -0700, Jim Osborn wrote:
> > How can I control the number of spaces a character
> > uses when reading mail in the pager? Mutt 1.3.99i.
>
> It appears to be hardcoded (to 8).
> Most versions of curses a
On Tue, Jul 30, 2002 at 01:53:57AM +0200, Sven Guckes wrote:
> * Thomas E. Dickey <[EMAIL PROTECTED]> [2002-07-29 21:37]:
> > On Mon, Jul 29, 2002 at 01:22:53PM -0700, Jim Osborn wrote:
> > > How can I control the number of spaces a character
> > > uses when reading mail in the pager? Mutt 1.3.99
* Thomas E. Dickey <[EMAIL PROTECTED]> [2002-07-30 00:07]:
> I added the ^T (toggle tabs) to tin sometime around 1994.
> There are a lot of newspostings that assume tabs are set to 4.
> So it's probably useful in some contexts. People
> tend to not format their email quite as rigorously...
> But
I am a mutt newbie. It seems to me that configuration of mutt would be
easier if:
* muttrc contains the entire set of mutt configuration variables (variables
not applicable to the particular installation may be commented out, using #)
* the configuration variables are grouped in categories, s
--8P1HSweYDcXXzwPJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Russell L. Harris spake thus:
> I am a mutt newbie. It seems to me that configuration of mutt would be=
=20
> easier if:
>=20
> * muttrc contains the entir
17 matches
Mail list logo