Looking for something easier? (try these)
When NeoMutt asks a question, the menu options are usually given with parenthesised letters or "number-colon", e.g.
- (R)eject, accept (O)nce, (A)ccept always, (S)kip
#!/bin/bash | |
# -c = --check | |
# = --check-format --check-header --check-domain | |
[ $# = 0 ] && ARGS="*.po" || ARGS="$@" | |
for i in $ARGS; do | |
echo -ne "${i%.po}:\t" | |
msgfmt --statistics -c -o /dev/null $i 2>&1 |
I suggest we try, as much as possible to focus our work on browser.c/h and not altering the code of any other file. This way, we can work in a specific branch and have a specific architecture in the file that will merge more efficiently. Then, when we merge, we can split the content of the file into many smaller files if that is relevant, of course.
Yes, or a separate file completely. New file, new history.
# base64 | |
s/\<mutt_from_base64\>/mutt_b64_decode/g | |
s/\<mutt_to_base64\>/mutt_b64_encode/g | |
# buffer | |
s/\<mutt_buffer_addch\>/mutt_buffer_addch/g | |
s/\<mutt_buffer_addstr\>/mutt_buffer_addstr/g | |
s/\<mutt_buffer_free\>/mutt_buffer_free/g | |
s/\<mutt_buffer_from\>/mutt_buffer_from/g | |
s/\<mutt_buffer_init\>/mutt_buffer_init/g |
all: main | |
main: main.o libfruit.a | |
$(CC) -o main main.o -L. -lfruit | |
libfruit.a: apple.o banana.o global.o | |
ar cr libfruit.a apple.o banana.o global.o | |
clean: | |
rm -f *.o *.a main |
// gcc -Wall -o test-dns test-dns.c | |
#include <netdb.h> | |
#include <stdio.h> | |
#include <stdlib.h> | |
#include <string.h> | |
#include <sys/socket.h> | |
#include <sys/types.h> | |
#include <sys/utsname.h> | |
#include <unistd.h> |
s/--disable-doc\>/--disable-doc/g | |
s/--disable-fcntl\>/--disable-fcntl/g | |
s/--disable-full-doc\>/--full-doc/g | |
s/--disable-iconv\>/GONE/g | |
s/--disable-nls\>/--disable-nls/g | |
s/--disable-pgp\>/--disable-pgp/g | |
s/--disable-po\>/GONE/g | |
s/--disable-smime\>/--disable-smime/g | |
s/--enable-debug\>/GONE/g | |
s/--enable-dotlock\>/GONE/g |
Build and Install Changes to NeoMutt
There are a lot of changes coming to NeoMutt's build and install. I suggest using this issue as a discussion board and creating pull-requests as needed. Whether you make changes as they happen in NeoMutt, or wait for us to finish, is up to you.
version number doesn't contain mutt's version no mutt strings, only neomutt
db_create | |
db_env_create |