rich at flatcap.org
Tue Sep 20 14:03:07 CEST 2016
> I finally took the time to add the feature.
Please can everyone give this feature a test, then let the list know how
it went. Even if it's just: "It works for me".
> I haven't written the documentation yet. Should I add it as a completely
> new patch?
Yes, please. The template docs are in the management repo:
Note, they'll probably get moved into the wiki, soon.
> 1. How can I compile neomutt with debug symbols? I tried setting CFLAGS,
> but that didn't do anything...
As Elimar said:
though, this *ought* to be the same:
I don't think DEBUG actually enables much, except the `dprint` function.
> 2. How can I send debug messages and errors? I didn't really look
> around, but it could have helped me understanding what was going on.
The `dprint` has the strangest prototype I've ever seen:
dprint (DEBUG_LEVEL, (DEBUG_FILE, PRINTF_STRING, ARGS...));
dprint (2, (debugfile, "error in the %s", name));
This will be save to the debug file (~/.muttdebug0 by default) if you
mutt -d LEVEL
Where LEVEL is 2 or above. Each time you run `mutt -d` the debug files
.muttdebug0 -> .muttdebug0
.muttdebug1 -> .muttdebug1
.muttdebug2 -> .muttdebug2
.muttdebug3 -> .muttdebug3
As for warning the user, there's: mutt_message() and mutt_error().
mutt_message (_("Authenticating (%s)..."), method);
mutt_error (_("%s authentication failed."), method);
Note the use of the _() function to provide message translations.
After printing an error, it's usual to call mutt_sleep(NUM_SECS) to make
sure that the user notices. If the time is set to 0, then the wait is
determined by the $sleep_time config variable.
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: not available
More information about the neomutt-devel