On Saturday, January 11, 2025 at 05:04:17 a.m. EST, Stuart Henderson
wrote:
On 2025/01/11 09:50, Stuart Cassoff wrote:> Excellent, thanks!
>
> Now 1 failure on amd64 and 4 on i386. Pretty good.
actually I missed another part,
pre-test:
cd ${WRKSRC}/neomutt-test-files; .
On 2025/01/11 09:50, Stuart Cassoff wrote:
> Excellent, thanks!
>
> Now 1 failure on amd64 and 4 on i386. Pretty good.
actually I missed another part,
pre-test:
cd ${WRKSRC}/neomutt-test-files; ./setup.sh
> Ok to update?
yes.
elds 4 fewer test failures.
It is supposed to point at a dir with a checkout of
https://github.com/neomutt/neomutt-test-files (which already has
the "tmp" dir created).
This would be ok:
Index: Makefile
===
RCS file: /cvs/po
On 2025/01/10 15:54, Stuart Cassoff wrote:
> Adding the env var makes the tests work.
> Making the tmp dir yields 4 fewer test failures.
It is supposed to point at a dir with a checkout of
https://github.com/neomutt/neomutt-test-files (which already has
the "tmp" dir created).
Adding the env var makes the tests work.
Making the tmp dir yields 4 fewer test failures.
Stu
Index: Makefile
===
RCS file: /cvs/ports/mail/neomutt/Makefile,v
diff -u -p -u -p -r1.99 Makefile
--- Makefile 9 Jan 2025 12:30:43
thanks, committed.
On 2024/09/03 04:57, James Cook wrote:
> On Tue, Jul 16, 2024 at 04:11:42PM +, James Cook wrote:
> > Hi,
> >
> > neomutt can't properly parse non-ASCII URLs on OpenBSD without
> > pcre2. It doesn't affect me personally but I imagine
On Tue, Jul 16, 2024 at 04:11:42PM +, James Cook wrote:
Hi,
neomutt can't properly parse non-ASCII URLs on OpenBSD without
pcre2. It doesn't affect me personally but I imagine someone out
there will be unhappy that neomutt can't open their IMAP folder.
See:
htt
Hi,
neomutt can't properly parse non-ASCII URLs on OpenBSD without
pcre2. It doesn't affect me personally but I imagine someone out
there will be unhappy that neomutt can't open their IMAP folder.
See:
https://github.com/neomutt/neomutt/issues/4352
You can see it in neom
some other person who
happens to be mentioned in a commit message > 5 years ago should be
responsible.
The sasl patches you suggest to remove are leftovers of the pledge
patches for mutt which were dropped for neomutt at some point. I can't
tell whether that removal was deliberate or an
who
> happens to be mentioned in a commit message > 5 years ago should be
> responsible.
>
> The sasl patches you suggest to remove are leftovers of the pledge
> patches for mutt which were dropped for neomutt at some point. I can't
> tell whether that removal was deliberate
e sasl patches you suggest to remove are leftovers of the pledge
patches for mutt which were dropped for neomutt at some point. I can't
tell whether that removal was deliberate or an accident - the Makefile
still says # uses pledge().
The auto_def patch doesn't look like a patch that
rote:
I am CC'ing tb as they touched this patch last.
I never touched neomutt.
> I am CC'ing tb as they touched this patch last.
I never touched neomutt.
I built upstream neomutt with gpgme sasl notmuch options and ports
neomutt FLAVOR (gpgme sasl notmuch) without any patches. Both linked
and launched without any issues. I did a cursory run through of
neomutt/Notmuch and neomutt/IMAP and they looked fine.
The one patch looks like it is
I upgraded openBSD and updated packages about 6 hours ago and this was
the first issue on this release.
Version and dmesg follow, debug.
I had quit viewing a message, deleted it, and was changing folders.
desktop(~)$: egdb neomutt neomutt.core
GNU gdb (GDB) 9.2
Copyright (C) 2020 Free
OpenBSD 7.0 release
debug-neomutt-20210205-notmuch (installed)
neomutt-20210205-notmuch (installed)
I guess I shouldn't have commented about not having any dumps.
desktop(~)$: egdb neomutt neomutt_20211020.core
GNU gdb (GDB) 7.12.1
Copyright (C) 2017 Free Software Foundation, Inc.
Li
On Mon 18/10/2021 23:48, Theo Buehler wrote:
> +Cc maintainer
>
> On Mon, Oct 18, 2021 at 09:07:07PM +, James Cook wrote:
> > I don't know if this is related to the other recent neomutt segfault
> > thread.
>
> Unlikely.
>
> > falsifian moth
> > falsifian moth ~ $ pkg_info neomutt
> > Information for inst:neomutt-20211015
>
> So it seems you're running -current, right?
Yes.
> > falsifian moth ~ $ dmesg|head -n1
> > OpenBSD 7.0 (GENERIC.MP) #232: Thu Sep 30 14:25:29 MDT 2021
> >
&g
+Cc maintainer
On Mon, Oct 18, 2021 at 09:07:07PM +, James Cook wrote:
> I don't know if this is related to the other recent neomutt segfault
> thread.
Unlikely.
> falsifian moth ~ $ pkg_info neomutt
> Information for inst:neomutt-20211015
So it seems you're r
Under 6.9 I had submitted several seq fault traces and had even more
not submitted. I was experiencing a fault once a day at least.
Stuart provided a patch under 6.9 that greatly reduced the dumps. I
had I think two with the patch.
With the new version of neomutt (20210205) using 7.0 release
I don't know if this is related to the other recent neomutt segfault
thread.
After sysupgrade -s and pkg_add -u, neomutt crashes immediately when I
start it. Is anyone else seeing this? Details below. I took filesystem
backups before upgrading, so I can probably figure out the exact
(wo
On Thu, Oct 07, 2021 at 01:31:29PM +0100, Stuart Henderson wrote:
On 2021/10/06 21:14, Jon Fineman wrote:
Not sure I built this correctly. I applied the patch, ran make in
./mail/neomutt under my userid, then with doas after pkg_add issued errors.
I did not run make install.
Is it valid to
On 2021/10/06 21:14, Jon Fineman wrote:
> Not sure I built this correctly. I applied the patch, ran make in
> ./mail/neomutt under my userid, then with doas after pkg_add issued errors.
> I did not run make install.
>
> Is it valid to run neomutt out of the pobj directory? While
On Wed, Oct 06, 2021 at 09:14:47PM -0400, Jon Fineman wrote:
Not sure I built this correctly. I applied the patch, ran make in
./mail/neomutt under my userid, then with doas after pkg_add issued
errors. I did not run make install.
Is it valid to run neomutt out of the pobj directory? While
Not sure I built this correctly. I applied the patch, ran make in
./mail/neomutt under my userid, then with doas after pkg_add issued
errors. I did not run make install.
Is it valid to run neomutt out of the pobj directory? While it
launched and I was able to interact with it I did get the
tes.
>
> It probably needs reporting upstream, but there's a new release of
> neomutt due this week so it would be better to test with that first, in
> case the poblems you're running into have been fixed already.
>
Not the released vers
new release of
neomutt due this week so it would be better to test with that first, in
case the poblems you're running into have been fixed already.
I had been using it about 5 minutes and just entered a few commands.
Hopefully one of these will help. dmesg follows. It is rather random
with staying up days to just a few minutes.
desktop(~)$: egdb neomutt neomutt.core
GNU gdb (GDB) 7.12.1
Copyright (C) 2017 Free Software Foundation, Inc
I had only been using neomutt about 10 minutes.
desktop(~)$: uname -a
OpenBSD desktop 6.9 GENERIC.MP#4 amd64
desktop(~)$:
desktop(~)$: egdb neomutt neomutt.core
GNU gdb (GDB) 7.12.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.
egdb neomutt neomutt_20210710.core
GNU gdb (GDB) 7.12.1
Copyright (C) 2017 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the
On 2021/07/10 06:44, Jon Fineman wrote:
> It had been running for several days. Ran the '$' command to purge messages
> marked for deletion. I have the debug package installed, not sure why I am
> not getting more info from egdb.
>
>
> desktop(~)$: egdb de
It had been running for several days. Ran the '$' command to purge messages
marked for deletion. I have the debug package installed, not sure why I am not
getting more info from egdb.
desktop(~)$: egdb debug-neomutt-20210205-notmuch neomutt.core
GNU gdb (GDB) 7.12.1
Copyright (C)
Hi,
Since kc can now be built on macppc (diff sent previously), here is a
diff that enables kc support for macppc in neomutt.
I've built neomutt and its 3 flavours without issues. I've also tested
by creating a basic neomuttrc with:
[...]
set header_cache=/tmp/neocache
set header_cac
gt;>>>> On 9/5/20 5:40 PM, Pamela Mosiejczuk wrote:
>>>>>>
>>>>>> On 2020-08-13 14:48, Aisha Tammy wrote:
>>>>>>>>>>> On 6/1/20 12:46 AM, Aisha Tammy wrote:
>>>>>>>>>>>> Hi,
>&
; >>>>
> >>>> On 2020-08-13 14:48, Aisha Tammy wrote:
> >>>>>>>>> On 6/1/20 12:46 AM, Aisha Tammy wrote:
> >>>>>>>>>> Hi,
> >>>>>>>>>> This is quite a handy package for autoconf
te:
> >>>>>>>> Hi,
> >>>>>>>> This is quite a handy package for autoconfiguration of neomutt
> >>>>>>>> and other utilities. I'm hoping we can get it so that a lot of the
> >>>>>>>> ne
On 9/5/20 6:08 PM, Aisha Tammy wrote:
> On 9/5/20 5:40 PM, Pamela Mosiejczuk wrote:
>>
>> On 2020-08-13 14:48, Aisha Tammy wrote:
>>>>>>> On 6/1/20 12:46 AM, Aisha Tammy wrote:
>>>>>>>> Hi,
>>>>>>>> This is quit
On 9/5/20 5:40 PM, Pamela Mosiejczuk wrote:
>
> On 2020-08-13 14:48, Aisha Tammy wrote:
>>>>>> On 6/1/20 12:46 AM, Aisha Tammy wrote:
>>>>>>> Hi,
>>>>>>> This is quite a handy package for autoconfiguration of neomutt
>>
On 2020-08-13 14:48, Aisha Tammy wrote:
On 6/1/20 12:46 AM, Aisha Tammy wrote:
Hi,
This is quite a handy package for autoconfiguration of neomutt
and other utilities. I'm hoping we can get it so that a lot of the
newcomers who want to use neomutt won't be that daunted by the dotfi
====
> > RCS file: /cvs/ports/mail/neomutt/Makefile,v
> > retrieving revision 1.56
> > diff -u -p -u -p -r1.56 Makefile
> > --- Makefile13 Aug 2020 18:22:58 - 1.56
> > +++ Makefile24 Aug 2020 11:00:09 -
> > @@
> >
> > Index: Makefile
> > ===
> > RCS file: /cvs/ports/mail/neomutt/Makefile,v
> > retrieving revision 1.56
> > diff -u -p -u -p -r1.56 Makefile
> > --- Makefile13 Aug 2020 18:22:58
On 2020/08/27 12:11, Rafael Sadowski wrote:
> Runs very stable for me and speeds up my work immensely.
>
> Opinions? OKs?
> Index: Makefile
> ===
> RCS file: /cvs/ports/mail/neomutt/Makefile,v
> retrieving revis
Ok
On 27/08 12:11 , Rafael Sadowski wrote:
> Runs very stable for me and speeds up my work immensely.
>
> Opinions? OKs?
>
> Index: Makefile
> ===
> RCS file: /cvs/ports/mail/neomutt/Makefile,v
> retriev
Runs very stable for me and speeds up my work immensely.
Opinions? OKs?
Index: Makefile
===
RCS file: /cvs/ports/mail/neomutt/Makefile,v
retrieving revision 1.56
diff -u -p -u -p -r1.56 Makefile
--- Makefile13 Aug 2020 18:22:58
Hi.
I built it, no problems.
If I understand correctly, gpg2 needs to be used instead of what the
manual says. However I got the following error:
Change (N)ame, (C)omment, (E)mail or (O)kay/(Q)uit? o
We need to generate a lot of random bytes. It is a good idea to perform
some other action (type
t;
>>> Aisha
>>>
>>> On 6/8/20 1:36 PM, Aisha Tammy wrote:
>>>> Bumping.
>>>> Also it makes it easy to connect to proton using the bridge so thats
>>>> a positive as well.
>>>>
>>>> Aisha
>>>>
>>>> O
Please either send directly to the maintainer, or at least CC the maintainer,
on ports changes.
On 2020/08/09 12:03, Olivier Taïbi wrote:
> diff -uNpr /usr/ports/mail/neomutt/Makefile
> /build/usr/ports/mail/neomutt/Makefile
Not sure what went wrong, but the emailed diff doesn't
Seems plausible/fine to me, but please document the flavor in DESCR as
well (warranting a REVISION bump).
The flavor must also be hooked up in mail/Makefile.
On Sun, Aug 09, 2020 at 12:03:17PM +0200, Olivier Taïbi wrote:
> +$OpenBSD$
Please comment patches.
> +Index: notmuch/private.h
> +--- no
diff -uNpr /usr/ports/mail/neomutt/Makefile
/build/usr/ports/mail/neomutt/Makefile
--- /usr/ports/mail/neomutt/MakefileTue Jul 28 23:54:23 2020
+++ /build/usr/ports/mail/neomutt/Makefile Fri Aug 7 23:46:50 2020
@@ -26,7 +26,7 @@ BUILD_DEPENDS+= textproc/docbook-xsl
Bumping.
>>> Also it makes it easy to connect to proton using the bridge so thats
>>> a positive as well.
>>>
>>> Aisha
>>>
>>> On 6/1/20 12:46 AM, Aisha Tammy wrote:
>>>> Hi,
>>>> This is quite a handy package for autoconfig
tive as well.
>>
>> Aisha
>>
>> On 6/1/20 12:46 AM, Aisha Tammy wrote:
>>> Hi,
>>> This is quite a handy package for autoconfiguration of neomutt
>>> and other utilities. I'm hoping we can get it so that a lot of the
>>> newcomers
> This is quite a handy package for autoconfiguration of neomutt
>> and other utilities. I'm hoping we can get it so that a lot of the
>> newcomers who want to use neomutt won't be that daunted by the dotfiles.
>>
>> I've attached the port but upstream doesn'
Bumping.
Also it makes it easy to connect to proton using the bridge so thats
a positive as well.
Aisha
On 6/1/20 12:46 AM, Aisha Tammy wrote:
> Hi,
> This is quite a handy package for autoconfiguration of neomutt
> and other utilities. I'm hoping we can get it so that a lot of t
Hi,
This is quite a handy package for autoconfiguration of neomutt
and other utilities. I'm hoping we can get it so that a lot of the
newcomers who want to use neomutt won't be that daunted by the dotfiles.
I've attached the port but upstream doesn't make any tagged releas
allation was successfully and there
> were no changes (aside from COPYRIGHT.md file) in the
> PLIST.
>
> 'env FLAVOR=sasl make package'
> (env FLAVOR=sasl was used for all intermediate commands)
> gives following error
>
> '/usr/portsdir/pobj/n
On Thu, Mar 19 '20 at 08.14 NZDT, myportslist20190...@nym.hush.com wrote:
> Synopsis: neomutt-20200313-gpgme-sasl error sending command line email
Looks like it's a known bug, see
https://github.com/neomutt/neomutt/issues/2176 (caused by commit 331702b
with comment "abor
Synopsis: neomutt-20200313-gpgme-sasl error sending command line email
Environment:
System : OpenBSD 6.6
Details : OpenBSD 6.6-current (GENERIC.MP) #56: Sun Mar 15 12:44:04
MDT 2020
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile
After the latest snapshot and neomutt, I am still getting
all of the headers with date and time correct.
Until the final Date: which is wrong.
This started one or two of the snapshots I used before and
was including the neomutt version right before this one.
Using just mail locally works correctly
Cherry-picked upstream commit from five days ago; this lets me read
mails again.
OK?
Index: Makefile
===
RCS file: /cvs/ports/mail/neomutt/Makefile,v
retrieving revision 1.40
diff -u -p -r1.40 Makefile
--- Makefile7 Nov 2019
On Sat, Nov 02, 2019 at 06:33:15PM +, Stuart Henderson wrote:
> https://github.com/neomutt/neomutt/issues/1882
Thanks, I'll just wait for today's release to come around then.
https://github.com/neomutt/neomutt/issues/1882
--
Sent from a phone, apologies for poor formatting.
On 2 November 2019 15:38:14 Klemens Nanni wrote:
Latest neomutt dumps core when assigning aliases to groups; this is
independent of the user configuration:
$ sysctl -n kern.version
OpenBSD
Latest neomutt dumps core when assigning aliases to groups; this is
independent of the user configuration:
$ sysctl -n kern.version
OpenBSD 6.6-current (GENERIC.MP) #424: Fri Nov 1 14:12:12 MDT 2019
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
$ cd /usr/ports/mail
On 2019/04/17 22:17, Solene Rapenne wrote:
> I'm not sure it's a neomutt bug or openbsd specific.
> It can be reproduced reliably.
>
> I have an imap server with a SSL certificate.
> If I make a ssh tunnel to forward it locally and that I connect to it through
> l
I'm not sure it's a neomutt bug or openbsd specific.
It can be reproduced reliably.
I have an imap server with a SSL certificate.
If I make a ssh tunnel to forward it locally and that I connect to it through
localhost, SSL certificate is wrong (due to different hostname).
neomut
On 2017/07/19 15:28, Klemens Nanni wrote:
> On Wed, Jul 19, 2017 at 02:15:03PM +0100, Stuart Henderson wrote:
> > On 2017/07/19 15:06, Klemens Nanni wrote:
> > > I was missing the slang flavor when trying neomutt over mutt so here it
> > > is.
> > >
> >
On Wed, Jul 19, 2017 at 02:15:03PM +0100, Stuart Henderson wrote:
> On 2017/07/19 15:06, Klemens Nanni wrote:
> > I was missing the slang flavor when trying neomutt over mutt so here it
> > is.
> >
> > --with-curses can be safely dropped as it's the default.
>
On 2017/07/19 15:06, Klemens Nanni wrote:
> I was missing the slang flavor when trying neomutt over mutt so here it
> is.
>
> --with-curses can be safely dropped as it's the default.
>
> Feedback? Comments?
I think neomutt already has enough build flavours..
I was missing the slang flavor when trying neomutt over mutt so here it
is.
--with-curses can be safely dropped as it's the default.
Feedback? Comments?
Index: Makefile
===
RCS file: /cvs/ports/mail/neomutt/Makefile,v
retri
On 2016 Oct 18 (Tue) at 11:16:35 +0100 (+0100), Stuart Henderson wrote:
:(My original plan was to replace mutt completely
MASSIVE NAK on that, please.
s for that?
>
> (My original plan was to replace mutt completely, but at this point I think
> it's better to have a clean mutt-1.7.1 without the big array of patch options
> to allow it to be updated sanely, and a separate clean neomutt).
OK to import this version. I agree with this ap
On 2016/10/17 13:11, Stefan Sperling wrote:
> On Sun, Oct 16, 2016 at 11:23:28PM +0200, Stefan Sperling wrote:
> > On Mon, Sep 26, 2016 at 01:07:30PM +0100, Stuart Henderson wrote:
> > > People who were seeing crashes with neomutt, please test this, and get
> > > me
On Sun, Oct 16, 2016 at 11:23:28PM +0200, Stefan Sperling wrote:
> On Mon, Sep 26, 2016 at 01:07:30PM +0100, Stuart Henderson wrote:
> > People who were seeing crashes with neomutt, please test this, and get
> > me backtraces if you still see them (the port Makefile here is setup to
On Mon, Sep 26, 2016 at 01:07:30PM +0100, Stuart Henderson wrote:
> People who were seeing crashes with neomutt, please test this, and get
> me backtraces if you still see them (the port Makefile here is setup to
> build with symbols so you don't need to set DEBUG in this case).
People who were seeing crashes with neomutt, please test this, and get
me backtraces if you still see them (the port Makefile here is setup to
build with symbols so you don't need to set DEBUG in this case).
neomutt.tgz
Description: application/tar-gz
74 matches
Mail list logo
