Re: FreeBSD ports mail/mutt feature patches
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 the *_PATCH options. > > You can find the post to the FreeBSD ports mailing here on the possible > plan of what's to come for the port. At a minimum removal of the quote > patch however the possible removal of all feature patches (including > maildir mtime). > > https://lists.freebsd.org/archives/freebsd-ports/2023-May/003815.html > > If you are a user of this port/pkg please let me know such that I can > gauge the importance of this. > > Also, wondering if any attempts have been made to include these features > in to mutt itself? There's some overlap here with neomutt which is a > possible option if the feature patch is removed. However, I do know > that the project in some cases is not fully open to accepting any/all > patches requested which is fine. If anyone wants to comment/test anything. https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=272194 https://reviews.freebsd.org/D40754
FreeBSD ports mail/mutt feature patches
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 the possible plan of what's to come for the port. At a minimum removal of the quote patch however the possible removal of all feature patches (including maildir mtime). https://lists.freebsd.org/archives/freebsd-ports/2023-May/003815.html If you are a user of this port/pkg please let me know such that I can gauge the importance of this. Also, wondering if any attempts have been made to include these features in to mutt itself? There's some overlap here with neomutt which is a possible option if the feature patch is removed. However, I do know that the project in some cases is not fully open to accepting any/all patches requested which is fine.
Re: searching for emails by date using mutt
On Thu, Aug 18, 2022 at 10:33:13PM EDT, Ranjan Maitra wrote: > Hi, > > Is there a way, in mutt, to search for emails sent on a specific date? Say > emails sent on September 22 2010? > > Many thanks, > Ranjan > l to limit the box while index Start reading here http://www.mutt.org/doc/manual/#patterns-modifier You'll get to 3.4 for date info and examples.
Re: Getting color on FreeBSD
On Thu, Aug 22, 2019 at 08:14:28PM EDT, Tim Chase wrote: > I'm a bit stuck trying to figure out why colors aren't working for me > on FreeBSD (where I understand that termcap is used rather than > terminfo). According to the configure script it appears all you need for color is start_color() from ncurses which should be there in the base system. Can you provide 'mutt -v' output? Does it have +HAVE_COLOR? Are you building mutt from source or using ports/pkg? If so can you provide the output off 'pkg info -f mutt' > So the terminal is doing color as expected, but somehow mutt/neomutt > doesn't seem to recognize that. Is there some trick that I've missed > for getting mutt/neomutt to play well with termcap/FreeBSD? I'm doing nothing special in ports/pkg or from source and colors just works with macOS Terminal/iTerm2, or cygwin xterm. Do you get color unknown command when you try to use 'color ...' in a .muttrc?
Re: while attaching files, TAB gives blank screen
On Sun, Apr 09, 2017 at 10:20:26AM EDT, Kevin J. McCarthy wrote: > On Sun, Apr 09, 2017 at 09:52:23AM +0200, Matthias Apitz wrote: > > I'm attaching the two different sets, maybe its worth to see what > > caused the problem. > > One thing I noticed is the NNTP option was set and is now unset. That's > an external patch, and a large one. If it were successfully applied to > 1.8.0, there may have been a strange interaction. > > In any case, I'm glad to hear you got it working! This turns out to be a combination of the nntp patch (properly maintained externally) and the mtime patch (less properly maintained by the mail/mutt port). It seems as if FreeBSD's patch fuzzer isn't inserting check_maildir_times() at the proper location. I would be the one to blame for this because I took the stance "if the patch applies (even with fuzzing) we're good." Clearly that was a bad idea. Applying just nntp or mtime everything is alright. However, when you both port options an alternative mtime is applied that takes into account nntp changes. A new mtime-nntp patch should be generated with updated context. Keep an eye out for this update in ports HEAD.
Re: mails to lists automatically?
On Mon, Feb 20, 2017 at 11:27:40AM EST, Francesco Ariis wrote: > On Mon, Feb 20, 2017 at 05:19:59PM +0100, Michelle Konzack wrote: > > On 2017-02-20 10:50:47 Jon LaBadie hacked into the keyboard: > > > Something similar may already be in there, the "L" command. > > > If set up, 'L' replies to the list, 'r' replies to the > > > message poster. > > > > ;-) I use mutt since 1999 and I am on more then 60 mailinglists, > > which mean, I know RTL. > > > > I do not want to use "l" if it is NOT neccesary. If I am in a > > Mailing-List folder, I want to use a Single-Key-Stroke reply and not > > break my fingers every time. > > Then folder-hook mlfolderbind something foo and > folder-hook nonmlfolder bind something bar > > I don't think the "If I press R, it should ask me if I want a > PM or RTL." is possible. Assuming the mailing list has the List-Post: header: message-hook ~h^List-Post: "bind pager r list-reply" message-hook ! ~h^List-Post: "bind pager r reply"
