with the FreeBSD's
> > Beastie in the right corner.
>
> What? Do you run FreeBSD and Mutt on the phone?
I use the Purism L5 as my daily driver, see https://puri.sm/products/librem-5/
This runs PureOS, a Debian flavor. On my laptops I run FreeBSD CURRENT
and copied the Beastie.eps file
On Wed, Apr 10, 2024 at 07:25:11AM +0200, Matthias Apitz wrote:
> El día martes, abril 09, 2024 a las 06:54:46 -0400, H escribió:
>
> > On 04/07/2024 07:42 AM, Matthias Apitz wrote:
> > > I do use on FreeBSD muttprint:
> > >
> > > Name : muttprint Version: 0.73_5 Installed
> > >
On Wed, Apr 10, 2024 at 10:23:37AM +0200, Matthias Apitz wrote:
I wasn't aware before, that muttprint exists for my mobile phone as
well. I've now installed it and configured it, even with the FreeBSD's
Beastie in the right corner.
What? Do you run FreeBSD and Mutt on the phone?
On 2024-04-10, Matthias Apitz wrote:
> El día martes, abril 09, 2024 a las 06:54:46 -0400, H escribió:
>
>> On 04/07/2024 07:42 AM, Matthias Apitz wrote:
>> > I do use on FreeBSD muttprint:
>> >
>> > Name : muttprint
>> > Version: 0.73_5
[...]
>> > WWW:
El día miércoles, abril 10, 2024 a las 07:25:11 +0200, Matthias Apitz escribió:
> I could make it available on my Internet host. About any RPM I don't
> know much. On my Linux mobilephone, running a Debian I see:
>
> $ apt search muttprint
> muttprint/byzantium 0.73-10 all
> Pretty printing of
El día martes, abril 09, 2024 a las 06:54:46 -0400, H escribió:
> On 04/07/2024 07:42 AM, Matthias Apitz wrote:
> > I do use on FreeBSD muttprint:
> >
> > Name : muttprint
> > Version: 0.73_5
> > Installed on : Sun Sep 24 11:32:52 2023 CEST
> > Origin : print/muttprint
On 04/07/2024 07:42 AM, Matthias Apitz wrote:
> I do use on FreeBSD muttprint:
>
> Name : muttprint
> Version: 0.73_5
> Installed on : Sun Sep 24 11:32:52 2023 CEST
> Origin : print/muttprint
> Architecture : FreeBSD:14:amd64
> Prefix : /usr/local
> Categories
I do use on FreeBSD muttprint:
Name : muttprint
Version: 0.73_5
Installed on : Sun Sep 24 11:32:52 2023 CEST
Origin : print/muttprint
Architecture : FreeBSD:14:amd64
Prefix : /usr/local
Categories : print mail
Licenses : GPLv2
Maintainer :
Hello!
On Wed, Nov 24, 2021 at 05:21:10PM +, Jean Louis wrote:
> * Anders Damsgaard [2021-11-22 12:05]:
> > * Globe Trotter via Mutt-users [2021-11-22 00:47:10
> > +]:
> > > What is the recommended way to pretty-print mutt emails? I found a
> > &g
On Sat, Mar 30, 2024 at 11:21:21AM -0700, googly.negotiator...@aceecat.org
wrote:
> ...this type of issue is really tricky because one has to be sure to
> *build* against the packaged (i.e. non-base) libraries, including
> cases like libncurses. IIRC this is far from automatic, some packages
> as
On Sat, Mar 30, 2024 at 09:21:53AM -0400, Derek Martin wrote:
> > "Programs in the OpenBSD base system ignore the locale except for
> > the character encoding..."
> Mutt is not part of the "base system" so the limitation on locale
> should not apply to it,
ou confirmed that locale was correct, did you then try
> Mutt?
I did. However, I set the LANG variable in .profile and .kshrc files,
which I think was the problem. Because, LANG (and the rest) wasn't
updated when in the new session.
> In either case--whether you set only LANG or only LC_CTYPE--you
> attention to the LANG variable. Thw following is an excerpt from the
> locale man page:
I don't have an OpenBSD system to test on, so I can't investigate
further, but I wouldn't think so, because:
> "Programs in the OpenBSD base system ignore the locale except for the
> character
II, but you've explicitly told xterm to use Unicode.
> That's wrong.
>
> The TL;DR of this is:
>
> 1. You should NEVER need to set Mutt's charset explicitly. [*]
> 2. Your shell, Mutt, and X should all inherit what they need from your
>LANG environment variable, assuming it is set prope
e been answering it
on this list ever since... seriously, see this post from 2006:
https://marc.info/?l=mutt-users=114434601817142=2
Things were A LOT worse then--Unicode hadn't really been adopted very
much in 2004. Some of the finer details of how (or rather where) to
set those settings keep ch
ut you've explicitly told xterm to use Unicode.
> That's wrong.
>
> The TL;DR of this is:
>
> 1. You should NEVER need to set Mutt's charset explicitly. [*]
> 2. Your shell, Mutt, and X should all inherit what they need from your
>LANG environment variable, assuming it is
incorrect--even if it appears to have solved your issue). By having
LANG unset, you've told your shell (and therefore everything started
by it) to use ASCII, but you've explicitly told xterm to use Unicode.
That's wrong.
The TL;DR of this is:
1. You should NEVER need to set Mutt's charset expl
On 2024-03-23 12:52:40, Sirius Rayner-Karlsson via Mutt-users wrote:
> In days of yore (Sat, 23 Mar 2024), Sadeep Madurange thus quoth:
> > On 2024-03-23 11:10:11, Sirius via Mutt-users wrote:
> > > In days of yore (Sat, 23 Mar 2024), Sadeep Madurange thus quoth:
&
In days of yore (Sat, 23 Mar 2024), Sadeep Madurange thus quoth:
> On 2024-03-23 11:10:11, Sirius via Mutt-users wrote:
> > In days of yore (Sat, 23 Mar 2024), Sadeep Madurange thus quoth:
> > > When I view the following email in mutt, I see a bunch of question marks
>
On 2024-03-23 11:10:11, Sirius via Mutt-users wrote:
> In days of yore (Sat, 23 Mar 2024), Sadeep Madurange thus quoth:
> > When I view the following email in mutt, I see a bunch of question marks
> > where the spaces are. I checked the codepoints and they all seem to be
>
In days of yore (Sat, 23 Mar 2024), Sadeep Madurange thus quoth:
> Hello,
>
> When I view the following email in mutt, I see a bunch of question marks
> where the spaces are. I checked the codepoints and they all seem to be
> the normal space (0x20) character in the ASCII tab
Hello,
When I view the following email in mutt, I see a bunch of question marks
where the spaces are. I checked the codepoints and they all seem to be
the normal space (0x20) character in the ASCII table.
This happens fairly often. Usually with git patches or emails hat
contain the output
Hi Mutt Users,
I've just released version 2.2.13. Instructions for downloading are available
at <http://www.mutt.org/download.html>, or the tarball can be directly
downloaded from <http://ftp.mutt.org/pub/mutt/>. Please take the time to
verify the signature file against my
On 2023-10-29 14:17, Michael Kjörling wrote:
> On 29 Oct 2023 14:44 +0100, from mutt-users@mutt.org (Jan Eden via
> Mutt-users):
> > for several years, I have used mutt with msmtp, and issues with sending
> > messages were usually returned to mutt and displayed as an error.
On 29 Oct 2023 14:44 +0100, from mutt-users@mutt.org (Jan Eden via Mutt-users):
> for several years, I have used mutt with msmtp, and issues with sending
> messages were usually returned to mutt and displayed as an error.
>
> Recently, though, mutt displays "Mai
Hi,
for several years, I have used mutt with msmtp, and issues with sending
messages were usually returned to mutt and displayed as an error.
Recently, though, mutt displays "Mail sent" even when there is a problem
(and the mail is not sent). I always used a simple msmtp configuration,
Dear Sébastien,
Il 12 settembre 2023 alle 16:07 Sébastien Hinderer ha scritto:
> Dear all,
>
> Here is something I have been wanting for a long time.
>
> For those who don't know, the email notifications sent by GitHub do have
> all the information to unsubscribe from the corresponding thread
/notifications/unsubscribe/ - | \
sed -e 's///g'`
curl -s $url > /dev/null 2>&1
```
And then the mutt macro to invoke that script from the index and pager:
# Unsubscribe from GitHub notifications
macro index,pager "," "github-unsubscribe\n" "Unsubscribe from
GitHub notifications"
Enjoy,
Seb.
Hello Mutt Users,
I've just released version 2.2.12. Instructions for downloading are
available at <http://www.mutt.org/download.html>, or the tarball can be
directly downloaded from <http://ftp.mutt.org/pub/mutt/>. Please take
the time to verify the signature file against my
Hello Mutt Users,
I've just released version 2.2.11. Instructions for downloading are
available at <http://www.mutt.org/download.html>, or the tarball can be
directly downloaded from <http://ftp.mutt.org/pub/mutt/>. Please take
the time to verify the signature file against my
on a different machine (but same version), and that seemed to
resolve it.
I created an issue here:
https://gitlab.com/muttmua/mutt/-/issues/451
since that seems like a better way to track this now that I know this
was an actual issue.
Thanks Will. I've merged this fix into the stable branch and will get
On Tue, Aug 15, 2023 at 12:39:34PM +0800, Kevin J. McCarthy wrote:
> On Mon, Aug 14, 2023 at 02:02:52PM -0700, Will Yardley wrote:
> > Building latest mutt (2.2.10) on latest Ventura (13.5) (using homebrew
> > for all the deps), and getting errors like this for gpg-error and a
On Mon, Aug 14, 2023 at 02:02:52PM -0700, Will Yardley wrote:
Building latest mutt (2.2.10) on latest Ventura (13.5) (using homebrew
for all the deps), and getting errors like this for gpg-error and a
similar one for gpgme itself (side note: the actual problem I'm trying
to fix is weird screen
Building latest mutt (2.2.10) on latest Ventura (13.5) (using homebrew
for all the deps), and getting errors like this for gpg-error and a
similar one for gpgme itself (side note: the actual problem I'm trying
to fix is weird screen redraw artifacts since updating OS X with the
version I'd had
Kevin J. McCarthy (2023/07/29 18:07 +0800):
> On Sat, Jul 29, 2023 at 11:38:00AM +0200, Sébastien Hinderer wrote:
> > Has anybody already set-up such a feature? Would be interested in the
> > details on (1) then.
>
> If you don't mind using the mailto URL, Mutt 2.1+ ha
On Sat, Jul 29, 2023 at 11:38:00AM +0200, Sébastien Hinderer wrote:
Has anybody already set-up such a feature? Would be interested in the
details on (1) then.
If you don't mind using the mailto URL, Mutt 2.1+ has ,
bound to 'Esc-L' by default.
--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3
Dear all,
I would like to be able to unscribe from GitHub threads directly from
within mutt (the index, say).
I noticed that the emails sent by GitHubcontain this Header:
List-Unsubscribe:
<mailto:unsub+to...@reply.github.com>,
<https://github.com/notifications/unsubscr
On Fri, May 05, 2023 at 12:37:02PM EDT, Derek Schrock wrote:
> Hello, I'm looking for any FreeBSD ports/pkg users of mail/mutt and
> hoping to get some feedback on option usage and which non-standard
> features you're using from the port's included extra patches. This
> is mainly
On Fri, May 19, 2023 at 08:07:00AM -0400, José María Mateos wrote:
I think this is very close to what I'd like to do, but going to
text/html, displaying the message, then switch back to text/plain
again. I'm going to play around with this to see if I can manage to get
the desired effect,
On Fri, May 19, 2023 at 02:54:46AM +0200, Mihai Lazarescu wrote:
I use this macro:
macro pager ~ 'unalternative_order *alternative_order
text/html text/enriched text/plain'
to switch to HTML and this:
macro pager '`' 'unalternative_order *alternative_order
text/plain text/enriched
On Thursday, May 18, 2023 at 19:53:50 -0400, José María Mateos wrote:
2. If I'm not convinced by that version, press some key and
then text/html is displayed inline (using w3m, lynx, links, or
whatever in the ~/.mailcap file).
I use this macro:
macro pager ~ 'unalternative_order
On Fri, May 05, 2023 at 05:58:21PM +, Tim Chase wrote:
On 2023-05-05 12:37, Derek Schrock wrote:
Hello, I'm looking for any FreeBSD ports/pkg users of mail/mutt and
:raises hand:
hoping to get some feedback on option usage and which non-standard
features you're using from the port's
On Fri, May 05, 2023 at 12:37:02PM -0400, Derek Schrock wrote:
Hello, I'm looking for any FreeBSD ports/pkg users of mail/mutt and
hoping to get some feedback on option usage and which non-standard
features you're using from the port's included extra patches. This
is mainly the *_PATCH options
On Fri, May 05, 2023 at 12:37:02PM -0400, Derek Schrock wrote:
>Hello, I'm looking for any FreeBSD ports/pkg users of mail/mutt and
>hoping to get some feedback on option usage and which non-standard
>features you're using from the port's included extra patches. This
>is mainly
On 2023-05-05 12:37, Derek Schrock wrote:
> Hello, I'm looking for any FreeBSD ports/pkg users of mail/mutt and
:raises hand:
> hoping to get some feedback on option usage and which non-standard
> features you're using from the port's included extra patches. This
> is mainly the *_P
Hello, I'm looking for any FreeBSD ports/pkg users of mail/mutt and
hoping to get some feedback on option usage and which non-standard
features you're using from the port's included extra patches. This
is mainly the *_PATCH options.
You can find the post to the FreeBSD ports mailing here
On Sat, Mar 25, 2023 at 02:12:00PM -0700, Kevin J. McCarthy wrote:
> Hi Mutt Users,
>
> I've just released version 2.2.10.
Thanks for the many updates and improvements and maintenance.
That's all I have to say but since I haven't posted to this list this
decade, maybe even last one,
Hi Mutt Users,
I've just released version 2.2.10. Instructions for downloading are
available at <http://www.mutt.org/download.html>, or the tarball can be
directly downloaded from <http://ftp.mutt.org/pub/mutt/>. Please take
the time to verify the signature file against my
On 19Mar2023 09:52, Peng Yu wrote:
I use the following python code to download UNDELETED messages. But it
will fetch all messages without considering whether an message has
been downloaded previously. How does mutt solve this problem to only
download the emails that have not been downloaded
Hi,
I use the following python code to download UNDELETED messages. But it
will fetch all messages without considering whether an message has
been downloaded previously. How does mutt solve this problem to only
download the emails that have not been downloaded before.
import email
On Sat, Feb 04, 2023 at 02:48:19PM +0200, e wrote:
If a received mail contains the "Disposition-notification-to:" header
field, what does MUTT do?
Nothing. Mutt ignores the header.
What kind of configuration can you do for MDNs generated by MUTT?
Perhaps my_hdr.
--
Kevin J. Mc
If a received mail contains the "Disposition-notification-to:" header field,
what does MUTT do?
What kind of configuration can you do for MDNs generated by MUTT?
On Mon, Jan 30, 2023 at 04:22:43AM +0200, e wrote:
> On Mon, Jan 30, 2023 at 04:10:45AM +0200, e wrote:
> >
> > Is it possible to use mutt without having an MTA on your own machine? I
> > have read that some MUA's use "Message submission" (rfc 2476)
> >
Is $smtp_url the situation where a MUA is using "Message submission" and it
sends to an MSA?
On Mon, Jan 30, 2023 at 04:10:45AM +0200, e wrote:
>
> Is it possible to use mutt without having an MTA on your own machine? I have
> read that some MUA's use "Message submissi
Is it possible to use mutt without having an MTA on your own machine? I have
read that some MUA's use "Message submission" (rfc 2476)
to send the mail to an MSA that can be on the same network for example. How can
I do this with mutt?
Hi,
I configured notmuch for my mail stores, and use mutt-notmuch
according to the man page[1]:
macro index "unset
wait_key~/bin/mutt-notmuch --prompt
search~/.cache/mutt_results"
mutt is started with the -F parameter, and each parameter (work,
personal etc) refers to a different
On 19Nov2022 09:21, Kevin J. McCarthy wrote:
On Sat, Nov 19, 2022 at 02:32:25PM +1100, Cameron Simpson wrote:
Maybe the docs should have a small mention around `~h` that it
cannot utilise the header cache.
There is a note, "***)", next to ~b, ~B, ~h, ~M, and ~X that mentions
they entail
On 19Nov2022 09:16, Kevin J. McCarthy wrote:
On Sat, Nov 19, 2022 at 02:15:05PM +1100, Cameron Simpson wrote:
On 18Nov2022 18:33, Kevin J. McCarthy wrote:
The headers are colored as they are displayed, but also when any
flags are updated.
If it's only colouring the visible index listing,
On Sat, Nov 19, 2022 at 02:32:25PM +1100, Cameron Simpson wrote:
Maybe the docs should have a small mention around `~h` that it cannot
utilise the header cache.
There is a note, "***)", next to ~b, ~B, ~h, ~M, and ~X that mentions
they entail reading the whole message in and recommends not
On Sat, Nov 19, 2022 at 02:15:05PM +1100, Cameron Simpson wrote:
On 18Nov2022 18:33, Kevin J. McCarthy wrote:
The headers are colored as they are displayed, but also when any
flags are updated.
If it's only colouring the visible index listing, that's fine with me.
No, it's not. I will fix
On 18Nov2022 23:08, Kurt Hackenberg wrote:
On Sat, Nov 19, 2022 at 02:25:50PM +1100, Cameron Simpson wrote:
from https://www.rfc-wiki.org/wiki/RFC2822. Is there a better RFC 2822
page? I used to use a nicely formatted tools.ietf.org URL, but that now
redirects to some RFC author editing ...
On Sat, Nov 19, 2022 at 02:25:50PM +1100, Cameron Simpson wrote:
from https://www.rfc-wiki.org/wiki/RFC2822. Is there a better RFC 2822
page? I used to use a nicely formatted tools.ietf.org URL, but that now
redirects to some RFC author editing ... thing.
Is this better? (For RFC 5322,
On 19Nov2022 14:25, Cameron Simpson wrote:
Anyway, I'll try plain `~f "cameron simnpson"` and see how it goes.
This is nice and fast:
color index white default "((~P|(%f polyname ~f 'cameron simpson'))) | (~v
~((~P|(%f polyname ~f 'cameron simpson'"
and does the same colouring I
On 18Nov2022 18:33, Kevin J. McCarthy wrote:
On Sat, Nov 19, 2022 at 08:32:39AM +1100, Cameron Simpson wrote:
It sure looks like it is being applied to the entire folder
contents, instead of only the lines being displayed. That is a
massive performance hit for a big folder. Is that the case?
TW ~() can also be very expensive.
If you mean: it involves walking the thread trees, I accept that. The
win of having most threads callapsed but ocrrectly coloured outwieghs
that. My naive perusing of the mutt code suggests that the thread
structure itself is in memory, yes?
Is there an eff
On 18Nov2022 18:33, Kevin J. McCarthy wrote:
On Sat, Nov 19, 2022 at 08:32:39AM +1100, Cameron Simpson wrote:
It sure looks like it is being applied to the entire folder
contents, instead of only the lines being displayed. That is a
massive performance hit for a big folder. Is that the case?
On Sat, Nov 19, 2022 at 01:16:47PM +1100, Cameron Simpson wrote:
On 19Nov2022 08:32, Cameron Simpson wrote:
The issue is my index colouring, specificly this line:
color index white default "((~P|%f polyname ~h '^from:.*cameron simpson')) | (~v
~((~P|%f polyname ~h '^from:.*cameron
On Sat, Nov 19, 2022 at 08:32:39AM +1100, Cameron Simpson wrote:
It sure looks like it is being applied to the entire folder contents,
instead of only the lines being displayed. That is a massive
performance hit for a big folder. Is that the case?
The headers are colored as they are
On 19Nov2022 08:32, Cameron Simpson wrote:
The issue is my index colouring, specificly this line:
color index white default "((~P|%f polyname ~h '^from:.*cameron simpson')) | (~v
~((~P|%f polyname ~h '^from:.*cameron simpson')))"
This colours messages as white if they're from me or from
On 19Nov2022 07:55, Cameron Simpson wrote:
On 18Nov2022 09:38, Kevin J. McCarthy wrote:
source ~/rc/mutt/aliases-auto
8407 aliases, nearly 2MB in size :-)
Yes, Mutt's internal structures used for aliases are not designed for
that many.
It's not the number of aliases. I've just stripped
On 18Nov2022 09:38, Kevin J. McCarthy wrote:
source ~/rc/mutt/aliases-auto
8407 aliases, nearly 2MB in size :-)
Really, it is a bit excessive. Particularly since I think I don't
ever use aliases anyway.
Yes, Mutt's internal structures used for aliases are not designed for
that many
On Wed, Nov 16, 2022 at 10:15:48AM +0100, Bastian wrote:
> On 15Nov22 23:36-0600, Ranjan Maitra wrote:
> > On Tue Nov15'22 12:33:32AM, Mihai Lazarescu wrote:
> > > You can select the attachments you want from one source message, then
> > > reply
> > > (r) or f
/mutt/aliases-auto
8407 aliases, nearly 2MB in size :-)
Really, it is a bit excessive. Particularly since I think I don't ever
use aliases anyway.
Yes, Mutt's internal structures used for aliases are not designed for
that many. It could lead to quite a slowdown in some circumstances. Do
you
made no difference, still
nice and fast. Even my macros to collapse/uncollapse certain patterns
seem basicly free.
So I started adding back in my config files (I source a few). Here's the
glaring one:
source ~/rc/mutt/aliases-auto
8407 aliases, nearly 2MB in size :-)
Really, it is a bit
On 15Nov22 23:36-0600, Ranjan Maitra wrote:
> On Tue Nov15'22 12:33:32AM, Mihai Lazarescu wrote:
> > You can select the attachments you want from one source message, then reply
> > (r) or forward (f) and mutt will ask whether to attach them to the new
> > message.
>
> T
On Tue Nov15'22 12:33:32AM, Mihai Lazarescu wrote:
> From: Mihai Lazarescu
> Date: Tue, 15 Nov 2022 00:33:32 +0100
> To: mutt-users@mutt.org
> Subject: Re: [Mutt] attach file from another email to current email
>
> On Monday, November 14, 2022 at 10:30:01 -0600, Ranjan Maitra
On Wed, Nov 16, 2022 at 11:43:39AM +1100, Cameron Simpson wrote:
The stuff before the "Sorting mailbox..." phase seems ... fast enough.
During the "Sorting mailbox..." phase I see mutt reading message files
I'd not expect it to need to touch, _and_ making some temporary fi
line:
mutt -f ~/mail/python -e fcc-hook . ~/mail/python; save-hook .
~/mail/OLD/2022/python
(That's from ps; the `-e` argument is a single string of course.)
The stuff before the "Sorting mailbox..." phase seems ... fast enough.
During the "Sorting mailbox..." phas
, and then include it,
which seems unnecessary and so I suspect that it is possible to directly add an
attachment from an email in one of my mail-folders.
You can select the attachments you want from one source message,
then reply (r) or forward (f) and mutt will ask whether to attach
them to the new message
Hello Mutt Users,
I've just released version 2.2.9. Instructions for downloading are
available at <http://www.mutt.org/download.html>, or the tarball can be
directly downloaded from <http://ftp.mutt.org/pub/mutt/>. Please take
the time to verify the signature file against my
Hello Mutt Users,
I'm pleased to announce the release of version 2.2.8. Instructions for
downloading are available at <http://www.mutt.org/download.html>, or the
tarball can be directly downloaded from <http://ftp.mutt.org/pub/mutt/>.
Please take the time to verify the signature
.
...of interest to Mutt users, so I don't think it's so badly OT here.
But feel free to continue via private email should you need to ask me
something and prefer not to keep using the list.
Cheers,
Ángel
On Sun, Oct 16, 2022 at 03:25:32AM +0200, Angel M Alganza wrote:
> On Sat, Oct 15, 2022 at 10:27:29PM +0100, Chris Green wrote:
>
> >> How do I get it into interactive mode? I.e. run imapfilter with the
> >> /home/chris/.imapfilter/config.lua configuration and then allow me to
> >> run some
On Sat, Oct 15, 2022 at 10:27:29PM +0100, Chris Green wrote:
How do I get it into interactive mode? I.e. run imapfilter with the
/home/chris/.imapfilter/config.lua configuration and then allow me to
run some commands to actually do things.
All the examples I can find seem to actually put
On Sat, Oct 15, 2022 at 10:27:29PM +0100, Chris Green wrote:
How do I get it into interactive mode? I.e. run imapfilter with the
/home/chris/.imapfilter/config.lua configuration and then allow me to
run some commands to actually do things.
All the examples I can find seem to actually put
On Sat, Oct 15, 2022 at 09:04:37PM +0100, Chris Green wrote:
> On Sat, Oct 15, 2022 at 08:46:17PM +0100, Chris Green wrote:
> > Hmmm.
> >
> > I've installed imapfilter on my xubuntu linux system and I've created
> > an imapfilter config file:-
> >
> > cwebin {
> > server =
On Sat, Oct 15, 2022 at 08:46:17PM +0100, Chris Green wrote:
> Hmmm.
>
> I've installed imapfilter on my xubuntu linux system and I've created
> an imapfilter config file:-
>
> cwebin {
> server = 'mail.gridhost.co.uk',
> username = 'c...@isbd.co.uk',
> password =
On Sat, Oct 15, 2022 at 08:10:03PM +0200, Angel M Alganza wrote:
> Hi Chris,
>
> On Sat, Oct 15, 2022 at 06:29:37PM +0100, Chris Green wrote:
>
> > I'm now considering using mutt to move some IMAP folders from one
> > server to another, both IMAP servers will be remote.
Hi Chris,
On Sat, Oct 15, 2022 at 06:29:37PM +0100, Chris Green wrote:
I'm now considering using mutt to move some IMAP folders from one
server to another, both IMAP servers will be remote. Is this a
sensible idea or should I look for a specialised tool?
I have ocasionally used Mutt
On Saturday, 15.10.2022 at 18:29 +0100, Chris Green wrote:
> I am a long time user of mutt (many, many years). I use it with mail
> delivered directly to a maildir hierarchy.
>
> I have occasionally tried it with IMAP4 but it never seemed to be
> ideal to me. However I'm now co
I am a long time user of mutt (many, many years). I use it with mail
delivered directly to a maildir hierarchy.
I have occasionally tried it with IMAP4 but it never seemed to be
ideal to me. However I'm now considering using mutt to move some IMAP
folders from one server to another, both IMAP
On Sun, Oct 02, 2022 at 09:43:47AM +1100, Cameron Simpson wrote:
> On 01Oct2022 09:33, Chris Green wrote:
> >As I said though it seems odd that only mutt suffers from the problem
> >(on my xubuntu systems anyway). Presumably both 'less' and my editor
> >'vile' use ncurses t
On 01Oct2022 09:33, Chris Green wrote:
As I said though it seems odd that only mutt suffers from the problem
(on my xubuntu systems anyway). Presumably both 'less' and my editor
'vile' use ncurses too and they just wrap long lines if you tell them
to do so.
I'm pretty sure that less does
e a talk with Tom Dickey who is the maintainer of
> > both vile and ncurses, he may be able to throw some light on this.
>
> Workaround: while viewing an affected email in Mutt, press the vertical
> bar key (`|`) and then type `less`. This will pipe the email to Less -
> which, as yo
ght on this.
Workaround: while viewing an affected email in Mutt, press the vertical
bar key (`|`) and then type `less`. This will pipe the email to Less -
which, as you've noted, is unaffected by the issue. You can then select
URLs or other long whitespace-free text strings per your terminal's
n
On Sat, Oct 01, 2022 at 01:24:37PM +0800, Kevin J. McCarthy wrote:
> On Fri, Sep 30, 2022 at 02:42:09PM +0100, Chris Green wrote:
> >I'm am also pretty sure that it's the mutt pager doing this as other
> >programs (i.e. less) wrap long lines in a terminal window but don'
On Fri, Sep 30, 2022 at 02:42:09PM +0100, Chris Green wrote:
I'm am also pretty sure that it's the mutt pager doing this as other
programs (i.e. less) wrap long lines in a terminal window but don't
chop them into pieces like mutt's pager.
Mutt uses ncurses to draw on the screen, which
On Fri, Sep 30, 2022 at 08:55:28PM +0200, Marcus C. Gottwald wrote:
>
> Chris Green wrote (Fri 2022-Sep-30 14:42:09 +0100):
>
> > So, when there is a long string of text in a message that is longer
> > than the width of the terminal and has no spaces in it mutt *always
Chris Green wrote (Fri 2022-Sep-30 14:42:09 +0100):
> So, when there is a long string of text in a message that is longer
> than the width of the terminal and has no spaces in it mutt *always*
> breaks the line at the RHS of the terminal window and displays the
> rest of the line
I have been playing with the various mutt settings which affect how
long lines are managed (in the pager in particular).
By 'long lines' I mean strings of text which have no spaces in them
and which are longer than the width of the terminal window. The
handling of text made up of words
1 - 100 of 9624 matches
Mail list logo
