Re: delete-thread key combination?

[Matthias Apitz]

El día Thursday, May 23, 2019 a las 08:16:31AM +0200, Wim escribió:

> Hi Jude,
> 
> On Thursday, 23 May at 00:27, Jude DaShiell wrote:
> 
> > that's listed as ^D.  Does that convention translate to shift-6 then type
> > upper-case D?
> >
> 
> That means one's got to press the 'Esc' and the 'd' keys at the same
> time.

Isn't this Ctrl+D at the same time? At least this is what I use to
delete full threads without reading them.

Btw: When I compare mutt with the MUA app on my Ubuntu phone (Dekko),
this deletion of full threads is what I most miss in this MUA, esp. if
one is subscribed to a lot of technical mailing lists and often it
happens that a thread is of no interest or one can't say anything in
this for help.

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
Public GnuPG key: http://www.unixarea.de/key.pub
May, 9: Спаси́бо освободители! Thank you very much, Russian liberators!

Re: delete-thread key combination?

[Wim]

Hi Matthis,

On Thursday, 23 May at 09:07, Matthias Apitz wrote:

> El día Thursday, May 23, 2019 a las 08:16:31AM +0200, Wim escribió:
>
> > Hi Jude,
> >
> > On Thursday, 23 May at 00:27, Jude DaShiell wrote:
> >
> > > that's listed as ^D.  Does that convention translate to shift-6 then type
> > > upper-case D?
> > >
> >
> > That means one's got to press the 'Esc' and the 'd' keys at the same
> > time.
>
> Isn't this Ctrl+D at the same time? At least this is what I use to
> delete full threads without reading them.
>
> Btw: When I compare mutt with the MUA app on my Ubuntu phone (Dekko),
> this deletion of full threads is what I most miss in this MUA, esp. if
> one is subscribed to a lot of technical mailing lists and often it
> happens that a thread is of no interest or one can't say anything in
> this for help.
>

I find the 'collapse-all' threads switch very good for handling
uninteresting threads.

>   matthias
>
> --
> Matthias Apitz, ✉ g...@unixarea.de, http://www.unixarea.de/ +49-176-38902045
> Public GnuPG key: http://www.unixarea.de/key.pub
> May, 9: Спаси́бо освободители! Thank you very much, Russian liberators!

--
Grüße Wim
  |\  _,,,---,,_
ZZZzz /,`.-'`'-.  ;-;;,_
 |,4-  ) )-,_. ,\ (  `'-'
'---''(_/--'  `-'\_)

Re: Can I do this (should I do this) with Mutt?

[John Long]

Thank you for a superb, helpful email Cameron.

I'll go over this and a few things posted upthread and come back with
questions later.

Thanks,

/jl


On Thu, 23 May 2019 09:56:08 +1000
Cameron Simpson  wrote:

> On 22May2019 15:03, John Long  wrote:
> >I have around 10 email accounts I use actively for various mailing
> >lists, work, personal etc.
> >
> >1. Is it reasonable to use Mutt with many email accounts? I know you
> >probably can, but is it reasonable as in, is it manageable, is the
> >performance good enough on a midrange box. Usability stuff, like will
> >mutt automagically respond using the correct account (the account the
> >email I'm replying to was received by), is it clear when you compose
> >which account you're using. Etc.  
> 
> You need to orchestrate switching accounts if you want it
> particularly easy.
> 
> Someone has posted a folder hook which switches their From: header if 
> they enter that folder. I don't entirely work that way myself.
> 
> I've got:
> 
> - an "alternates" regexp matching my various email addresses; this
> lets mutt know what email is to me versus some list
> 
> - some reply-hooks to fiddle the from in some settings; for example I 
>   switch to my gmail address if theres an @googlegroups.com address 
>   present because Google's stupid that way; some of my mailing list 
>   subscriptions are unavoidably google groups.
> 
> - some folder hooks, which exist essentially to fiddle my settings
> when I use IMAP directly from mutt to match the imap target.
>   My normal use is local folders, like you.
> 
> Someone else should describe account-hooks - I suspect I'm misusing 
> mine.
> 
> >2. I have around 100,000 emails right now between all my accounts.  
> 
> That's nothing large.
> 
> I do recommend using a mail indexer for big searches. I use notmuch 
> myself, via some simple wrapper scripts for ease of use. It is easy
> to have a cron job or something maintain this silently; you can just
> ignore it until you need it.
> 
> >I have one pop account because my ISP mail server doesn't support
> >IMAP. I use IMAP with all the rest.  
> 
> This should be ok.
> 
> >I like having the email on my box(es)
> >rather than leaving it on servers.  
> 
> So do I. Do you _remove_ it from the servers or just keep it synched?
> 
> >Of the mailbox flavors, which is
> >appropriate for this volume of email?...and also for the let's say
> >200 a day I get between the various mailing lists I'm on.  
> 
> Only 200? Again, nothing unreasonable there.
> 
> Use Maildir. It uses one file per message and is explicitly designed
> for lock free activity, meaning you can point multiple mutts or other
> tools at a mailbox without worrying about conflict.
> 
> I us compressed mboxes for archive folders though. Simply more
> compact. They are not folders I access regularly though.
> 
> >3. I seem to remember that mutt didn't poll automagically for pop3 or
> >IMAP or both. Is that still true? Is there a way to get mutt to check
> >mail every 10 minutes, 15, etc. without middleware? I don't want to
> >get into fetchmail, getmail etc. I want the client to do it all.  
> 
> I think this is the wrong choice. 
> 
> It is good to separate the mail fetching and sending from the mail 
> reading. That way it can just tick along independently of your mutt
> (or other tool) use.
> 
> Let a fetcher collect email, and just have mutt poll folders (which
> it does).
> 
> For myself, I fetch my email from various accounts using getmail 
> regularly, with a short delay before the next poll. It all gets 
> delivered into my +spool folder.
> 
> I send email via my local mail system i.e. just the local "sendmail" 
> command (postfix on a Mac for the laptop, postfix on an Ubuntu system 
> for the home server).  This avoids all sorts of problems configuring 
> mutt (and other tools) - you do it once, for the system mail. Then: 
> _everything_ can send email, and you can dispatch email while offline
> - it'll go out when you're online again, courtesy of the mail system
> being a proper mail system.
> 
> Nor do I file messages with mutt (except by hand of course on an 
> occasional ad hoc basis). Like most mutters I file messages with a 
> separate rule based programme. Procmail is popular, but it tends to
> be integrated into the fetching. I have my own gripes with that and
> with procmail itself, and use my own filer (mailfiler). It monitors
> the +spool folder, and files anything which appears there according
> to text based rule files.
> 
> One consequence of this is that I do pull messages from my ISP
> inboxes, emptying them.
> 
> If you wish to keep the upstrwam populated (for example a work IMAP
> mail folder structure) you might use offline-imap, which will
> maintain a bidirectional mirror of an IMAP server with a set of local
> folders. Changes upstream come down, and changes you make locally go
> back up. So you can work on the local folders and know that the
> upstream IMAP will reflect that.
> 
> Mailfiler 

Re: NeoMutt 20170113 (1.7.2) (debian9) segfaults on readonly mbox

[Kevin J. McCarthy]

On Wed, May 22, 2019 at 11:42:39PM -0700, Will Yardley wrote:

On Thu, May 23, 2019 at 08:24:11AM +0200, Alexander Dahl wrote:

On Thu, May 23, 2019 at 01:47:15PM +1000, m...@raf.org wrote:



> This might not be the right place to report this but

Is the mutt mailing list the right place to discuss neomutt problems?
(Serious question, I don't actually know.)


Short answer (not an official one, but just based on the discussion I've
seen), no.


In general, as Will says, no.  But segfaults are always of interest, in 
case the bug is present in Mutt too.  Particularly for easy to 
reproduce, clearly common functionality.


In this case, the bug was fixed in commit 786aa6cf for release 1.8.1.

I like to encourage people to post to mutt-users first, as was done 
here, and if it's clear there is a bug in Mutt, create a ticket on 
gitlab: .


--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA


signature.asc
Description: PGP signature