I've been using this in my personal build for a long time, according to
the author date on the commit it's been at least since 2012. I've
submitted it once before as part of a series to support getting the
version information from git back when the official version control was
still in mercuria
Let compilers know that `mutt_buffer_printf()` and
`mutt_buffer_add_printf()` expect the second argument to be a
`printf`-style format string with the arguments for the format starting
at the third argument. This allows warnings to be shown if these are
incorrect.
---
buffer.h | 2 ++
1 file chang
In case it helps inform a decision, here's the OAuth2 status of several
IMAP providers:
OAUTHBEARER: Google, Yahoo, ATT, Comcast, Sky
XOAUTH2 only: Microsoft, AOL, Yandex
Neither: Apple, Cox, Zoho, Mail.com, GMX, FastMail, 1&1
For each service, I searched for the IMAP server name, then d
Thanks, Vincent.
Nevertheless, in my 1.11.3 source directory I had the two files,
1) dotlock.c
2) mutt_dotlock.c
Then I did a
mv '1.11.3 source directory'/mutt_dotlock.c mutt/mutt_dotlock.c
and a
git status
git add
and now it's part of my latest mutt source installation (git-cloned)
So, what I do
Hi,
On 2019-04-10 10:47:57 +0200, felixs wrote:
> is the file mutt_dotlock.c part of mutt's source code?
Yes and no. :) It is just a copy of dotlock.c, which is part of mutt's
source code.
The copy is done by
mutt_dotlock.c: dotlock.c
cp $(srcdir)/dotlock.c mutt_dotlock.c
in the Makefi
Hi mutt developers,
is the file mutt_dotlock.c part of mutt's source code?
What strikes me is the fact that this file is present in my
already existing mutt-1.11.3 directory (installed from a tarball and
built from source), but, as to my checks, it was NOT part of the mutt
source code repo I clon