| Age | Commit message (Collapse) | Author |
|---|
|
These are mostly automated changes corresponding to the emacs
settings:
(c-set-style "linux")
(setq c-basic-offset 2)
(c-set-offset 'case-label '+)
Most of the code follows the convention:
(add-to-list 'c-cleanup-list 'space-before-funcall)
but this is not enforced by this indentation cleanup.
Also, I personally dislike tabs, so I have:
(setq-default indent-tabs-mode nil)
in my own configuration. However I have no desire to change every line
just for that effect. So this cleanup does nothing about the mix issue.
Some of the secondary files (e.g. regex.c) have been skipped.
I've also skipped crypt-gpgme.c, because I need to think about that
file. Werner Koch and the GnuPG team contributed most it, and it
follows the Gnu indentation settings. It should probably be made
uniform with Mutt, but I don't want to discourage future GnuPG
contribution to the file.
I manually reverted a few unsightly cleanups, and added a few tweeks
when I saw things that could be improved.
|
|
The result of
find . -name "*.[ch]" -exec emacs -batch {} \
--eval="(progn (delete-trailing-whitespace) (and (buffer-modified-p) (save-buffer)))" \;
|
|
It will fail, rather than return NULL.
Further clean up imap_new_data() since it also had NULL checks for
safe_calloc() that shouldn't happen.
|
|
|
|
|
|
Thanks to Vincent Lefèvre for working on these utf-8 screen display issues.
|
|
Add U+00AD SOFT HYPHEN to the filtered characters in headers and the
pager. In some terminals and situations it causes major display problems.
|
|
Curses and slang don't support them, so there's little point in
showing them or attempting to somehow deal with them.
This patch adds filtering in the pager, and changes the filtering
added in 6e0aca94cdb0 for the index to completely skip the marker.
|
|
Filter out U+200F RIGHT-TO-LEFT MARK and U+200E LEFT-TO-RIGHT MARK in
rfc2047 and 2231 encoded fields. GNU Screen has a bug that corrupts
the display, and can cause the wrong email to appear to be selected in
the index. Until screen fixes the issue, filter it out in mutt.
|
|
Currently, no callers were providing a non-NULL buffer to
mutt_buffer_init, and splitting it will allow more sane semantics for
buffer allocation, initialization, and destruction in a later patch.
|
|
With utf-8//TRANSLIT, we internally didn't recognize it as utf-8. This
leads to badly broken behaviour if --without-wc-funcs is used for some
reason. In that case, if we have utf-8 as charset, we implement our own
wide char functions; for all other charsets, we use the system
single-byte locale functions. And using these with utf-8 is broken.
|
|
|
|
|
|
|
|
In mbyte.h and without using wc functions, only the prototypes were
defined but implementations were missing resulting in build
errors. These new functions are derived from the iswalnum() and
towupper() routines which don't provide full unicode coverage.
|
|
|
|
as pointed out by exg on #mutt.
|
|
|
|
Wipe unwanted code depending on M_ICONV_HOOK_TO in charset.c:mutt_iconv_open().
Totally wipe M_ICONV_HOOK_TO symbol.
Remove misusages of M_ICONV_HOOK_FROM flag in:
- crypt-gpgme.c:print_utf8().
- mutt_idna.c:mutt_idna_to_local() and mutt_local_to_idna().
- pgp.c:pgp_traditional_encryptsign().
Document usage policy of M_ICONV_HOOK_FROM flag.
Cosmetic downcasing of some constant charset names (utf-8, euc-jp) for consistency.
Correction of a typo in the "iso8859-5" charset name.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Remove it from mutt.h
|
|
|
|
|
|
Takashi <taki@luna.email.ne.jp>.
|
|
|
|
<taki@luna.email.ne.jp>.
|
|
|
|
|
|
|
|
|
|
When the Charset is euc-jp or shift_jis, iconv is used for mbrtowc
and wcrtomb. The worst part is mbrtowc_iconv(), where I attempted to
make mbrtowc both restartable (it can process part of multibyte
character) and fast in the case where there is nothing left over
from a previous character. Also I try to make no assumptions about
how those character sets work, which is easy, because I know very
little about them ...
People who don't use one of those two stateless Japanese display
charsets shouldn't be affected. People whose systems provide the
wchar_t functions should be even less affected, because they don't
even get this code in their binary.
|
|
|
|
Takashi <taki@luna.email.ne.jp>, with small changes from Edmund
Grimley Evans.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
