summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAge
* configure: Implement a --help option to document --prefix.Carl Worth2009-12-04
| | | | | Also document that values for CC, CFLAGS, etc. can be specified via environment variables.
* Makefile: Silence compiler errors during dependency generation.Carl Worth2009-12-04
| | | | | | | | | | | | | | | We have a bootstrapping issue with our dependency generation. When the Makefile.config doesn't exist yet, the complete compilation flags are not yet available for passing to the compiler to generate the dependencies. But we don't have explicit rules to create these dependency files, (just the implicit rule that is created by the -include), so we can't control when make will attempt to create them. We do have a dependency of the dependency files on Makefile.config, so make should eventually call the compiler with the correct flags and everything should be good. So in the meantime, silence any complaints.
* Makefile: Inform user that they might want to call ./configure explicitly.Carl Worth2009-12-04
| | | | | | If the Makefile does this for the user, then no arguments are passed. So it's only polite to let the user know that it's possible to get pass those arguments.
* configure: Support the capturing of CFLAGS and CXXFLAGS at configure time.Carl Worth2009-12-04
| | | | | | | | | | | | | | | | | | These variables can now be set via configure time via environment variables like so: CFLAGS=-g ./configure and subsequent builds will remember these values. The values can still be overridden at compile time by passing make variables: make CFLAGS=-O2 The CXXFLAGS variable is optional. If unset at either configure time or at compile time, it will inherit its value from the CFLAGS variable. (Though if explicitly set at configure time it must be explicitly overriden at compile time---just overriding CFLAGS will not override CXXFLAGS as well.)
* Fix quiet compilation to print the user's CFLAGS, CXXFLAGS, LDFLAGS.Carl Worth2009-12-04
| | | | | | | | | | The only reason I ever call "make V=1" myself, (other than when debugging the compiler command-line for some reason), is to ensure whether my CFLAGS, (like "-g -O0" or "-O2"), are actually making it to the command-line. But these are hard to find in the V=1 output, and really, we should just print these even in the quiet case. So do that.
* TODO: Note about adding "notmuch search --matching"Carl Worth2009-12-04
| | | | | | | | This bug was recently discussed on the mailing list: id:878wdifu13.fsf@yoom.home.cworth.org so note one idea for fixing it.
* Fix option parsing for the case of a value with '='.Carl Worth2009-12-04
| | | | | To support this we need to match the longest-possible suffix and then strip the shortest-possible prefix.
* Fix configure script to handle --prefix=Jameson Graef Rollins2009-12-04
| | | | | | | Reviewed-by: Carl Worth <cworth@cworth.org>: This is really the fundamental thing that people expect a configure script to do, so it's important to support it.
* * notmuch-config: fix small leak from 'g_key_file_to_data'Dirk-Jan C. Binnema2009-12-04
| | | | Signed-off-by: Dirk-Jan C. Binnema <djcb.bulk@gmail.com>
* Make search filters handle disjunctive queries.Jed Brown2009-12-04
| | | | | | | | | | | | | notmuch-search-filter now accepts an arbitrary query and will group if necessary so that we get tag:inbox AND (gravy OR biscuits) instead of the former tag:inbox AND gravy OR biscuits Signed-off-by: Jed Brown <jed@59A2.org>
* Remove unused notmuch_parse_date function prototype.Jeffrey C. Ollie2009-12-03
| | | | | | | notmuch_parse_date is not implemented, so remove the unused function prototype. Signed-off-by: Jeffrey C. Ollie <jeff@ocjtech.us>
* configure: Tweak the working of the example commands slightly.Carl Worth2009-12-03
| | | | | Basically just getting better parallelism between the descriptions of the Defora and Debian commands. (And fixing a nearby typo.)
* Add some text to configure on how to install dependencies with yum.Jeffrey C. Ollie2009-12-03
| | | | | | | | | Add some text on how to install dependencies with yum for Fedora or other systems that use yum for package management. Since the named of the required packages on Fedora are slightly different from Debian this will help get new users of notmuch that use Fedora going quicker. Signed-off-by: Jeffrey C. Ollie <jeff@ocjtech.us>
* notmuch-reply: Display reply message part using UTF-8.Kan-Ru Chen2009-12-03
| | | | | | | Pass the message through the charset filter so that we can view messages wrote in different charset encoding. Signed-off-by: Kan-Ru Chen <kanru@kanru.info>
* vim: preserve the 'show everything' flag when finding next/prev bufferBart Trojanowski2009-12-03
| | | | | | | | | When show mode is invoked it could be displaying just the matched messages or everything. This flag is passed to NM_search_show_thread(). It is then stored in a buffer variable, b:nm_show_everything, and used for subsequent calls to NM_search_show_thread() triggered by <Space>, <C-n> and <C-p>. Signed-off-by: Bart Trojanowski <bart@jukie.net>
* emacs: Open only matched (and unread) messages when displaying a thread.Carl Worth2009-12-03
| | | | | | | | | | This is the long-awaited feature that when viewing a thread resulting from a search, only the messages that actually match the search will be opened initially (in addition to unread messages). So now, it's finally useful to tag a single message in a giant thread, and then do a search later and easily find just the single tagged message.
* emacs: Make message-summary button extend to very beginning of message.Carl Worth2009-12-03
| | | | | | | | There's no visible change here---we're just making the button extend through the invisible portions of the message before the message-summary line. The reason this is important is that it's easy for the user to position point at the (invisible) `point-min', so we want to ensure that there's a valid button there.
* Since we know what these buttons do it seems like the underlines areAlexander Botero-Lowry2009-12-03
| | | | unnecessary.
* emacs: notmuch-fontify-headers: Remove unneeded progn and indent correctly.Carl Worth2009-12-03
| | | | | | | The defun special form doesn't require a progn. And the remainder of the function was previously indented in a misleading way, (as if each "if" was always evaluated, rather than each only being evaluated if all the previous evaluated to nil).
* emacs: Make message-summary button begin at beginning of line.Carl Worth2009-12-03
| | | | | Otherwise, RET is unreliable for opening/closing messages when navigating through messages with 'n' and 'p'.
* emacs: Highlight message-summary with background-color instead of inverse video.Carl Worth2009-12-03
| | | | | Also, do this with a notmuch-message-summary-face variable so that the user can easily customize the desried effect.
* emacs: Make the message-summary highlighting extend to end of visible line.Carl Worth2009-12-03
| | | | | This will look much nicer than the highlighting terminating at the end of the summary text.
* emacs: Fix notmuch-show-next-open-message.Carl Worth2009-12-03
| | | | | | | This function was still implemented in terms of the old, global toggle for visibility of unread messages, (which no longer exists). Fix it to use the local 'invisibility-spec property on the button controlling message visibility.
* TODO, emacs: Correct a few typos.Carl Worth2009-12-03
| | | | Sometime I'll stop misspelling things so much, honets.
* TODO: Add some tasks, delete some tasks.Carl Worth2009-12-02
| | | | | | | | | | | | | A new item from IRC discussion, (speeding up "notmuch restore"), as well as a bug I just hit myself, (content from citations is not being indexed). While here, notce that several items have recently been completed ('?' now displays documentation, not function names; we have a search binding from notmush-show-mode; and "notmuch new" responds to SIGINT by flushing). Finally, the item regarding optimizing chunky searching is irrelevant since we dropped chunky searching in favor of the much better streamed searching.
* notmuch show: Preserve thread-ordering and nesting without --entire-threadCarl Worth2009-12-02
| | | | | | | | | | | | | | | | | | | | | | | | When "notmuch show" was recently modified to not show an entire thread by default, it also lost all capability to properly order the messages in a thread and to print their proper depth. For example, the command: notmuch show thread:6d5e3e276461188c5778c9f219f63782 had dramatically different output than: notmuch show --entire-thread thread:6d5e3e276461188c5778c9f219f63782 even though both commands were selecting and displaying the same set of messages. The first command would diplay them "flat", (all with depth:0), and in strict date order; while the second command would display them "nested" (with depth based on threading), and in thread order. We now fix "notmuch show" without the --entire-thread option to also display nested and thread-ordered messages. If some messages in the thread are not included in the displayed results, then they are not counted when computing depth values.
* notmuch.1: Document the new --entire-thread option to "notmuch show".Carl Worth2009-12-02
| | | | | This was added to "notmuch help" earlier, but not to the man page. Add it there, and use consistent wording in both places.
* emacs: Add --entire-thread option to "notmuch show" command line.Carl Worth2009-12-02
| | | | | We (plan to) do any hiding of messages from within emacs, so don't let notmuch hide messages from us.
* vim: use notmuch show --entire-threadBart Trojanowski2009-12-02
|
* notmuch show: limit display to only matching messagesBart Trojanowski2009-12-02
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | This patch changes the default behaviour of notmuch show to display only messages that match the search expression. However, --entire-thread option is provided to display all messages in threads that matched the search expression. It is deemed that will be more useful for human users on the command line. Scripts can be modified to include the --entire-thread option so that they can display all messages once more. Example: $ notmuch search subject:git AND thread:23d99d0f364f93e90e15df8b42eddb5b thread:23d99d0f364f93e90e15df8b42eddb5b July 31 [4/12] Johan Herland; [RFCv2 00/12] Foreign VCS helper program for CVS repositories (inbox unread) Note that in this thread 4 out of 12 messages matched. The default show behaviour is to show only those messages that match: $ notmuch show subject:git AND thread:23d99d0f364f93e90e15df8b42eddb5b | grep 'message{' | wc -l 4 With the --entire-thread option the output will contain all dozen messages: $ notmuch show --entire-thread subject:git AND thread:23d99d0f364f93e90e15df8b42eddb5b | grep 'message{' | wc -l 12 Signed-off-by: Bart Trojanowski <bart@jukie.net>
* configure: Allow user to specify compiler to be used.Carl Worth2009-12-01
| | | | | | | | | | | | The environment variables CC and CXX can be set at configure time to specify what compiler to use. This compiler will be used for any configure-time compilation, and will also be recorded in Makefile.config to be used during the actual build. The compiler to be used can still be overridden at build time by using a make variable such as: make CC=gcc
* configure: Generate more friendly Makefile.config with separated CFLAGSCarl Worth2009-12-01
| | | | | | Each dependency now gets its own variable in the resulting Makefile.config to make it much easier to debug where the various flags came from in the case of any problems.
* configure: Clarify pkg-config warning now that Makefile does not invoke ↵Carl Worth2009-12-01
| | | | | | | | pkg-config. It's probably a bit more work to use this configure script without pkg-config, but it's at least possible, (and we could make it even easier if this becomes an important use case).
* configure: Generate some documentation into Makefile.config.Carl Worth2009-12-01
| | | | | It's just not nice to auto-generate a file without helping out the poor user who gets stuck trying to figure out what went wrong.
* configure: Resolve all pkg-config flags at configure time.Carl Worth2009-12-01
| | | | | | | | Previously, we were resolving these within the Makefile. This had the problem that if pkg-config was not present, the Makefile would still invoke it resulting in ugly errors before the configure script was even run, (which would finally present a kind error message about pkg-config not being present).
* configure: Move getlinetest.c down into config/have_getline.c.Carl Worth2009-12-01
| | | | | | This keeps configure-related clutter out of the main directory, and also gives a more direct correlation between the name of the test and the feature being tested for.
* getdelim: Silence a (bogus) compiler warning.Carl Worth2009-12-01
| | | | | | Some compilers complain that result might be used uninitialized in this function. I believe such compilers simply aren't looking hard enough, but it's easy enough to silence them.
* Makefile: Split warnings into two sets (WARN_CFLAGS and WARN_CXXFLAGS)Carl Worth2009-12-01
| | | | | Some C++ compilers complain about -Wmissing-declarations not being valid, so avoid passing it except when compiling a C file.
* Makefile: Switch from echo to printf for better portability.Carl Worth2009-12-01
| | | | | | Some systems have an echo implementation which doesn't know how to interpret a sequence of "\n". The word is that printf should be much more portable, so let's try that instead.
* configure: Assimilate new getlinetest into recent configure conventions.Carl Worth2009-12-01
| | | | | | | | | We're now using printf to print what we're checking before we check. We're also making variables such as HAVE_GETLINE available to both make and to the C pre-processor. With this, the local getline implementation is now only compiled if not available on the system.
* Add test to configure script to detect getlineJeffrey C. Ollie2009-12-01
| | | | | | | | Add a simple test to the configure script to detect getline. It's not important that the test run, just that it compiles and links without any errors. Signed-off-by: Jeffrey C. Ollie <jeff@ocjtech.us>
* configure: Fix valgrind check to take effect, and to work.Carl Worth2009-12-01
| | | | | | | We were missing an "override" directive in the assignment of CFLAGS within Makefile.config so it was actually having no effect. Then, we were also failing to get the proper include path for valgrind.h so it wouldn't have worked even it were having effect. Fix both problems.
* Makefile: Incorporate getline implementation into the build.Carl Worth2009-12-01
| | | | | It's unconditional for a very short time. We expect to soon be building it only if necessary.
* compat/getdelim: Silence a warning about mixing of signed/unsigned.Carl Worth2009-12-01
| | | | | If the length is ever so large as to overflow, then we'll end up returning a negative value (which indicates an error anyway).
* compat: Change includes from config.h to compat.h.Carl Worth2009-12-01
| | | | | We may switch to using an autoconf-like config.h, but we're not doing that just yet.
* compat: Add implementation of getline from gnulib.Carl Worth2009-12-01
| | | | | | | | | These were copied from the gnulib git repository as of: commit 563c779682040ed4b89c9b4bbe428dcd8157c90a They come under the GNU GPL v3 (or later) exactly as notmuch is licensed.
* xutil: Implement xstrndup without relying on strndup.Carl Worth2009-12-01
| | | | | | | | Since we need to do this for portability, (some systems don't have a strndup function), we might as well do it unconditionally. There's almost no disadvantage to doing so, and this has the advantages of not requiring a configure-time check nor having two different implementations, one of which would often be less tested.
* lib/index: Fix memory leak for email addresses without names.Carl Worth2009-12-01
| | | | | | | | We carefully noted the fact that we had locally allocated the string here, but then we neglected to free it. Switch to talloc instead which makes it easier to get the behavior we want. It's simpler since we can just call talloc_free unconditionally, without having to track the state of whether we allocated the storage for name or not.
* configure: Use printf to achieve result of "echo -n".Carl Worth2009-12-01
| | | | | | | We had avoided using "echo -n" originally for portability concerns, and instead just printed the same string in both conditions, (and also printed the string late if any check took long). The word is that printf is quite portable, so we use that instead.
* Makefile: Add new "install-bash" target for bash completion supportCarl Worth2009-12-01
| | | | | | | It was problematic to have this in "make install" since it would unconditionally try to install to /etc, (even if a non-privileged user was attempting an install to a prefix in the user's home directory, for example).
generated by cgit v1.2.3 (git 2.39.1) at 2024-06-30 18:05:27 +0000