Commit 64489b36 authored by Antonio Radici's avatar Antonio Radici

New upstream version 1.9.1

parent f3bea014
Language: Cpp
# BasedOnStyle
TabWidth: 8
UseTab: Never
IndentWidth: 2
ColumnLimit: 80
BreakBeforeBraces: Allman
IncludeCategories:
- Regex: '"config.h"'
Priority: -10
- Regex: '<stddef.h>'
Priority: -5
- Regex: '<.*>'
Priority: -4
- Regex: '".*_private.h"'
Priority: -3
- Regex: '"mutt.h"'
Priority: -2
# Main Header 0
- Regex: '".*"'
Priority: 5
AlignAfterOpenBracket: true
AlignEscapedNewlinesLeft: false
AlignOperands: true
AlwaysBreakAfterReturnType: None
BinPackArguments: true
BinPackParameters: true
BreakBeforeBinaryOperators: false
BreakBeforeTernaryOperators: false
Cpp11BracedListStyle: false
DerivePointerAlignment: false
IndentCaseLabels: true
IndentWrappedFunctionNames: false
KeepEmptyLinesAtTheStartOfBlocks: false
MaxEmptyLinesToKeep: 2
PointerAlignment: Right
ReflowComments: false
SortIncludes: true
SpaceAfterCStyleCast: true
SpaceBeforeAssignmentOperators: true
SpaceBeforeParens: ControlStatements
SpaceInEmptyParentheses: false
SpacesInCStyleCastParentheses: false
SpacesInParentheses: false
SpacesInSquareBrackets: false
# Allow some slightly over-long lines
PenaltyExcessCharacter: 1
# NEVER
AllowShortFunctionsOnASingleLine: false
AllowShortBlocksOnASingleLine: false
AllowShortCaseLabelsOnASingleLine: false
AllowShortIfStatementsOnASingleLine: false
AllowShortLoopsOnASingleLine: false
# OPTIONAL
AlignTrailingComments: true
# AlignConsecutiveAssignments: true
# AlignConsecutiveDeclarations: true
# AlwaysBreakBeforeMultilineStrings: true
# SpacesBeforeTrailingComments: 2
root = true
[*]
end_of_line = lf
insert_final_newline = true
charset = utf8
trim_trailing_whitespace = false
# those two settings may be overwritten below.
indent_size = 2
indent_style = space
[ChangeLog.neomutt]
indent_size = 1
[{[mM]akefile*,*.am}]
indent_size = 4
indent_style = tab
*.h linguist-language=C
* **bug reports**
* Expected behavior
* Actual behavior
* Steps to reproduce
* Used program versions
* Operating System and its version
* **feature requests**
* Why do you not like the current state?
* What would you like to see to change?
* **What does this PR do?**
* **Are there points in the code the reviewer needs to double check?**
* **Screenshots (if relevant)**
* **Does this PR meet the acceptance criteria?** (This is just a reminder for you,
this section can be removed if you fulfill it.)
- Documentation created/updated (you have to edit
[doc/manual.xml.head](https://www.github.com/neomutt/neomutt/blob/master/doc/manual.xml.head)
for that)
- All builds are passing
- Added [doxygen code documentation](https://www.neomutt.org/dev/doxygen)
[syntax](http://www.stack.nl/~dimitri/doxygen/manual/docblocks.html)
- Code follows the [style guide](https://www.neomutt.org/dev/coding-style)
* **What are the relevant issue numbers?**
# Wildcard ignores
*.o
*.a
*.in
# Ignore these files in all subdirectories
**/Makefile
# Ignore directories
**/.deps/
autom4te.cache/
# Wildcard ignored within subdirectories
po/*.gmo
doc/*.html
doc/*.1
doc/instdoc
doc/instdoc.sh
doc/Muttrc
doc/makedoc
doc/manual.txt
doc/manual.xml
doc/muttrc.man
doc/stamp-doc-chunked
doc/stamp-doc-rc
doc/stamp-doc-xml
po/POTFILES
po/mutt.pot
po/stamp-po
.version
aclocal.m4
compile
confdefs.h
config.guess
config.h
config.log
config.status
config.sub
configure
conftest
conftest.c
conftest.err
conststrings.c
depcomp
hcache/hcversion.h
install-sh
keymap_alldefs.h
keymap_defs.h
missing
mutt
mutt_dotlock
mutt_dotlock.c
mutt_md5
git_ver.h
patchlist.c
pgpewrap
pgpring
smime_keys
stamp-h1
txt2c
neomutt-*.tar.gz
neomutt-*/
# Stuff generated by autoreconf --install
ABOUT-NLS
config.rpath
m4/codeset.m4
m4/fcntl-o.m4
m4/gettext.m4
m4/glibc2.m4
m4/glibc21.m4
m4/iconv.m4
m4/intdiv0.m4
m4/intl.m4
m4/intldir.m4
m4/intlmacosx.m4
m4/intmax.m4
m4/inttypes-pri.m4
m4/inttypes_h.m4
m4/lcmessage.m4
m4/lib-ld.m4
m4/lib-link.m4
m4/lib-prefix.m4
m4/lock.m4
m4/longlong.m4
m4/nls.m4
m4/po.m4
m4/printf-posix.m4
m4/progtest.m4
m4/size_max.m4
m4/stdint_h.m4
m4/threadlib.m4
m4/uintmax_t.m4
m4/visibility.m4
m4/wchar_t.m4
m4/wint_t.m4
m4/xsize.m4
po/Makevars.template
po/Rules-quot
po/remove-potcdate.sed
po/boldquot.sed
po/en@boldquot.header
po/en@quot.header
po/insert-header.sin
po/quot.sed
po/remove-potcdate.sin
This diff is collapsed.
notifications:
email:
recipients:
- rich@flatcap.org
on_success: change
on_failure: always
sudo: false
dist: trusty
language: c
compiler: gcc
cache: ccache
addons:
apt:
packages:
- libgpgme11-dev
- libnotmuch-dev
- libtokyocabinet-dev
- libkyotocabinet-dev
- libgdbm-dev
- libdb-dev
- liblmdb-dev
- libqdbm-dev
- libslang2-dev
- libgnutls-dev
- libssl-dev
- libsasl2-dev
- libgss-dev
- xsltproc
- lynx
- docbook-simple
- docbook-xsl
- libxml2-utils
- gettext
- lua5.2
- liblua5.2-dev
- autopoint
git:
depth: 3
install:
- git clone --depth 1 https://github.com/neomutt/travis-build.git ~/config
before_script:
- ccache --zero-stats
script:
- ~/config/build
after_script:
- ccache --show-stats
This diff is collapsed.
MUTT HACKERS BEWARE
A word of warning about string comparisons: Since mutt may run in a
huge variety of locales, case-insensitive string comparisons and
case conversions may be dangerous. For instance, in iso-8859-9,
tolower('I') is DIFFERENT from 'i' - it's indeed the Turkish dotless
lowercase i.
For this reason, always use the ascii_* functions defined in ascii.h
and implemented in ascii.c when comparing or handling strings which
are defined as us-ascii. This concerns lots of text-based
protocols, message header tags, character set names, domain names,
e-mail addresses, etc.
Thu Apr 26 15:40:11 CEST 2001, <roessler@does-not-exist.org>
Hello and thank you for your interest in our project :)
Tips for a good bugreport
-------------------------------
* Help us help you! The more details you give, the better we\'ll be able to
help you out.
* Please use markdown syntax, especially for backtraces and config files!
* Please provide a minimal working example. That means, you should try to
replicate your issue with the minimal configuration from your muttrc and/or
any other relevant config files. These are the details you should be posting.
* Sometimes even small and inconspicuous details matter, so please be very
careful when writing down the steps to reproduce your problem.
* Please give us a list of program versions of **every** program relevant to
your report.
Tips for writing a good feature request
---------------------------------------
* Describe your problem and especially the context of it very detailed. It has
happened many times, that the problem could be solved without implementing
another feature.
* Please describe also your desired solution carefully. Nothing is more
frustrating - for both you and us, as developers - if we understand your
problem the wrong way and implement something which doesn't help you.
Tips for writing good pull requests
---------------------------------------
* The first line should be a short (50 characters or less) summary of your
commit message. If you can't find a short enough one-line summary, split the
commit into multiple ones.
* Keep one line between the one-line summary and the body.
* Use bullet points in the body of the commit message to separate multiple
things you did.
* your commits should be clear and concise. That means also you shouldn't sum up
two features or two bug fixes into one commit. If you do, it makes both bug
fixes or features harder to understand. Also, don't hesitate to
[rewrite](https://git-scm.com/book/en/v2/Git-Tools-Rewriting-History) the
Github history of your development branch.
* Wrap the body of the commit message at around 80 characters.
* if your commit addresses a particular PR, commit or Issue, please say so in
your commit. The Github documentation
([1](https://help.github.com/articles/autolinked-references-and-urls/)
and [2](https://help.github.com/articles/closing-issues-via-commit-messages/))
can help you with that.
* Please eliminate any warnings gcc or any other tool produces during the
compilation stage.
* If your commit addresses only a specific method or a specific file, please say
so in your commit.
Thank you for your help!
The Neomutt Team.
This source diff could not be displayed because it is too large. You can view the blob instead.
This diff is collapsed.
This diff is collapsed.
This diff is collapsed.
Notes
=====
Supported platforms
===================
Mutt has been reported to compile and run under the following Unix operating
systems:
AIX
BSDI
Convex
Data General Unix (DG/UX)
Digital Unix (OSF/1)
DYNIX/ptx
FreeBSD
HP-UX
IRIX
Linux
Mac OS X
Atari MiNT
MkLinux
NetBSD
OpenBSD
QNX
SCO Unix 3.2v4/5
Solaris
SunOS
Ultrix
UnixWare
- If you are building from Mercurial, or if you are changing parts of mutt,
particularly the build system, do read doc/devel-notes.txt.
- A C99 compiler (such as GCC) is required.
......@@ -17,6 +45,8 @@ Notes
- For building the manual, mutt needs the DocBook XSL stylesheets
as well as the DocBook DTD as of version 4.2 installed locally.
For details, please see the section "Generating Mutt Documentation
From Source" in doc/devel-notes.txt.
Installation
......@@ -88,7 +118,7 @@ to ``configure'' to help it out, or change the default behavior:
--disable-nls
This switch disables mutt's native language support.
--with-included-gettext
--with-included-gettext
Mutt will be built using the GNU gettext library included in
the intl/ sub-directory. You may need to use this switch if
your machine has something which looks like gettext to the
......@@ -101,13 +131,13 @@ to ``configure'' to help it out, or change the default behavior:
routines, so this provides a way to support them.
--enable-flock
use flock() to lock files.
use flock() to lock files.
--disable-fcntl
by default, Mutt uses fcntl() to lock files. Over NFS this can
result in poor performance on read/write. Note that using this
option could be dangerous if dotlocking is also disabled.
--enable-nfs-fix
some implementations of NFS do not always write the
atime/mtime of small files. This means that Mutt's ``mailboxes''
......@@ -264,3 +294,8 @@ Sparc Linux
include files when building mutt. Configuring mutt with the
--disable-warnings switch is said to help against this problem.
Digital Unix (OSF/1)
The system curses library is said to be badly broken. Use GNU
ncurses or SLang instead.
This diff is collapsed.
This diff is collapsed.
Visible changes since Mutt 1.2
==============================
Folder formats and folder access
--------------------------------
- Better mh support: Mutt now supports .mh_sequences files.
Currently, the "unseen", "flagged", and "replied" sequences are
used to store mutt flags (the names are configurable using the
$mh_seq_unseen, $mh_seq_flagged, and $mh_seq_replied configuration
variables). As a side effect, messages in MH folders are no longer
rewritten upon status changes.
- The "trashed" flag is supported for maildir folders. See
$maildir_trash.
- POP folder support. You can now access a POP mailbox just like an
IMAP folder (with obvious restrictions due to the protocol).
- URL syntax for remote folders. You can pass things like
pop://account@host and imap://account@host/folder as arguments for
the -f command line flag.
- STARTTLS support. If $ssl_starttls is set (the default), mutt
will attempt to use STARTTLS on servers advertising that
capability.
- $preconnect. If set, a shell command to be executed if mutt fails
to establish a connection to the server. This is useful for
setting up secure connections; see the muttrc(5) for details.
- $tunnel. Use a pipe to a command instead of a raw socket. See
muttrc(5) for details. (Basically, it's another way for setting
up secure connections.)
- More new IMAP/POP-related variables (see muttrc(5) for details):
$connect_timeout, $imap_authenticators, $imap_delim_chars,
$imap_peek, $pop_authenticators, $pop_auth_try_all,
$pop_checkinterval, $pop_delete, $pop_reconnect, $use_ipv6.
- The following IMAP/POP-related variables are gone:
$imap_checkinterval, $imap_cramkey, $pop_port.
- There's a new imap-fetch-mail function, which forces a check for
new messages on an IMAP server.
- The new-mailbox function was renamed to create-mailbox, and is
bound to C instead of n by default.
Character set support
---------------------
- Mutt now uses the iconv interface for character set conversions.
This means that you need either a very modern libc, or Bruno
Haible's libiconv, which is available from
<http://www.gnu.org/software/libiconv/>.
- With sufficiently recent versions of ncurses and slang, mutt works
properly in utf-8 locales.
- On sufficiently modern systems, the $charset variable's value is
automatically derived from the locale you use. (Note, however,
that manually setting it to a value which is compatible with your
locale doesn't do any harm.)
- $send_charset is a colon-separated list of character sets now,
defaulting to us-ascii:iso-8859-1:utf-8.
- charset-hook defines aliases for character sets encountered in
messages (say, someone tags his messages with latin15 when he
means iso-8859-15), iconv-hook defines local names for character
sets (for systems which don't know about MIME names; see
contrib/iconv for sample configuration snippets).
- The change-charset function is gone. Use edit-type (C-e on the
compose menu) instead.
- The recode-attachment function is gone.
Other changes
-------------
- There's a new variable $compose_format for the compose screen's
status line. You can now include the message's approximate
on-the-wire size.
- The attachment menu knows about collapsing now: Using
collapse-parts (bound to "v" by default), you can collapse and
uncollapse parts of the attachment tree. This function is also
available from the pager when invoked from the attachment tree.
Normally, the recvattach menu will start uncollapsed. However,
with the new $digest_collapse option (which is set by default),
the individual messages contained in digests will be displayed
collapsed. (That is, there's one line per message.)